The default option is, that an Activation Key can only be used once. A key is stored in the license file and even if the license file is replaced, it can never be used again on the same machine.

 

If you want to allow that:

 

•a user can uninstall the application and reinstall it again

•any additional Activation Key can be used again when an application is reinstalled

•a user can change his hardware like network adapter

 

on the same machine, you can configure this as an option.

 

There are different ways for a reinstallation.

Reinstallation during the Evaluation Period

Reinstallation during the evaluation period is always possible but will never prolong the evaluation time - for details see Evaluation Options.

Restore a  Backup

If the user backups the license file, deletes the folder, and restore the license file, the application will work without any additional configuration settings.

Complete Reinstallation

With a complete reinstallation, the original (generic) license file is installed again. The user has to enter the Serial Number again. By default, the Serial Number Key can not be entered twice. If you select Unlimited installation

during the creation of an Serial Number Key, the key can be used multiple times on the same machine.

 

Hardware ID changes

The hardware ID changed because e.g. the network card was replaced. The result is a copy protection error. Your application could now try to automatically reactivate the product.

 

How does Licence Protector detect, if an Activation Key is used on the same machine?

There is a 2 step process.

 

1. Local (offline) test

 

The original key is stored in different places. If a new Activation Key is applied, it is checked if the Activation Key was already used or not.

 

2. Online validation

 

If an Activation Key is marked for Online Validation or the application is activated online, then the Activation Server performs an additional online check. For each Activation Key or product activation, the complete hardware profile (installation codes) is stored. The Activation Server now checks, if the Activation Key was already used on the same machine (the installation codes match) or if the Activation Key is sent from a different machine.  If the installation codes do not match, the Activation Key is used on another machine and is rejected.

 

You can define, how many criteria have to match - e.g. 3 criteria out of 9 should match to allow a reinstallation.

 

Example

The MAC address is used for Copy Protection. The user replaces the network adapter. A reinstallation should be possible if hostname, volume ID, and NetBios name matches. This would allow a reinstallation even if the network is replaced.

 

It is possible to define that all installation codes must match. This would allow a reinstallation only on a 100% identical machine configuration.

 

For a network license, the server hardware is used to identify the machine.

 

A reinstallation is not possible if you use Tamper Detection. To allow a reinstallation, deactivate Tamper Detection.

 

See also
Create Activation Key / Serial Number for multiple usage
Web Activation Server definitions
Reactivation after copy protection violation