New Configuration Policy is available in CA Client Automation R14 to Lock the Hostuuid

book

Article ID: 40621

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

Issue/Introduction

Introduction:  

Client Automation assigns each managed computer a CA Technologies-specific Universal Unique Identifier (UUID). It is stored on each computer at the following locations:

x32 Windows registry:      HKEY_LOCAL_MACHINE\Software\ComputerAssociates\HostUUID
x64 Windows registry:      HKEY_LOCAL_MACHINE\Software\Wow6432Node\ComputerAssociates\HostUUID
Linux/UNIX:               /etc/cadmuuid                                   


The Hostuuid can change if any of the following items changes:

Virtual machine :     System ID (a system BIOS attribute) is the only characteristic checked by the algorithm.

Physical computer: 

   ? MAC address compliance  -    If one of the MAC addresses does not match with one of the original MAC addresses of the target.

   ? Hard disk serial number compliance  - If one of the Hard Disk serial numbers does not match with one of the original hard disk serial numbers of the target.

   ? System ID compliance   -  If the System ID does not match with the original System ID of the target.

 

Question:

   How do I lock the Hostuuid for some or All agents.

 

Environment:   

  CA Client Automation R14                                       

 

Answer:

In previous version you could lock the hostuuid by the following steps:

 Windows:        Create a string value LockHostUUID with value “1”, under the registry key HKLM\Software\ComputerAssociates\HostUUID.

 Linux/UNIX:   Create a file named /etc/calockuuid.

 

The new way to do it in  CA Client Automation R14:  

Once you have installed R14, there will be a new Configuration Policy created under : Default Computer Policy\DSM\Agent      

Lock the host UUID of agent                 Set to TRUE    

<Please see attached file for image>

Config Policy.jpg           

 

You can either update the Default configuration Policy and then it will update all machines.

OR

You can create a Custom Policy and only apply it to a single machine or Group.   

 

  

Additional Information:         

TEC493519 - How to create a Custom Configuration Policy                



Environment

Release:
Component: BITCM

Resolution

Please Update This Required Field

Attachments

1558700078908000040621_sktwi1f5rjvs16k15.jpeg get_app
1558700076957000040621_sktwi1f5rjvs16k14.jpeg get_app