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

Note:

Password must have a minimum of

eight

characters and must be

alphanumeric

Note:

A customized location can be provided to store the exported data. See the

export parameter table.

Note:

The source CMS must not e rebooted until import is completed. If the source

CMS is rebooted, it restarts the Insight Software services. As a preca

ution,

HP recommends setting the auto start mode for the services to manual. For

the list of services, see Appendix B: Stop order of services table column

Service Display Name

After a successful export operation, the default export file,

Products.zip

, is

created in

<HPSIM

install Path>

data

configdate

export

. For an example of a successful export operation,

see Figure 1.

Since changes made to the managed environment after the export is done are not part of the

exported file, the source CMS Insight Software

services must not be restarted to help ensure that no

changes are made from the source CMS. If changes are made after an export operation, HP

recommends rerunning the export utility. Failure to do so might result with the target CMS being out of

sync with

the managed environment. The export operation can be executed multiple times on the

source CMS. The export file is overwritten each time if the same file name is specified.

Note:

If version 6.0 or earlier of HP Insight Software is installed on the source

CMS, services need to be stopped manually. See

Data Migration of an

Existing MS Windows CMS to a new Insight Software 6.0

system for a list

of services to stop.

Figure 1: Console output of export execution

>mxexport

f Products.zip

: HP Insight Software Data Export Tool Launcher :