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

9
2.
Obtain
the number of users
.
Go to
Options

S
ecurity

Users and Auth
orizations
.
3.
Count the number of scheduled tasks
. Go to
Tasks and L
ogs

Scheduled tasks
.
4.
Review the set of collections
. Go to
the l
eft navigation pane
,
and select
C
ustomize
to view all
collections and
the
details.
Note:
Command line interfaces are a go
od way to validate nodes. For instance,
you can export node lists with mxnode
–
lf and save it off to compare post
migration.
Step 3: Undeploying the existing Shared Resource Domains
Required migration pre
-
export actions for gWLM:

Undeploy all Shared Reso
urce Domains.
Note:
If the import cannot be completed and the source CMS must be used again,
steps 3, 4a and 5 above must be undone. See steps 12 and 9 in the post
import operations section.
Step 4
: Reconfigur
ing
Insight Control server deployment agents
This first step may be skipped if the source and target CMS are configured to use the same IP address
and host name
.
Before shutting down the source CMS, the deployment agents must be reconfigured to
interact with the target CMS.
To reconfigure the agents
:
1.
On the source CMS,
s
elect the desired servers in the server deployment console.
2.
Right
-
click
,
and select
Change Agent Settings

Production Agent
.
3.
Enter
the IP address of the target CMS so agents will connect to the
target
CMS.
As the deployment agents on th
e servers selected above connect to the target CMS, the selected
servers will be added to the deployment console.
If you have customized
deployment
jobs on the source CMS, you
must
export the jobs from the source
CMS
for later
import
to
the target CMS.
To
export your custom jobs on the source CMS:
1.
In the deployment console, select the desired jobs for export
2.
Right
-
click
your mouse
,
and
then select
Export…
3.
Specify a name for the exported job file
.
4.
Copy this exported job file
and any customized script files
t
o a safe location
.