Enterprise VDI / Citrix Deployment Guidelines

Requirement

Internet access at the client level is needed for activation at the time of first use. This can be isolated afterword if PCs retain their state between log on and off. To see if the activation process will work with your security protocols (firewalls, proxy, etc), please first install and activate a software trial to highlight any potential issues.

Licenses

Licenses are required on a per PC (instance in a VDI / Citrix environment) basis. A license is needed for each real and potential PC. For example, if you usually have 50 unique concurrent PC, but you could have 500 concurrent PCs, then 500 licenses will be necessary.

A single key will be issued with X concurrent activations associated with it, where X= the number of licenses purchased.

Deployment

For virtual PC deployments, it’s crucial to manage how seats are handled between log on/off and whether instances are destroyed on log off. If the instance changes in any substantial way (SID, MAC, Hostname, etc) with each instance (even for the same user), scripting deactivation would be necessary.

Should any instance / VM be destroyed prior to deactivation, there are tools on your account page to deactivate them manually:

https://support.stardock.com/space/SHC/1260585049/How+to+deactivate+Stardock+products

In a typical VDI / Citrix deployment, again - especially if a PC instance is destroyed / changed between log off and on - scripting deactivation and activation is advised.

Activation at log on:

https://support.stardock.com/space/SHC/1352531974/Product+silent+installation+and+activation

Deactivation at log off:

https://support.stardock.com/space/SHC/1340342298/How+to+deactivate+with+the+command+prompt

We can provide tailored scripting if requested.