The Activation Limit is used to provide hardware locking for protected software. By tying a license to a specific hardware profile the protected software can only be installed on the number of machines that you allow.
See Hardware Locking and the Activation Process for details.
When DeployLX validates a license the current state of the licnese is resolved to one of three states.
The license has been activated and the current hardware profile is similar (within the defined tolerance) to when it was activated.
The license has not been activated or the hardware has changed more than allowed.
If there are no child State limits that target the Unactivated state then validation fails. Otherwise the activation limit defers to the child limits.
The child limits of the Unactivated state have expired as well.
If there are no child State limits that target the Unactivated Expired state then validation fails. Otherwise the activation limit defers to the child limits.
The ASP.NET templates are appended to the ASP.NET response when the license has not been activated. The form includes instructions for activating the license online or by phone or email.
During the grace period both the header and footer templates will be used. After the grace period has expired the entire ASP.NET response is replaced with the footer template.
The email template is used when by the activation form when generating an email request to customer service.
The forms may be customized or completely replaced to fit your specific application style.
See the How to Create a Custom Form topic for details on replacing or customizing the form.