MyWorkDrive Support

How can we help you today?

Server Setup Guide

You are here:
< Back

Overview

The MyWorkDrive Server services provide web based access to existing Windows file shares that support our Web File Manager, Mapped Drive Client and Mobile Apps. The MyWorkDrive Server services should be installed on a stand-alone Windows physical or virtual server that is located on the same LAN and domain as the Windows file shares and run within IIS.  Setup will install the IIS services automatically.  In addition to making the file shares available over a web browser, the MyWorkDrive server enables our API for securely mapping drives using our Mapped Drive, Office 365 & Mobile Clients. For additional details, read the Technical Overview Support Doc.

View the setup video here:

Before you begin, ensure you have regular and complete backups of your file server(s).  In addition, we recommend volume shadow copy be enabled with hourly snapshots on all file share drives.

 

 Step 1: Server Prerequisites

  • Domain-joined, fully patched server running Windows 2012 r2 – 2016 Server.
  • .Net 4.6 (will be prompted to install by setup as needed).
  • Minimum 4 GB ram, 2 virtual cpu’s if installed as a virtual machine – for larger enterprises please review our Server Sizing Guide.
  • Direct Internet access on the server running MyWorkDrive (no proxy services) to activate and initialize the software with outgoing firewall access to ports 443, 9350-9354 and 5671.   For additional details on locked down environments review our firewall settings guide.
  • Antivirus software products installed on the MWD server can interfere with MyWorkDrive processes and cause extreme slowness for IIS Web Services.
  • Incoming port 443 (if you will be using your own domain name & SSL certificate).
  • Server must be part of a Windows Active Directory domain, ideally a member server.
  • The server where MyWorkDrive is installed should be on the same LAN or very fast connection as the  Windows File Shares for best performance.
  • We do not support installing MyWorkDrive on a server that is running Small Business Server, Microsoft Exchange, other IIS sites or any software that includes IIS .net components.
  • If shares are accessed through DFS, ADFS or SAML is used for authentication it is necessary to enable delegation so that the MWD Server trusts these servers – see support article here.
  • Additional client requirements and limitations are located in our support article here.

Step 2: Verify & Run the MyWorkDrive Server Setup

  • Logon to the server as a domain admin
  • Run MyWorkDrive-Setup.exe,
  • When setup completes restart the server to complete the installation.
  • Open the MyWorkDrive Control Panel (shortcut on the Desktop) in Chrome browser at http://127.0.0.1:8358
  • The post setup wizard will launch with basic setup questions including shares, Office 365 editing and optional myworkdrive.net relay usage
  • Once at least 1 share is setup and the server is made public (using myworkdrive.net domain or your own host name(see below) you may begin using MyWorkDrive.
  • You will receive an email when your site is ready if using *.myworkdrive.net domain – this takes about 15 minutes.

Step 3: Post Setup: Login into the Admin Portal to Setup Shares

  • Open the MyWorkDrive Admin page at http://127.0.0.1:8358 on the MyWorkDrive Server
  • Login using an Active Directory Domain Account with local administrator rights on the MyWorkDrive server and permissions to read network file shares.  For example the domain admin credentials ( mycompany\administrator or administrator@mycompany.local ).  Be careful to only login using a domain account, do not login using a local machine account.
  • If you have trouble viewing the admin page in your server’s browser adjust your screen size and disable Internet Explorer Enhanced Security Configuration (IE ESC) for administrators or use our recommended browser – Chrome.

Step 4: Setup Shares

If no shares are already setup (new installs) The MyWorkDrive Admin Panel will start with the Add Shares section already open, otherwise click Add to setup shares.   Enter a folder name (share name) and the folder path that points either to the local file share path (eg: e:\share if installed directly on the file server ) or enter the path to the network share using host name and share name on the same LAN as the MyWorkDrive Server (eg: \\server1\project ).



Import existing Users and Groups permissions to begin choosing what users/groups should be able to see the share in MyWorkDrive or manually search and Add Groups and/or Users you wish to permit access to the shares in MyWorkDrive.  Note we only import only imports existing permissions to help you select what users/group who already have NTFS permission can access sharing using MyWorkDrive.  Note future user/group changes need to be add/removed from MyWorkDrive shares so ideally use Active Directory Groups to limit updates.

Verify Home Drive Settings on the Settings tab – enabled by default – this information is pulled from Active Directory automatically for each user on their profile tab.

Set the file size limit for transfers ( this will depend on your internet upload/download speed ), we recommend limiting to 30 MB or less on slower connections.

Starting in Server version 4 we allow entering %username% variables – for example: \\servername\project\%username% in the folder path.  If the user has a folder only their folder will appear under the share.

** Note existing file share permissions on your file server should be everyone full control and only utilize NTFS to limit user file permissions  – As a security precaution, MyWorkDrive passes through authentication and will only provide access to files and shares the user/group already has on the internal network, Users must already have NTFS and share permissions to the files prior to adding to MyWorkDrive.   MyWorkDrive can limit permission further but not grant NTFS permissions to any shares.  Share permissions are a legacy feature in Windows and best practice is to set user permissions using NTFS only and allow everyone full control at the share level.

Step 5: Proceed to accessing the client file web access site to verify functionality

  • Access the local site for basic testing of the site at http://127.0.0.1:8357  or  over port 80 at http://127.0.0.1 beginning with Server Version 4.2 (Chrome browser is best)
  • Login using various users to test web file access, shares and home drive access (if allowed) on the Server.

Step 6: Publish to the cloud

When you have completed the setup, you can make your files available remotely (in the cloud) by utilizing 1 of these 2 methods:

a. Cloud Connector https://YourCompany.MyWorkDrive.net

If you would like to use our Cloud Web Connector to make your server available to user’s in the cloud at YourCompany.MyWorkDrive.net simply access the settings page at http://127.0.0.1:8358 on your server and enter your host name on myworkdrive.net and choose your closest data center.     While you are waiting for the deployment to complete you may test locally using the client test site at http://127.0.0.1:8357.  Typically your server is live within 15 minutes.  Note: We do not support myworkdrive.net for production use of our mapped drive client.   For fastest speeds and larger file access we recommend you setup direct access using step b below.

b. Publish your own domain by adding an SSL certificate

For fastest speeds, mapped drive client use and enterprises, use your own hostname, SSL Certificate and open port 443 from your firewall.  Steps: Setup a host-name on your domain:eg: share.mycompany.com, Install and purchase an SSL certificate, Bind the “WebClient” site in IIS to port 443 and finally expose your site over port 443 through your firewall.  For security we do not recommend opening up your site to port 80 (http) unless redirected to port 443 (https) – See Require SSL setting.  For additional instructions see our support guide on how to setup and install your own SSL Certificate/Hostname to your MyWorkDrive server.

Optimization Tip: We recommend using internal DNS to force any site traffic as local – So for example internally share.yourcompany.com should resolve to the internal ip address.  This speeds up internal access and bypasses any firewall issues.  This is standard practice for any internally hosted website – for example Exchange Outlook Web Access and ADFS.

Security Tip:  We recommend reviewing our guide on how to harden your IIS Server and disable unneeded IIS SSL Ciphers: Read the SSL Lock Down Guide Here. 

Standard Features & Settings

Office 365 Online/Office Online Server File Editing:  Knowledge Base Article

MyWorkDrive Server supports online editing of documents stored on local file shares in Office 365 Online or using a Local Office Online Server in our Web Browser client and in iOS Office apps.  MyWorkDrive is the only solution that allows users to edit Office Documents in Office 365 Online but store them on-premise.

An Office 365 Business account is required to edit Office documents online (View does not require an Office 365 Business Account).

Enable Office 365 Editing using the setting tab in the MyWorkDrive Server Admin Site on your MyWorkDrive Server.

Optionally in settings add an email domain lookup of your sign-in URL to assist mobile users when using Office Mobile Apps if your domain user’s email address can also be used to sign-in to active directory.  If enabled, when a user adds MyWorkDrive as a place in iOS or Android mobile office apps they can sign-in with just an email address and password and will not be prompted to enter their MyWorkDrive server URL: for example email domain is acme.com and sign-in URL is https://share.acme.com:

Office Local Web Edit: By Enabling this feature users can choose edit from the menu in the Web Browser client and office documents will open directly from the browser in local office.  For security an additional security prompt will be presented.  If DUO Two Factor Authentication is enabled it will be requested as well.  The administrator can optionally disable password saving for this additional pop up – which means the user will be prompted for username password every time a document is opened for edit from the browser in local office.(default:enabled).

Office Double Click Action:  This feature allows the administrator to control the action when an office file is double clicked in the web client – Open Online, Open Locally or Download (default:open online).

Require SSL:  By enabling this option any http port 80 connections to the MyWorkDrive client site are automatically redirected to https (http port 80 and https port 443 must already be bound to the webclient site in IIS and Windows Firewall on the server must be set to allow ports 80 and 443 to public addresses) (default:disabled).

Require Email Username Format: Enabling this option will require users to login using email address.  This is helpful in larger companies with multiple domains and also lessens the impact of entering a bad password lockout since only the 1 username is checked (default:disabled).

Enable Mapper Client: By disabling this option users will be unable to login using the desktop mapped drive client (default:enabled) in addition the administrator can restrict password saving or file types (requires version 5 of the mapped drive client).

Enable Mobile Client: By disabling this option users will be unable to login using the desktop mobile client (default:enabled).

Enable WebDAV: By disabling this option user will be unable to use WebDAV to login to MyWorkDrive (note disabling is recommended when Two Factor Authentication is used) (default:enabled).

Enable OneDrive Sharing:  By disabling One Drive Sharing users will not be able to share files externally using OneDrive (default:enabled).

Enable Outlook Sharing: By disabling Outook Sharing users will not be able to share files externally using Outlook Online (default:enabled).  The maximum attachment size can also be set – default is 10 MB.  If company policy requires MFA to authenticate users to Office 365 additional steps are required before enabling this feature – Outlook Sharing Article.

Home Drives:  By default home drives are enabled and available to users when they login.   MyWorkDrive will display the UNC path as specified for that user in AD Users & Computers.  The file server should be located ideally on the same LAN as the MyWorkDrive server ( or on a very fast connection ) and will need to be able to resolve the server by the host name as entered in AD Users & Computers.   Optionally require users have access to at least one MyWorkDrive share to restrict user logins to the MyWorkDrive server.

Search:  MyWorkDrive integrates with the the Windows Search Service.  Due to Windows limitations, Windows Search integration is only appropriate for up to 2 TB maximum. Windows File Server Search Guide.  For Enterprises with larger file server volumes or NAS devices MyWorkDrive integrates with dTSearch.  dtSearch Setup Guide.

Session Timeout: In Settings it is possible to edit the default settings for user session timeouts.   Please note you can set both the public PC and private PC settings on this page (calculated in minutes).  The default times are 8 hours for Public computer and 5 days for private computer ( these match Microsoft Office 365 defaults ).  Adjust these timeouts to meet your companies security requirements.  For additional security enable Duo Two Factor Authentication.

Enterprise Features & Settings

Two Factor MyWorkDrive supports Duo Two Factor Authentication for enhanced security.  Configuration details are located in our Two Factor Authentication Support Article.   Two Factor Authentication requires an Enterprise or Partner License.

ADFS/SAML SSO:  ADFS integration allows users to access MyWorkDrive using ADFS for a Single Sign On (SSO) Experience without requiring re-entering of credentials.  ADFS Support Article Note: MyWorkDrive users can already sign-in with their Active Directory accounts, ADFS or SAML adds additional integration options for enterprises.  MyWorkDrive supports SAML integration with easy integration for popular providers such as Microsoft Office 365/Azure AD, OKTA and OneLogin.  SAML Support Article.  Optionally require users to access the MyWorkDrive Web Browser client using ADFS or SAML by enabling “Require ADFS/SSO Login in browsers”.  To enable logging out of ADFS or SAML when signing out of MyWorkDrive “Enable single logout”.

Clustering/Load Balancing:  MyWorkDrive supports clustering multiple servers for fail-over and load balancing.  See our support article for additional details.

Branding:  Enterprise licensees can customize the powered by, help page URL, background and toolbar colors

Data Leak Prevention (DLP):  Review the support article for DLP.  Data Loss/Leak Prevention requires an Enterprise or Partner License

Previous Versions  MyWorkDrive connects to Windows Volume Shadow Copy Snapshots (VSS) services to enable previous versions restores from our Web Client. Review the support article for Previous Versions