In above example standard licensing diagram we have two programs (Program 1, 2), two clients (Client 1, 2) and three orders (Order 1, 2, 3) defined in activation center. Client 1 has two orders (Order 1 for Program 1 and Order 2 for Program 2) and Client 2 has single Order (Order 3 for Program 2). Two licenses are granted for Order 1 and single license is granted for Order 2 and Order 3.
Above web licensing example diagram shows two different programs (Program 1, 2) in ACEN. Two licenses are granted per serial number for Program 1 and single license is granted per each serial number for Program 2 in above example. Serial numbers are generated in PC Guard and distributed to end users after purchase. No client nor order entries are required in web licensing model. End users are identified with serial number.
Supported protection scenarios
Number of granted web licenses per serial number is defined in ACEN Program settings (valid values: 1-100, default value: 1). By default, single license is granted per single serial number. Multiple licenses can be granted per single serial number.
By default, custom features stored inside serial number will be used for generation of activation code. If no feature is set in serial number, default program features will be used.
Demo mode can be combined with all protection scenarios. Application will initially work in demo mode and will not require activation until demo period is over.
License removal feature is available only in case limited license feature is disabled. If license removal is enabled, web license can be removed by end user by selecting "Remove license" radio button on activation dialog and by clicking on "Continue >>" button. License will be removed from both local machine and from activation center. If computer if off the Internet at the time of license removal only local license will be removed. License in ACEN will stay active in this case. Next time it is run, protected application will automatically try to activate (reactivate) license on that computer.
By default, expiration date for each web license will be based on default validity period, fixed date limitation and day of the month limited license settings in Activation center.
When reactivating or transferring (standard model only) web license, expiration date, custom features and custom counters from original web license will be used for new web license instead of default program settings. Expiration date, custom features and custom counters of original web license can also be changed in Activation center by administrator user at any time. Next time web license is reactivated, transferred or validated by license validation task, updated data will be used for new web license.