A further advanced option is to set the time between server-client checks, or the client "lease time", for each license code associated with this specific product. Click the 'options" tab:
You have three server call-back time (License Check Interval) choices:
- License check Interval: This is the standard maximum time-gap between End-Users' Software successfully 'calling' to NSL's Servers (to check the validity of its License) before their Software becomes disabled.
- License check Interval Offline (Days): Following a successful Offline Activation (the method used when End-users have no Internet Connection, or their Firewall prohibits their Software from talking to NSL's Servers), this is the maximum time-gap before re-activation is required.
- License check interval VM (Hours): This applies if the activated device is a virtual machine and has been detected as such with our virtualization management functionality, if enabled.
NOTE: The VM license check interval takes precedence over the Offline one (where both are applicable) and both of these take precedence over the standard license check interval.
If set to '0', no re-activation schedule is set and hence End-Users will not experience any future requirement for re-activation.
Set your choice of interval and then click save.
Security advisory: If you have a normal application then you will want to set this value to a low number. If you have a low-security client deployment where you trust the user base then you can make it a longer period. If you want the equivalent of a perpetual license then make the setting a very long period. This period is used to check and update the remote client, and to also prevent more installations of your product in the wild than you set. The longer the period you set the longer time lag before illicit versions are terminated or remote features are switched on/off etc.
Caution: Set to 0 should only be set for specific license codes/end-user installations unless you wish to never have your products validate with the server - this option would allow users to abuse your EULA as the server will never be able to validate the number of active deployments of the license code (the number of activations) against any limits you have set.
This is all that is required for this stage.
Concurrency Mode: When becoming acquainted with Zentitle, Concurrency mode can be set to 'Off'. Cloud concurrency is discussed in this document and network concurrency applies to the LAN daemon local license server as discussed here.