Moving HP SIM 5.x to a new Windows system (441289-003, January 2009)

14
<
HP SIM Install Folder
>
\
config
\
discovery
\
hosts
And
<
HP SIM Install Folder
>
\
config
\
discovery
\
templates
Note:
The above files are available in a system only if templates and host files were created in HP
SIM. If the host files or templates were never crea
ted on a CMS, the specified folders are not present.
WBEM Indication configuration
To ensure that WBEM events are received correctly, reinitialize the WBEM subscription by executing
mxwbemsub
to each of the managed systems with WBEM providers installed. Fo
r example:
mxwbemsub
a
n <Managed systems with WBEM providers installed>
Configuration settings
Copy the
globalsettings.props
and
nodesecurity.xml
files from the source CMS and paste
it under the corresponding folder on the target CMS. The
globalsetting
s.props
and
nodesecurity.xml
files are located under the same location for both source and target systems:
<HP SIM Install Folder>
\
config
\
If required, go to
<HP SIM Install Folder>
\
config
\
from the target system
.
Open
globalsettings.props
file using Notep
ad. Update the CMS device key in
globalsettings.props
according to the device key value in the database.
Go to
Control Panel
Administrative Tools
Services
and restart the
HP SIM
service.
WMI Mapper configuration
The target CMS will have the source CMS as
the mapper proxy host. Change the WMI mapper proxy
host with the target CMS.
1.
Sign in to HP SIM on the target CMS system with administrative privileges.
2.
Go to
Options
Protocol Settings
WMI Mapper Proxy
3.
Select the existing mapper proxy host and click
Delet
e
4.
Click
New
and type in the target CMS name or IP address and click
OK
5.
Run Identification task on managed systems with WBEM providers installed.
Migrating trusted system certificates from the source CMS to the target
CMS
1.
Sign in to HP SIM on the source CM
S system with administrative privileges.
2.
Select
Options
Security
Certificates
Trusted Certificate.
3.
Select a certificate and click
Export
.
4.
Save the certificate locally.
5.
Repeat steps 3 and 4 for all the certificates listed in
Trusted System Certificates
page
.