|
|
The Basics about Copy Protection |
|
|
|
||
|
The Basics about Copy Protection |
|
|
|
|
The Basics about Copy Protection
|
|
|
The Basics about Copy Protection |
|
|
|
||
|
The Basics about Copy Protection |
|
|
|
|
This feature prevents the application, that it can be run on different machines. It binds the license file to a hardware specific item.
The user can not move the application from computer A to computer B because the hardware identifiers that are used for Copy Protection will be different on another machine - Copy protection does not prevent the copy process but starting the application on non licensed machines.
The place, where the license file is stored is used to determine the hardware information of the machine.
| • | If the license file is stored on a local machine, then the hardware of the local machine is used |
| • | If the license file is stored on a server, then the server hardware is used (Volume ID, MAC Address, Hostname). When starting the application on a local machine within a network, Licence Protector retrieves the server hardware even if the application is running on the local machine |
| • | If the license file is stored on a NAS drive (Network attached storage), then the hardware of the NAS is used (Volume ID, MAC Address, Hostname). When starting the application on a local machine within a network, Licence Protector retrieves the NAS hardware even if the application is running on the local machine |
Copy Protection can be used as an option. You can create a license without Copy Protection by just sending out an Unlock Key without Copy Protection (manual product activation) or special configuration settings for the online activation.
You can also use your own hardware IDs - see chapter Use own hardware IDs