How_Many_Remote_Desktop_Servers_Are_Needed_
Client_Machines_-_WDSAAS_Workstations
Aside from the specific hardware and software requirements listed below, there is one other essential pre-condition for running Worldox Enterprise. You must currently be running Worldox Professional.
Worldox Enterprise can be deployed on either Microsoft Windows Server 2012R2/2016/2019. Functionally, these deployments are identical; however there are different considerations for each.
Microsoft Windows Server 2012R2/2016/2019
|
REQ: |
You can refer to Sample Scenarios for more information. However, during your site survey phone call, your Enterprise installation technician will be able to confirm requirements specifically needed for your site. |
There is no one best answer, as that depends on a complex interaction of hardware capabilities, expected usage patterns and requirements (if any) for redundancy and uninterrupted access to Worldox.
As best practice, we recommend:
Use dedicated servers (machines or virtual) for Worldox Enterprise.
Plan for redundancy; use multiple servers even in low-usage, few user scenarios.
Note: While we recommend multiple servers for redundancy, we defer to Microsoft for specific site planning. For more information, please visit:
https://technet.microsoft.com/en-us/library/hh831447.aspx
When anticipating higher use levels and many users, split the server load to multiple servers AND have at least one backup server on hand.
Factors to consider:
1. Total number of users expected to access Worldox Enterprise
2. Maximum number of Worldox Enterprise users expected at peak load times
3. Access strategy: Will Worldox Enterprise be used as a secondary, remote access point for users – from home offices, at client sites, on the road – or will Enterprise be the primary Worldox access from all points?
4. Server specifications, capacity, configuration
5. Need for uninterrupted access; if your sole Worldox Remote Desktop Server goes down, what is the impact? If one of multiple Worldox Remote Desktop Servers goes down, can the remaining server(s) handle the load?
|
|
Conditions |
Server |
Detail |
|
A |
5 Worldox users Enterprise provides partial access to Worldox, supplementing local network access |
1 or 2 |
One dedicated Session Host is sufficient to handle the load. To add redundancy and a safety factor, add a second Session Host. |
|
B |
18 Worldox users Enterprise provides partial access to Worldox, supplementing local network access |
2 |
One dedicated Session Host MAY BE sufficient to handle the load. To add capacity, add a second server. That second server also serves as backup, adding redundancy and a safety factor. |
|
C |
18 Worldox users Enterprise is the sole access point to Worldox. |
2 or 3 |
One dedicated Session Host MAY NOT BE sufficient to handle the load. To add capacity, add a second server. That second server also serves as backup, adding redundancy and a safety factor. Given expected higher loads, consider adding a third server. |
|
D |
35 Worldox users Mixed access: Enterprise is the sole access point to Worldox for some users, and offers remote access to all users. |
3 |
Two dedicated Session Hosts MAY BE sufficient to handle the load. To add capacity, add a third server. That third server also serves as backup, adding redundancy and a safety factor. |
|
REQ: |
One, dedicated machine (workstation class for small deployments): Running Windows 10 or newer OS Minimum 4 gigs RAM Multi-core processor |
|
REQ: |
For each workstation: Running Windows 10 or newer OS Minimum RAM: 4-6GB Remote Desktop Client v.7 minimum |
|
REQ: |
Microsoft Windows Server 2012R2/2016/2019: On the firewall, make sure port 443 is open and routing to the internal IP of the machine that will be designated as the Remote Desktop Gateway. Depending on setup, the gateway role and all other Remote Desktop Services may be on a single machine or split between multiple. Example Hostname to use (ts.domain.com). Please contact Worldox Technical support for clarification on the optimal layout for your given application. |
|
REQ: |
If using an SSL certificate, on the Firewall make sure you have Port 5010 open and routing to the internal IP of the WDSERVER machine. If the site is large, also add Port 5011. Example Hostname to use (wdserver.domain.com). |
| REQ: |
The WDSERVER should be able to access port 80 and port 21 for code updates. If necessary, these ports can be limited to accessing the following URLs: wdcrs.wdsaas.com, wdserver.worldox.com, wdserver2.worldox.com. |
|
REQ: |
Minimum 1Mbps Per User |
Consider that bandwidth requirement as a bare minimum. It might be enough at a small office, where Worldox Enterprise is used as a secondary, remote access point for users. That bandwidth may be not nearly enough in larger offices with more users and more activity.
It is difficult to state bandwidth requirements, as what will be an acceptable or optimal at your site depends on a complex interaction of factors, not all strictly Worldox-related:
1. Communication hardware, capacity and configuration used
2. Total number of users, all applications
3. Number of users expected to access Worldox Enterprise
4. Number of Worldox Enterprise users expected at peak load times
5. Total volume of traffic now (all applications, not including Worldox) at your site, average and peak load
6. Expected DMS usage patterns … will most users be uploading/downloading documents frequently?
7. Average file size of Worldox-managed documents.
8. Is this connection also used for video conferencing?
In terms of bandwidth, there are few helpful guidelines available. Microsoft recommends that 128kb be reserved for each user on remote access. However, that recommendation covers screen transfers only. Bandwidth required for Worldox Enterprise would clearly have to be much higher, given that Worldox sends and receives much more than just screen data.
So here, our best practice recommendation is simple. Get more bandwidth than you think you need, as much as you can afford. Extra capacity affects speed, which directly correlates to workflow efficiency and user satisfaction.