How to prevent the Host UUID from changing on client automation systems when they are virtualised

Document ID : KB000028714
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem

When a system is virtualised some unexpected behaviour is noticed such as

  • causing an RAC job to be initiated
  • Scalability server components become unregistered
  • Manager become inoperable.

Environment

  • Any version of CA IT client Manager or CA Client Automation.
  • Any OS

Cause

When a system is virtualised the Hardware change causes the HostUUID to be recalculated

Solution

Follow the guidelines below and there should not be any issues with virtualising the systems

  1. Managers cannot change their name, not even the Fully Qualified Domain Name (FQDN). If the name is changed the Managers will suffer multiple issues. Changing the Name of a Manager System is not supported
  2. If a Manager or Scalability server changes it's IP then this must resolve correctly in DNS
  3. prevent the HostUUID from changing by locking it.
    • Windows
      • HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\HostUUID
        or
        HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\HostUUID
         
        and add the STRING
         
        LockHostUUID
        value =1
    • Unix \ Linux
      • Create a new file named "calockuuid" in the folder "/etc"
  4. Test the entire process in a sandbox environment before attempting this on a production system.
  5. Ensure you have a full Backup as per the Client automation Backup and restore green books