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

10
Note:
OS administrative privileges are required for the signed in user on the
source CMS.
Configuring the target CMS for migration
To avoid a loss of data,
complete the steps defined in the Exporting the source CMS configuration
data section before proceeding with the setup process for the target CMS.
If the source CMS uses a remote database, then the data from the remote database is extracted as
part of the
export process. After the export operation has completed, the remote database can then
be reconfigured for use with the target CMS.
IMPORTANT:
If the target CMS is to be the same physical system as the source CMS, you
must complete the export process on th
e CMS before installing and
configuring the target CMS.
Note:
The target CMS cannot be the same physical system as the source CMS
when the target CMS is a cluster CMS.
Step 1: Selecting new host name and IP address for a new system as the
target CMS
The ta
rget CMS requires a new operating system which includes configuring a new host name and IP
address within the OS.
Step 2: Optional. Upgrading memory and firmware on the target CMS
system
Verify hardware requirements for Insight Software 6.2 at
http://www.hp.com/go/insightsoftware/docs
and ensure the new CMS is properly configured.
Step 3: Installing and pre
-
configuring the target CMS
1.
Install a supported version of Windows operating system that meets In
sight Software requirements
on the target CMS.
The target system must not have
the
UTC system time set earlier than the source. For example,
ensure the system time is synchronized for the source and target CMS.
The target CMS OS must be the same locale as
the source CMS.
The target CMS must either be on the same LAN as the source CMS, or it must have access to all
of the managed systems reachable by the source CMS.
The target CMS must have the same DNS configuration settings as the source CMS. At a
minimum,
the target CMS must be able to resolve the same set of forward and reverse DNS
lookups supported by the source CMS.