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

Scenario

pplication Discovery

the

results of template is not the

same

on the target CMS as was on the

source

CMS

When does this happen

Templates o

n source

CMS are

defined to use a wild card (Any) for any of t

System Scope

fields

(Arch, OSver, OS type)

Solution

When the user perform DMT of AD and when the template does not provide the desired results the

following needs to be performed

for all

System Scope (Arch, OSver, OS type)

templates

Open the tem

plate in edit mode

Select the first entry in the drop down list for Arch

Save it.

Scenario

The export or import includes all products, only wanted HP

SIM data

When does this happen

By default the data migration tool will export installed products

using a set of XML configuration files.

The same applies to the import, on import both the export file and the set of installed components is

examined to pull the common set of data from the exported file.

Solution

It is possible to only import HP SIM dat

a, or export only HP SIM data. To do this navigate to the

installation directory and locate the config/migration folder.

Delete (or move to a new location) all

XML files except

hpsim_migrate.xml

for both the source and target CMS systems.