Maintenance Expiry Dates

The maintenance periods for Licence Services will expire over time, requiring fresh maintenance keys to extend the maintenance. In the event of a License Server failure, or when licenses are moved to another server, maintenance details must be updated on the License Server to ensure that the maintenance dates of your Datamine applications are correct.

All maintenance license keys must be registered in sequence when licenses are moved, in order to ensure that software has the correct maintenance dates. The is illustrated below:

Time	Event	License Installed	Maintenance Starts	Maintenance Expires
First year of ownership 01/01/2009	Software Purchase	Full license	01/01/2009	01/01/2010
Second year of ownership 01/01/2010	Maintenance Paid	Maintenance license for1 year (ML1)	01/01/2010	01/01/2011
Third year of ownership 01/01/2011	Maintenance Paid	Maintenance license for1 year (ML2)	01/01/2011	01/01/2012

To move a license to a new server during the first year of software ownership, the dongle must be transferred to the new server, and the full license key for the software must be registered on that server.
Similarly, to move the license to a new server during the second year of software ownership, the dongle must be transferred to the new server, and the full license key for the software must be registered on that server. In addition, the maintenance key (ML1) must also be registered in order to update the maintenance period.
The third year (and later) of ownership is where confusion may arise: after transferring the dongle, and registering the full software license you must first register ML1, and then ML2 in order to update the maintenance period. This is because a maintenance key expects to find a specific "maintenance expires" date. ML1 requires an expiry date of 01/01/2010 and ML2 requires an expiry date of 01/01/2011. Consequently, if ML2 is applied immediately after the software key, it will find the wrong date, and it will fail.