General recommendations
1 Enable access for restricted users.
By default, restricted users are allowed to access protected application and Allow users by user type option in windows users settings is set to "All users".
2 Protected application should be initially installed by user with administrator rights.
3 Decode Machine ID (MID) values in order to find out which (if any) locks are changed.
Please see "Machine ID code decoding" chapter in documentation for more information.
4 Use "Allow system time adjustments of up to xx minutes" option to prevent license reset in case invalid system time is detected.
Protection code is tracking system date and time. In case system clock is set back and is outside of "Allowed system time adjustments period" protected application will consider system time as invalid and reset license.
5 Enable flexible machine locking.
By default, change in any of enabled locking parameters will result in license reset. Flexible locking will allow you to customize default locking policy and to make it more flexible for end users.
6 Enable logging.
Enable logging and set appropriate logging policy to define which information should be logged by protected application.
7 Find our which error message was displayed before license was reset.
Exact error message will make finding the cause of license reset much more easier.
The following questions will help you in determining the cause of license reset
1 Did you decode current and previous MID codes and compare new and previous locking parameters?
Change in locking parameters will reset license. "Machine locking error!" message is displayed in this case. Application will generate different Site/MID codes and will ask for new activation code. You can find which (if any) locking parameters are different by decoding current and previous MID codes.
2 Is this computer used by multiple restricted or administrator users?
In case support for restricted users was not enabled switching between different user accounts could invalidate license.
3 Was application installed and unlocked by user with administrator rights?
Even if support for restricted users was enabled application should be installed and activated by user with administrator rights in order to avoid problems in case computer is accessed from multiple (restricted) user accounts. In case application was installed and activated by restricted user it will work just fine for that user. However, in case it's accessed from another restricted user account it may refuse to work (depending on installed OS).
4 Is there any removable cd/dvd/hd/ethernet/wi-fi card device in this computer?
Removable device which is often enabled/disabled (removed) can affect locks and thus reset license. You can turn off appropriate locking parameters or enable flexible locking policy. Please see machine locking notes chapter in product documentation.
5 Is this computer part of network with roaming profiles enabled?
Using roaming profiles on network could affect license status. Be sure to enable "Enable support for roaming profiles" option if application is distributed to users with roaming profiles enabled. In this case protection code will handle license data in such way that it is not affected by roaming profiles.
6 Did you enable "Erase previous license" option?
If existing active license is detected on remote computer this option will reset license.
7 Is there some kind of security software installed?
Some third party software could affect license status by deleting license information or preventing protected application from managing it.
8 Was system time turned backward?
In case limited license feature is active license will be invalidated in case system time is turned backward. Time synchronization software could also affect license by turning system time backward.