After Renaming a Scalability Server, when deploying software to agents which report to that SS I get the error message "Unable to update sourcelist on Scalability Server"

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

Description:

After making a Scalability Server name change, when deploying software to agents which report to that SS, I get the error message "Unable to update sourcelist on Scalability Server".

• This happens even after changing the name of the Scalability Server the agents report to on the agent side.
  
  
• The actual installation of the software completes but reports back to the DM as a failure
  
  
• The TRC_USD_SDMSIEXE* logs will show the error
  
  ERROR | CMsiLibDct <ServerName> is invalid/unaccessable

NOTE: This issue will only occur if the Software Delivery Shares (SDMSILIB and SDLIBRARY$) exist before the name change is performed.

Solution:

To resolve this error you should remove the old 'SDLIBRARY' and 'MSILIB' shares (SDLIBRARY$ and SDMSILIB) and add them again, so the shares will now use the new SS hostname/FQDN

1. First remove the shares by running..

   sd_sscmd removeshare SDLIBRARY sd_sscmd removeshare MSILIB

2. Then add the shares again by running..

   sd_sscmd addshare SDLIBRARYsd_ssmcd addshare MSILIB 

3. Then try the deployments again.
   
   
4. If the problem persists, please set DETAIL tracing on the agent by running

   cftrace -c set -l DETAIL -s 50000

Then reproduce the problem, open an issue with Support and provide the TRC_USD* logs from the Agent's %sdroot%\..\logs direc

Environment

Release:
Component: BITCM