Cause
There could be bad blocks on the source or destination disk.
Suggested action
Insight Control does not support migrations of disks with bad blocks. If the bad block is on the destination disk, change the destination disk.
SAN-connected destination server displays blue screen
Suggested action
To migrate Windows Server 2003 to a
•Service Pack 1
•Service Pack 2
•Updated Storport storage driver (see http://support.microsoft.com/kb/932755)
Out of memory error occurs on the application station during migration
The Insight Control application station requires a minimum of 1024 MB of free memory for Insight Control migrations.
Suggested action
If an Out of memory error occurs on the application station during migration, you must free memory or add memory to the application station and then restart the migration.
Destination server boots with an invalid IP address
After a P2P migration, the destination server may boot with an invalid IP address (for example, 169.x.x.x), instead of using the IP address that was configured through the migration wizard.
Cause
This issue occurs if the destination IP address configuration fails or Dynamic Host Configuration Protocol (DHCP) is not enabled in the network. Whenever a NIC is added to the server, then by default the NIC is assigned an IP address using the DHCP configuration. If there is no DHCP server configured on the network, then the server will boot with an invalid IP address.
Suggested action
After the P2P migration is complete, manually configure the IP address on the destination server. Refer to the specific operating system documentation help files for specific instructions on performing this task.
Windows server migration Source Agent or PINT remote deployment fails with Agent is already deployed or not required error
When you remotely deploy the Windows server migration Source Agent or PINT from the Insight Control server migration application station or from Systems Insight Manager, the server migration Source Agent deployment fails with the error Agent is already deployed or not required. In addition, no logs are generated for the agent deployment under the <server migration installation folder>\log\AgentLogs\hp\log\source IP\ folder.
Migration process 59
