Scenarios for the manual deactivation of licenses - Johnson Controls - Metasys - LIT-12012392 - Software Application - Software Licensing - 3.0

Branch License Manager License Portal Help

Brand
Johnson Controls
Metasys
Product name
Software Licensing
Document type
User Guide
Document number
LIT-12012392
Version
3.0
Revision date
2020-10-30
Language
English

License deactivation after the system ID changes

If a machine's system ID changes, you cannot complete the deactivation of any licenses that were activated for the machine's old system ID. In this case, you must contact Johnson Controls sales support and request the licenses to be manually deactivated to make them available for reuse. The following scenarios provide examples where this is necessary.

  • Operating System (OS) change: After installing and licensing software, the machine is re-imaged with a different OS without first deactivating the software license. Request manual deactivation to use the license on the same machine with a different OS, or on a different machine.
  • Hardware failure: After installing and licensing software, the machine's hard-drive or motherboard failed and was replaced. Request manual deactivation to use the license on the repaired machine or on a different machine.
  • Virtual machine configuration changed: After installing and licensing software on a virtual machine, the VM's Disk ID or UUID is changed without first deactivating the software license. Request manual deactivation to use the license on the reconfigured VM or another machine.
  • Virtual machine moved to a new host: After installing and licensing software on a virtual machine, the VM is moved to a different physical machine. Request manual deactivation to use the license on the moved VM.

License deactivation when the machine is unavailable or non-operational

If a machine becomes unavailable or is no longer operational, you cannot complete the deactivation of any licenses on that machine. In this case, you must contact Johnson Controls sales support and request the licenses be manually deactivated to make them available for reuse. The following scenarios provide examples where this is necessary.

  • Theft or loss of machine: After installing and licensing software, the machine is stolen or lost. Request manual deactivation to use the license on a replacement machine.
  • Virtual machine deleted: After installing and licensing software on a virtual machine, the virtual machine is deleted without first deactivating the software license. Request manual deactivation to use the license on a different physical or virtual machine.

License deactivation when the license is not listed in the Software Manager

If a license is not listed in the License Inventory within the Software Manager, you cannot complete the deactivation of that license. This occurs if the machine's system ID has changed or if the Software Manager cannot access the license data, because it was deleted, moved, or otherwise lost.

For the case where the Software Manager cannot access the license data but the machine's system ID is still the same, you can add a license back into the License Inventory by reactivating it on the same machine without deactivating first. This makes the license available for deactivation. For example, you may need to do this if you uninstall the Software Manager and then reinstall it in another location on the same machine.

For the case where the system ID changed, see License deactivation after the system ID changes.