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

:-:-:-:-:-:-:-:-:-: HP Insight Software Data Import Tool Launcher :-:-

:-:-:-:-

:-:-:-:-:-:-:-:-:-:-:-:-:-:-:

:-:-:-:-:-:-:-:-:-::-:-:-:-:-:-:-:-:-::-:-:-:-:-:-:-:-:-::-:-:-:-:-:-:-:-

:-::-:-

:-:-:-:-:-:-:-:

Lookup HPSIM InstallPath (x86)

HPSIM InstallPath: C:\Program Files\HP\Systems Insight Manager

Lookup succeeded

Data encryption password:

Is database remote (y/n) ? y

The following steps are needed to perform only if the target CMS is

configured with a remote SQL server database.

1. The source CMS, target CMS, and the remote SQL server must be in the

same Windows domain.

2. The folder, configdata-import, under <HPSIM installation

directory>\Systems Insight Manager\data on the target CMS must be shared

with full permissions granted to the database server for the user running

the import tool. The share name must be the default, configdata-import

3. The SQL service account must be configured to run as a domain user or

administrator user that would have access to the configdata-import share

named above.

4. The xp_cmdshell must be enabled on the remote database.

a. For SQL 2005, open SQL Surface Area Configuration, select the

Database instance used for the installation, select xp_cmdshell and click

the check box to enable.

b. For SQL 2008, open Microsoft SQL Server Management Studio, select the

database instance used for install, then right click and select Facets.

Select 'Surface area Configuration' from the pulldown and set

XPCmdShellEnabled to true.

Have you followed the above steps (y/n) ? y

All HP Insight Software running services will be stopped.

Do you want to continue (y/n) ? y

All HP Insight Software services stopped successfully.

WARNING! Import wipes out all data from the database.

Do you want to proceed (y/n): y