Setup
...
Requirement
Internet access at the client level is needed for activation at the time of first use (they . This can be Internet isolated after 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 as that process will to highlight any potential issues.
Licenses
Licenses are required on a per PC (instance in a VDI / Citrix environment) basis. You would need a license 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, you would need 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, much depends on how your it’s crucial to manage how seats are managed handled between log on and /off and if they whether instances are destroyed on log off. Also, if If the instance changes in any substantial way (SID, MAC, Hostname, etc) with each instance (even for the same user), scripting deactivation would be crucialnecessary.
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
So, in In a typical VDI / Citrix deployment, again - especially if a PC instance is destroyed / different changed between log of off and on - one would script activation on scripting deactivation and activation is advised.
Activation at log on:
https://support.stardock.com/space/SHC/1352531974/Product+silent+installation+and+activation
And deactivation on Deactivation at log off:
https://support.stardock.com/space/SHC/1340342298/How+to+deactivate+with+the+command+prompt
...