HP Virtual Connect Enterprise Manager Software manual Source server identification fails

Cause

Some versions of Windows Server 2003 that are pre-installed by HP cannot be migrated successfully unless corrective action is performed before attempting the migration. Affected systems are detected by the server migration Source Agent during initialization. If the system is affected, instructions for performing the corrective action are provided. If you attempt the migration without first performing the corrective action, your destination server becomes non-bootable.

NOTE: The server migration Source Agent will not detect whether the corrective action has already been performed. Subsequent attempts to execute this agent will indicate that corrective action is still required. However, the corrective action needs to be applied only once.

Suggested action

Resolution

1.Cancel the migration agent execution.

2.In the command prompt window, change to the root directory of the Windows disk.

3.Run the following command: SFC /SCANNOW. This command might take several minutes. For more information about this command, see the following website:

http://support.microsoft.com/kb/310747/en-us

Source server identification fails

The source server identification fails during the first step of the migration wizard.

Suggested action

1.Verify the identifier entered. If the name is entered for a source server that is in a domain, be sure that the Fully Qualified Domain Name (FQDN) is entered.

2.Verify that the migration agent has been installed on the identified source server. For more information about running the migration agent, see the Insight Control server migration online help.

3.Verify that the source server can be reached from the application station. Communication on network ports 51125 and 51126 must be enabled by any firewall between the application station and the source server.

4.Verify that the agent status messages do not indicate that the source server is locked to another server.

Migration Agent deployment fails

The migration Agent might fail deployment for several reasons, including:

•Incorrect password

•Reserved ports

•Insufficient disk space

•Network issues

•Special characters in the source password like colon (:), quotes (“), or backslash (\)

•The source server is inside a VPN and the CMS is outside the VPN

•Missing 32-bit libraries on 64-bit Linux source server

Source preparation 47