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

19
Step
8
: Restart
ing
the Insight
S
oftware
services on the target CMS
Start the services listed in Table 2 in the reverse order in which they were stopped.
Note:
The “
HP Application Discovery
“service has to restarted on
s
ource and
target
systems after
installation
Post import operation tasks
Step
1: Verify
ing
the import on the target CMS
HP
recommends
logging in
to the target
(
new
)
CMS to verify the data has successfully migrated.
V
erification of some key data on the target CMS can help ensure the migration was successful. If the
optional step to
r
ecord key data items under the
Exporting the source CMS configuration data
section
was performed, use the item counts that were recorded to
verify
the following after logging in
to the
target CMS as a user that has CMS
-
level admi
nistrator privileges
. If verification fails, attempt the
export and import processes again.
1.
Verify that
the All Systems system list is the same size as was on the source system.
Note:
If the target CMS was a managed system on the source, the count
might
b
e
one less.
2.
V
erify
that
users are the same
.
S
ee
Option
s

S
ecurity

Users and Authorizations
.
3.
Verify that
scheduled tasks appear correct
.
S
ee
Tasks and Logs

Scheduled tasks
.
Note:
For an upgrade, there
might
be more tasks than before.
4.
Verify
the set of collec
tions.
From the left navigation page, select
Customize
to view all
collections and
the
details to see if they appear corre
ct.
Note:
For an upgrade, more collections
might
exist than before.
Step 2: Verify
ing
SMTP settings on the target CMS
After a migratio
n to a new host, it is possible that the SMTP configurations need to be updated. Log
into the CMS console, select
Options

Events

Automatic Event Handling

E
-
mail settings
,
and verify
that the SMTP server is correct. If these settings are incorrect, automati
c event handling and the
emailing of reports
might
fail.