|
|
Deliver license File and Serial Number |
|
|
|
||
|
Deliver license File and Serial Number |
|
|
|
|
Deliver license File and Serial Number
|
|
|
Deliver license File and Serial Number |
|
|
|
||
|
Deliver license File and Serial Number |
|
|
|
|
If you have more than 5 modules it makes sense to deliver a customer specific license file with all the modules enabled the customer has bought. Otherwise the user would have to type in an Activation Key per module.
This scenario works as follows:
| • | Evaluation Version with generic license file. Use the same settings like EasyGo |
| • | Customer buys the product - he gets a customer specific license file and a Serial Number |
| • | Type in the customer name |
| • | Copy protection must be set to none |
| • | The Activation status must be set to none |
| • | Set all modules to the values the customer has bought |
| • | The Serial Number is used to activate the product using the EasyGo Workflow - see Workflow - from Distribution to Activation |
| • | Customer copies license file to the installation directory |
| • | Activation of the product using the EasyGo screens and workflow - how to implement EasyGo see Implementing EasyGo |
Customer specific license File
This license file should have the same settings like the generic license file (including time limitation for the main module) but all other modules the customer has bought without time limitation and set to the values needed (e.g. set number of licenses bought). The time limitation of the main modules defines the time the customer can use the software before he has to activate it.
