How do I update license files on customer machines when using license file aliases and/or EZTrial?
Posted by Zach C, Last modified by Tanner O on 14 November 2017 11:45 AM

Using Protection PLUS 5 SDK and activating through SOLO Server is the ideal way to update license files. After the initial activation, a user can simply perform a license refresh with SOLO Server to get the updated license data.

While License file aliases are highly effective tools for preventing a customer from re-installing a trial version of your application to gain additional time, they can, unfortunately, also make it somewhat difficult to perform legitimate License File updates manually. To avoid these issues, any changes to the license file should be made programmatically through a trigger code process or some other appropriate function.

License file aliases employ the last-used date and time fields to determine which copy is the most recent. This is why re-installing an application that has an old last-used date and time will have its data overwritten by the backup alias copy.  In order to force the application to use a new license file that was recently copied into the application directory, it is necessary for its last-used date and time to be LATER than the last date and time the application was executed.

When you create a license file in LFEdit, it automatically puts the LOCAL system date and time in the last used date and time fields of the license file. The last-used date and time fields do not compensate for time zone differences. If you ship this file to a customer in a time zone behind you and they immediately launch the application, it will think that the user turned the clock back. You can remedy this in one of the following ways:

  1. In LFEdit, click Tools / Options and uncheck the option "Set Last Used Date/Time to Current Date/Time at Save", create a new license file and change the Last Used Date on the Expiration Fields tab to be yesterday.
  2. Activate the customer with EZ Trigger Code 26 to reset the last used date and time to the current system date and time.
  3. Tell the user to wait a few hours before running the application. The application will automatically start running once their local time has reached the Last Used Date and Time.

Keep in mind that this applies to license files that are shipped and immediately used by a customer. If you post a trial version of your product on a website and a user in another time zone installs it, they will likely not have a problem because their date and time should be later than the date and time stored in the license file shipped with your trial.