Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.3 system

Step 6: Configure Insight Dynamics Global Workload Manager property file
This step can be skipped if you are not using the CMS to manage gWLM nodes. Users of Insight Dynamics
Global Workload Manager must perform several additional steps. For complete information, see the Insight
Dynamics Global Workload Manager 6.3 Users Guide.
1. In multi homed networks, ensure gWLM property
com.hp.gwlm.security.virtualLocalHostName=<SIMvirtualserverIP> in file
~\Virtual Server Environment\conf\gwlmagent.properties has the correct
SIMvirtualserverIP.
Where SIMvirtualserverIP is virtual server IP address of HPSIM.
If <SIMvirtualserverIP> is missing or is not HPSIM virtual server IP, add/modify it to be the IP
address of the HPSIM virtual server.
2. Ensure both forward and reverse DNS is setup for Insight Dynamics Global Workload Manager
managed nodes, for example:
a. If DNS does not resolve targets, put entries in the target CMS hosts file located at
~\Windows\System32\drivers\etc\ for Insight Dynamics Global Workload
Manager managed nodes.
b. Put entries in the managed nodes /etc/hosts files for the CMS.
Step 7: Post-Import HP Insight Orchestration Configuration
This step can be skipped, if HP IO is installed on source and target node at the same path.
The following script should be executed in the target CMS node after importing data successfully.
fix_sysprep_dmt.pl
The fix_sysprep_dmt.pl script updates the IO database entries and updates sysprep references after the
import operation is performed in the target CMS.
Before executing the script, please ensure that,
- Download fix_sysprep_dmt.pl script from
ftp://ftp.hp.com/pub/softlib2/software1/pubsw-windows/p395312722/v72832
- SQLCMD Tool installed on the target CMS
- A username created in DBMS with access to the IO database (it can be the same user used
by IO)
Steps to execute fix_sysprep_dmt.pl in target CMS after import:
1. Stop the “HP Insight Orchestration” Windows service
2. Backup the database ‘hpio’ from the source cms sql instance
3. Open a command prompt :
o Navigate to <Virtual_Server_Environment_install_directory>\lbin.
o Type perl fix_sysprep_dmt.pl [-s SERVER] [-p PORT] [-i
INSTANCE] [-u USERNAME] [-w PASSWORD]
If no parameters are supplied, the script assumes local database, default instance and port, and credentials
from logged user.
Where:
- SERVER – Database server
o The hostname or IP address of the remote database.