Server Limitations

Updated: 12/07/2021 04:32 PM

Disclaimer: We do not under any circumstance recommend a user to install and use our software on any form of server unless absolutely necessary and you have a very experienced IT/Server Manager that knows exactly what they are doing with a given Windows Server.

Our software was never designed with server usage in mind. There are a few work arounds that over the years have been found to work, however, your mileage may vary heavily.

To start, if you do not understand or have a good grasp on how we issue licensing with our programs, please read through our 'Licensing' documentation page.

The main issue that happens when installing our software on any form of server is the activation. Because our activations are 'User Licenses', it can cause issues when the given user tries accessing a server. A user can experience issues because that user, when connecting to the server, is given a different user account through windows or is given a completely different windows instance than they used previously. Since our program uses 'User Licenses', it is important that the user signs into the same machine running the same windows install with that users windows account accessed each time.

There are multiple methods for this to be done effectively but the main option that we have tested and have not had problems with is to use a dedicated virtual machine for a single user. This means that the only person that should access this machine is that user making it as if the virtual machine is that user's workstation just accessed remotely.

We have had some customers get our software working with unknown methods (to us) on virtualized servers/machines (such as Citrix or other VM farms), but this has been a 'it works sometimes with specific settings on the server' so we do not recommend trying to get these options to work as most people do not have the time as the filing deadlines approach to fight with program issues.