How to reassign licenses after a component change
ILS licenses are bound to certain attributes of the computer. Which attributes are used is configured with the license that insite issues - normally this will be a combination of IDs of certain hardware components and/or values of system settings of the computer (e.g. computer name, ID of network interface card, motherboard, harddisk, ...).
In ILS a "device" is identified by the values of certain attributes MINUS ONE!
So even if it is the same computer in the customer's view, it may be a different device for ILS. But what does "MINUS ONE" mean? If ILS detects a single deviation in one of these attribute values, the license will still be valid, or, in other words:
A deviation of a single attribute value is allowed and has no impact on the validity of the customer's license.
However, if ILS detects more than one deviation, the license will not be valid anymore. This is the case for the entire lifetime of the license.
A "real-life" example:
- insite has bound a license to three device attributes
- computer name
- motherboard id
- id of NIC (network interface card)
- Customer has licenses activated for the device and licensed applications run.
- Some time goes by and the computer is moved to another room and therefore gets a different name.
- The licensed applications still run, since only one device attribute differs from the configured license data.
- Later on, the NIC fails and the customer replaces the defect NIC with a new one.
- The licensed applications will not run anymore, since two device attributes differ now.
- In this case
- the customer could undo the renaming of the computer and the licensed application will run again, or
- the customer transfers the license to a new device.
In the latter case, the customer has to contact insite. It will be handled the same way as described in the scenario
How to transfer a license to a new computer.
References:
Main use case
Use cases TOC