Changing the IP address of an ON Command CCM, Symantec Patch Manager, ON iCommand, or Symantec LiveState Delivery server

Article:TECH108894  |  Created: 2004-01-10  |  Updated: 2005-01-01  |  Article URL http://www.symantec.com/docs/TECH108894
Article Type
Technical Solution

Issue



You need to know how to change the IP address of your ON Command CCM, Symantec Patch Manager, ON iCommand, or Symantec LiveState Delivery server.


Solution



Changing the IP address of an ON Command CCM, Symantec Patch Manager, ON iCommand, or Symantec LiveState Delivery server is not a critical problem when all connecting instances use name resolution (the recommended, and default behavior).
However, in many environments where name resolution is not reliable, the settings are often customized to use the IP address instead of the server name.

Windows Agent configuration changes

The Windows Agent default settings for the server contact method is name resolution, and is defined in the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\CSD\control\2.0\UseNameLookUp
This is a DWORD key that has a value of 0 or 1. If set to 0, the server IP address is used instead of using the server name when trying to connect to an ON Command CCM, Symantec Patch Manager, ON iCommand, or Symantec LiveState Delivery Server. The default value for this key is 1. This setting is for using name resolution.

The environment variables for DEPOT_SERV, HOME_SERV, and CONFIG_SERV are set using the IP address instead of the normal server name.

In environments where name resolution is not reliable and the settings have been changed to use the IP address instead of the server name, the new IP address must be distributed to the clients via an extended desktop agent configuration package before the server address is changed.

Remote Depot Connections configuration changes

This setting is only used when explicitly defined. Default depot server is the configuration server. Connections to remote or independent Depot structures other than the default ON Command CCM, Symantec Patch Manager, ON iCommand, or Symantec LiveState Delivery configuration servers is accomplished by using the server name registry key located at:

    HKEY_LOCAL_MACHINE\SOFTWARE\CSD\control\2.0\LocalServer
This is a STRING key that contains the alternate UNC path value for the server.

In environments where name resolution is not reliable and the settings have been changed to use the IP address instead of the server name, the new IP address must be distributed to the clients via an extended desktop agent configuration package before the server address is changed.

Pre-OS Options configuration changes

If you choose to use IP addressing over name resolution, you must change DHCP option 128, if defined, to the respective server IP address. You must also change the server listing in the Ccmlocator.lst file, if defined, to the server IP address. If you are using TFTP from this server, you may need to adapt an option 66 bootserver if the IP address is used.


Command Center connection parameters configuration changes

You only need to change the Command Center settings when IP addressing is used instead of name resolution. The same is true for the Depot Replicator tree configuration, the Package Import Tool, and other tools like CLI routines or ADK. The settings for MMC based tools are stored in the referenced MMC .msc file, and can be changed via the search and replace function of any convenient text editor. If you use this method of direct editing the .msc file, which is in XML format, it is highly recommended to make a backup copy of the file before you apply any changes to it.

BootP Server configuration changes

If this is a bootp server, you may need to adapt the Bootp.tab file if the server IP address is used.


Configuration changes for ODBC connections to a CCM server

If you design your own tools using ODBC access to the server, you may need to adapt the ODBC connection parameters if IP addressing is used instead of name resolution. See Configuring ODBC access to the Sybase CCM database.






Legacy ID



2004091012311760


Article URL http://www.symantec.com/docs/TECH108894


Terms of use for this information are found in Legal Notices