A.5 Updating Connected Components and Services

To update components and services:

1. (Conditional) If you are migrating the QDB, complete the following steps to update the primary management server and each secondary management server that connects to it:

   1. (Conditional) If you customized any management server port or persistent IOC settings, use the Windows Registry Editor to back up the following registry keys on the management server computer:

      On this type of operating system...	Back up...
      32-bit	HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AppManager\ 4.0\NetIQms\NetIQmc Port HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AppManager\ 4.0\NetIQms\Port HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AppManager\ 4.0\NetIQms\Unix Port HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AppManager\ 4.0\NetIQms\Config\Persistent IOC HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AppManager\ 4.0\NetIQms\Config\PIOC Map File Path
      64-bit	HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NetIQ\ AppManager\4.0\NetIQms\NetIQmc Port HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NetIQ\ AppManager\4.0\NetIQms\Port HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NetIQ\ AppManager\4.0\NetIQms\Unix Port HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NetIQ\ AppManager\4.0\NetIQms\Config\Persistent IOC HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NetIQ\ AppManager\4.0\NetIQms\Config\PIOC Map File Path

   2. From the AppManager\bin folder in the location where you installed the management server, type the following command to re-register the management server service:

      netiqms -r QDBms:QDB_name:Windows_or_SQL_account_user_name:password:SQL_Server_name\
      instance -ur -i

   3. Restore persistent IOC settings.

      For more information about restoring persistent IOC settings, see Restoring Persistent IOC Settings.

   4. (Conditional) If you have UNIX agents, restore the port setting that defines where the management server listens for communications from UNIX agents.

      For more information about restoring the port setting, see Restoring the UNIX Port Setting.

   5. Restore any registry keys you backed up.

   6. Start the NetIQ AppManager Management Server service (NetIQms).

2. (Conditional) If you are migrating the CCDB, on each QDB Control Center manages, complete the following steps to enable the QDB to connect to the restored CCDB:

   1. In Microsoft SQL Server Management Studio, right-click the QDB and select New Query.

   2. In the query window, type the following command, and then click Execute:

      UPDATE dbo.CC_CacheManager SET Name = 'new_CCDB_SQL_Server_name\instance' WHERE Name = 'old_CCDB_SQL_Server_name\instance'

3. (Conditional) If you are migrating the QDB and Control Center manages it, complete the following steps to update the QDB connection information in the CCDB:

   1. (Conditional) If Control Center uses SQL authentication to communicate with the QDB, configure the QDB with the same SQL Server user account and permissions.

   2. Log on to the Control Center console with an account that is a member of the Administrator group and has the db_owner database role for the QDB.

   3. On the Global Tasks tab of the ribbon, click Manage Repositories.

   4. Select the QDB, and then click Modify.

   5. Provide the following information, and then click OK:

      • Name of the SQL Server and instance, if applicable, that hosts the QDB

      • Name of the QDB

      • Whether to use Windows or SQL Server authentication

      • (Conditional) If you select SQL Server authentication, SQL Server account information

   6. Click Close to close the Manage Repositories window.

4. (Conditional) If you are migrating the CCDB, complete the following steps to update the command queue service:

   1. Use the Control Center console to add the Windows user account for the command queue service as a Control Center administrator.

   2. In Microsoft SQL Server Management Studio, right-click the CCDB and select New Query.

   3. In the query window, to clear the previous command queue service settings from the CCDB, type the following command, and then click Execute:

      delete from Property where Scope = 'cqs'

   4. On the command queue service computer, from the AppManager\Control Center\bin folder, open the NQCQS.exe.config file in a text editor.

   5. Under <appSettings>, change the value of the ServerName parameter to specify the SQL Server and instance that hosts the restored CCDB, and change the value of the DBName parameter to specify the restored CCDB name. For example:

      <appSettings>
        <add key="ServerName" value="MYSQLSERVER\INSTANCE1" />
        <add key="DBName" value="CCDB_name" />

   6. Restart the command queue service to apply the changes.

5. (Conditional) If you are migrating the CCDB, complete the following steps to update the Deployment Service:

   1. (Conditional) If the Deployment Service will use different credentials or a different account to log on to the migrated CCDB, from the AppManager\Control Center\bin folder on the Deployment Service computer, issue the following command to change the account:

      deploymentservice -setwindowsauth domain\user_name password

   2. Use the Control Center console to add the Windows user account for the Deployment Service as a Control Center administrator.

   3. On the Deployment Service computer, from the AppManager\Control Center\bin folder, open the DeploymentService.exe.config file in a text editor.

   4. Under <appSettings>, change the value of the ServerName parameter to specify the SQL Server and instance that hosts the restored CCDB, and change the value of the DBName parameter to specify the restored CCDB name. For example:

      <appSettings>
        <add key="ServerName" value="MYSQLSERVER\INSTANCE1" />
        <add key="DBName" value="CCDB_name" />

   5. Restart the Deployment Service to apply the change.

6. (Conditional) If you are migrating the CCDB, complete the following steps to update the Deployment Web Service:

   1. Use the Control Center console to add the Windows user account for the Deployment Web Service as a Control Center administrator.

   2. On the Deployment Web Service computer, from the AppManager\Control Center\web folder, open the Web.config file in a text editor.

   3. Under <appSettings>, change the value of the ServerName parameter to specify the SQL Server and instance that hosts the restored CCDB, and change the value of the DBName parameter to specify the restored CCDB name. For example:

      <appSettings>
          <add key="ServerName" value="MYSQLSERVER\INSTANCE1">
      <add key="DBName" value="CCDB_name" />

   4. Restart the World Wide Web Publishing Service to apply the change.