Data migration of an existing Microsoft Windows CMS to a new Insight Management 7.0 system

5. Copy any customized deployment script files from the safe location to the appropriate locations on

the target CMS.

If the deployment server is remote, you will need to change the location where HP SIM looks for the

deployment server.

1. Open a command prompt and run mxnodesecurity –l to list the deployment server IP

address. If this address is correct you can stop here.

2. To change the IP address used by HP SIM for the deployment server, type the following in the

same command window:

a. mxnodesecurity -r -p dsc_rdp -n <rdp-ip> to delete the old deployment server IP

address where <rdp-ip> is the IP address of the deployment server.

b. mxnodesecurity -a -p dsc_rdp -c username:password -n <rdp-ip> to add

the new deployment server IP back in with the user name and password necessary to access

that server.

Step 13: Reinstalling and reconfiguring Insight Remote Support

Insight Remote Support Advanced must be reinstalled and reconfigured on the target CMS. For more

information, see the HP Systems Insight Manager 7.0 Installation and Configuration Guide for

Microsoft Windows.

Step 14: Acquiring a new CA certificate for Target CMS

If the source CMS had a CA-signed certificate,and if the source CMS/target CMS are two different

servers with different names/IP addreses, then request a new CA certificate from a certificate

authority (CA).

Step 15: If this is a secondary CMS migration, perform the following operations

1. Log in to the primary CMS in the federation that the migrated secondary CMS is part of.

2. Stop the HP Matrix infrastructure orchestration windows service.

3. Remove the source CMS from the federated CMS list using SIM Federated Configuration.

4. Add the target CMS to the federated CMS list using SIM Federated Configuration.

5. Open a prompt window, go to <IO_installed_directory/support> and run the

following script:

a. fix_fqdn_dmt.pl – f <input_file>

6. Start the HP Matrix infrastructure orchestration windows service.

For details on how to run the fix_fqdn_dmt.pl script, see Appendix G: Running

fix_fqdn_dmt.pl script.

Step 16: Updating bookmarks

1. Notify users that bookmarked URLs to the source CMS will no longer be valid after migration to the

target CMS.

2. Provide new links to the target CMS; for example, https://<newcmsname>:50000

Step 17: Registering deployment server with new IP address.

After migrating data from source CMS to target CMS with a different IP address, IO templates that

reference deployment servers (such as Insight Control server deployment, HP Server Automation, and

Ignite-UX) are still valid and published. However, provisioning using these templates fails with the

error Task for Logical Server logical-server-name has failed. Logical

server job completed with a failure status. Failure: Deployment server

credentials not found.