Duplicate Bootserver entries

Products

• CA Client Automation - IT Client Manager
• CA Client Automation
• CA Client Automation - Software Delivery

Issue/Introduction

It is possible to cause duplicate entries in the database for the same Bootserver in the CSMDB tables of the MDB.

This can cause some unexpected issues when the wrong Bootserver record is looked up.

Example:

• Can't read additional parameter file:
  \\...CA\DSM\Server\SDBS\var\managedpc\images\dosboot\parms\180373E25F95.dat: No such file or directory
•  Error : OSM010014: The OS Image is not available on the boot server:xxxxxxxx.   But image is clearly available on the boot server Image Library.
• OS Image is displayed in the SS OS Image library but when trying to select it has a red x and cannot be selected
• Boot server listed multiple times in the boot server selection pane of OS Installation Wizard
• Boot server listed multiple times in the "Move Computer to Boot Server" Dialogue.

Environment

Client Automation - All Versions

Cause

When there is a duplicate entry in the mdb the wrong record is being referenced, This record does not have the links to associated images and PC's and thus produces errors when actions are attempted

Resolution

Identify and remove duplicate boot server records:

Step 1. Identify the incorrect record

• Log a support case and request T1ED253
• On Domain Manager: apply the test fix T1ED253 ( Please note this test fix is version independent) 
• Change into folder  ...CA\DSM\bin
• Run the command:
  • ccsmcmd listbootserver -u<user> -p<password>
    
    • This will show the two boot server entries
      • <bootserver>
      • <bootserver>
        
        
• On the running Scalability Server run the commands

  1. caf setcomputername %computername%temp
  2. caf stop
  3. caf start
     
     
• on Domain Manager run the command to list the bootservers again:
  • ccsmcmd listbootserver -u<user> -p<password>
    
    1. This will now show
       1. <bootserver>
       2. <bootservertemp>
          
          
• The incorrect entry is now identified as it has not changed with renaming of the Scalability Server.
• It is possible to use a script to run step 1D if there are many SS to rename.

If you receive the message “This setting cannot be changed because it is controlled by DSM Policy” on Step 1D above, you need to change this to locally managed in configuration policy.

1. Create a new config policy that can be applied to all Scalability servers
2. In this policy expand DSM\Agent
3. Right Click on "Use Operating system name for this agent" and choose "Setting" "Locally Managed"
4. Seal and apply this policy to your Scalability Servers and you can now run the “caf setcomputername” command

 

Step 2. Remove the duplicate records: 

1. Delete the "old" boot server <bootserver> by running the command:
   • ccsmcmd deletebootserver -n <bootserver> -u<user> -p<password>

 

Step 3. Rename Scalability Server back to desired name

1. On the Scalability server run the commands
   1. caf setcomputername <bootserver>
   2. caf stop
   3. caf start