Data migration of an existing Microsoft Windows CMS to a new Insight Management 7.0 system

49
Scenario 10: After data migration, provisioning fails during OS
deployment step
Note:
This problem occurs only if the deployment server is configured in the same
CMS that has been migrated.
After migrating data from a CMS to another CMS with a different IP address, Infrastructure
Orchestration templates that reference deployment servers (such as Insight Control server deployment,
HP Server Automation, and Ignite-UX) are still valid and published. However, provisioning using these
templates fails with the following error:
Task for Logical Server logical-server-name has failed. Logical server
job completed with a failure status. Failure: Deployment server
credentials not found.
After data migration to a CMS with a different IP address, open a command prompt and enter the
following commands to register the deployment servers in your environment using the new IP address:
Insight Control server deployment
mxnodesecurity –a –p dsc_rdp –c username:password -t on -n ipaddress of
IC server deployment server
Ignite-UX
mxnodesecurity –a –p dsc_ignite –c username:password -t on -n ipaddress
of Ignite server
HP Server Automation (SA)
mxnodesecurity –a –p dsc_sas –c username:password -t on -n ipaddress of
SA server
VMware Auto Deploy (AD)
mxnodesecurity -a -p dsc_custom -c username:password -t on -n ipaddress
of VMware AD server
Currently the data migration tool migrates all the credentials (such as username), hence it is better to
check the credentials before adding or modifying it and remove the incorrect/invalid ones, if
necessary.
Use the following command to check if the existing users are valid.
C:\Program Files\HP\Systems Insight Manager>mxnodesecurity –l
Listing all global credentials...
NODENAME PROTOCOL USERNAME PASSWORD
@default1 snmp public private
Listing all system credentials...
NODENAME PROTOCOL USERNAME PASSWORD TRYOTHERS
IPADDRESS18 sign-in Administrator ******** Yes
IPADDRESS19 dsc_sas administrator ******** No