Data migration of an existing MS Windows CMS to a new Insight Software 6.0 system

23
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 1
3
: Reinstall
ing
and reconfigur
ing
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 6.0 Installation and Configuration Guide for
Microsoft Windows
.
Step 14: Updat
ing
bookmarks
1.
Not
ify 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
.
Scenarios not supported

The source and target CMS (Including the datab
ase server) having different login credentials.

Importing to a clustered CMS environment. Currently the export and import utility are not
supported for a clustered CMS installation.

The source CMS running with Insight
S
oftware
v
3.
x
/6.0 and target CMS runni
ng only
standalone HP SIM.

The source CMS running with standalone HP SIM and target CMS having Insight
Control
or
Insight Software v
3.x/6.0 installed.

The source CMS as a 64
-
bit system and the target CMS as a 32
–
bit system.

If you have issues activating a
Logical Server after the import,
see
the LSM Troubleshooting
guide
.

HP I
nsight Dynamics recovery management
currently has a limitation that job information is not
migrated to the
target
CMS.
Therefore,
the jobs TAB of HP I
nsight Dynamics recovery
managemen
t
will be empty after migration
.

The target
CMS
system
must
not be one of the managed
system
s
of the source CMS
, and
instead must be a NEW system. Deleting the target system from the source CMS will not work if
the target system was ever licensed for any p
roduct. Licensing
what will be the
target
CMS system
on the source CMS (even if it is then deleted before running DMT) may allow for multiple licenses
for that target
system
for the same product.
Insight Software components that do not support migration

I
nsight Remote Support
Remote support data will need to be re
-
configured on the target CMS, for instance, all systems
needing remote support will need to be re
-
imported.

VCRM uses a separate migration tool
. Therefore,
it does not support migration described
in this
document.

RDP does not support data migration
, some manual steps were listed in this paper that will
assist in migrating RDP jobs and scripts
.

VPM, Version and Patch Management migration is not supported in Insight
S
oftware v6.0 and
is not support
ed by data migration.