Setting up a New MyWorkDrive Instance (Overview)

Server Sizing

The VM size depends on user behavior, the sizing guide is the best resource to determine your needs. For example:

• Small deployments will run on 2 core / 4gb of ram. Typically for less than 50 users/light utilization.
• Larger deployments will scale to 8 cores / 32gb or ram. Typically for more than 50 users but less than 250 users/medium utilization.
• Deploying multiple MyWorkDrive servers for load or business continuity reasons is supported. Clustered MyWorkDrive servers are recommended for environments larger than 250 concurrent users.

Server Sizing details are available in this guide:
https://www.myworkdrive.com/support/server-sizing-guide/

Installation Basics

MyWorkDrive is an application that needs to be downloaded and installed on a Windows server. The software can be downloaded from our portal here:
https://www.myworkdrive.com/portal

If you are installing for the first time and need a trial key, one will be generated as part of the install.

We support all Microsoft Server OS’es that Microsoft presently supports – 2016 to 2025. MyWorkDrive can be installed on a physical or virtual server, on premise or in the cloud. We would advise installing the MyWorkDrive server as close to storage as possible – if you’re using Azure Storage, an Azure VM would be advised; if using local SMB storage, a local VM would be advised.

We advise installing MyWorkDrive on a clean server without any other software installed. MyWorkDrive will install all necessary prerequisites (.NET, C++, IIS, RSAT, etc)

When installing, the administrator will choose to either install it using Active Directory or Entra ID for identity. Active Directory usage requires the server to be domain joined.
After installation, you should be able to access the admin panel using either a domain admin or a local admin account.

For complete installation details, please review the Server Setup Guide:
https://www.myworkdrive.com/support/server-setup-guide/

Additionally, we do have an imaged Azure VM that could be deployed. Instructions are available here:
https://www.myworkdrive.com/file-server/azure/

Please be mindful that Anti-Virus exceptions may need to be created for MyWorkDrive to install and function appropriately. Please review this document for additional details:
https://www.myworkdrive.com/support/antivirus-settings-for-myworkdrive/

Storage Basics

MyWorkDrive can use SMB, OneDrive, SharePoint, Azure Files or Azure Blob as storage
The access and connection options vary depending on the use of AD or EntraID as the user identity provider. Here’s an article that covers those topics in more detail:
https://www.myworkdrive.com/support/storage-options-by-product-version/

End User Access to MyWorkDrive

Publishing the server for access by end users can be a public or private endpoint, with a direct connection or behind a proxy or load balancer. We outline various options in our deployment guide:
https://www.myworkdrive.com/support/publishing-your-myworkdrive-server-to-the-internet/

Additionally, some firewall ports and rules may need to be adjusted to accommodate MyWorkDrive. We have a full list available here:
https://www.myworkdrive.com/support/firewall-settings-myworkdrive-server/

Once available to end users, users can access via the Webclient or Install clients for Mac/Windows and iOS/Android.

MyWorkDrive Native Clients

MyWorkDrive has native clients for Windows, macOS, iOS and Android. We have additional information on the available functionality and installation options in our client admin guide:
https://www.myworkdrive.com/support/desktop-clients-admin/

Additional Options

Single Sign On (For Active Directory Deployments):
https://www.myworkdrive.com/support/sso-setup-overview/

Delegation (required for SSO and Public Sharing with SMB):
https://www.myworkdrive.com/support/delegation-setup-adfs-dfs-servers-active-directory/

DUO/2FA:
https://www.myworkdrive.com/support/duo-two-factor-authentication/

Office Online Editing:
https://www.myworkdrive.com/support/office-365-online-editing-setup/

Device Approval:
https://www.myworkdrive.com/support/device-approval/

Scripted Client Install:
https://www.myworkdrive.com/support/desktop-clients-admin/

Branding:
https://www.myworkdrive.com/support/client-branding-settings/

DFS:
https://www.myworkdrive.com/support/configuring-shares-on-dfs-with-myworkdrive-server/

Public Sharing:
https://www.myworkdrive.com/support/public-link-sharing/

Web Client Search:
https://www.myworkdrive.com/support/windows-file-server-search/

Data Leak Prevention:
https://www.myworkdrive.com/support/data-leak-prevention/

Support for Multi-Node/Cluster environments:
Clustering and Load Balancing MyWorkDrive Servers

SEIM syslog integration
https://www.myworkdrive.com/support/syslog-integration-configuration/

Time and Resources

Installing MyWorkDrive takes about 15 min, when you have a server VM ready to go.

Configuring is a variable depending on the features you want to deploy and the available resources. 15 minutes at minimum. Usually 30 or so. But can take several hours to configure advanced features in Azure or publishing with Proxies or Load balancing.

General disciplines to have available to complete setup

• Someone who can create and manage servers/virtual machines (MyWorkDrive installs on a Windows Server(2016,19,22). The server needs to be domain joined if you intend to use Active Directory for the user database.) Typically best if the VM is created, patched and domain joined (if using AD) prior to the setup call.
• Someone who has admin to AD to add delegation rules and domain join machines if using AD for user identity.
• Someone who is a Global Admin to Azure, if using Entra ID for user identity (and/or if we want to enable services in Azure – office online editing with SharePoint, SSO, OneDrive/SharePoint shares)
• Someone who can manage DNS, Firewall, Routing, SSL. We may need outbound ports enabled for some services. We may need inbound mappings – if we want to publish the server to the internet with a direct connection or proxy (can deploy on our built in reverse proxy or internal only – but may still need ports opened internally)
• A project owner who knows what resources/users should be included in the configuration – what shares are needed, who needs them, what features they need.

The most time consuming elements of initial setup options are

• Publishing with Proxies or Load Balancers.
• Publishing with direct connections which require SSL/DNS and Firewall changes
• Enabling SSO with Active directory user database, requires adding an enterprise app, setting Delegation in AD. This runs about 15 minutes.
• Enabling Office Online Editing with an Azure tenant hosted app. This usually takes about 30-60 minutes. It can be done with apps hosted by MyWorkDrive using the user’s OneDrive acccount in nearly no time, but if you want to use your own Azure Apps or a SharePoint Service Site, there are steps to complete in Azure/SharePoint.
• Enabling OneDrive/SharePoint as file shares. Similar to Office Online Editing, this can be done quickly with MyWorkDrive hosted apps, but creating your own in your own Azure tenant takes a little bit.
• Guest User Access using Microsoft B2B with Active Directory for users – This takes 60-90 minutes.
• Configuring ACL with Azure Blob Shares. This can be done quickly, but usually leads to questions about options and usually runs 60-90 minutes.

Support

MyWorkDrive support’s hours of operation are currently 8am PST to 5pm PST Monday through Friday. However, we can always be reached by Email:
support@myworkdrive.com
Submitting a ticket using our Help Desk Portal