HP Insight Foundation Software for ProLiant - Manual (Page 65)

Migration of Windows 2008 or Windows 2012 from Physical Server—> Physical
Server—> Physical Server, results in blue screen error.
When Windows 2008 or Windows 2012 OS is migrated using SMP to a Physical Server and the
same Server-OS is migrated to another Physical Server, the destination windows results into blue
screen error during boot up.
Suggested action
Use DISM 6.3 on CMS for this type of migration.
Migration does not start after confirmation. The event log continuously displays
Operation Migration waiting for connection to source
When the migration starts, the source server reboots and runs the migration agent in exclusive
mode during migration.
Rebooting the source machine might take a few minutes. If this process takes a long time, verify
that the source machine is rebooted with the migration agent running in exclusive mode. The source
machine might be waiting for user input during the reboot. Another possibility is that the boot order
is incorrect.
If the migration agent is deployed on an operating system that is not first in the boot order, the
migration agent might fail to boot to the Insight Control mode.
Suggested action
Change the boot order by editing boot.ini, and verify that the operating system on which Insight
Control is deployed is first in the boot order.
Destination server mouse and keyboard do not work after a Windows migration
The mouse and keyboard might not be operational immediately on a destination server after a
migration.
Suggested action
To detect and activate the mouse and keyboard, reboot the destination server so that PnP correctly
detects and activates the mouse and keyboard.
If the mouse and keyboard still do not work, ensure that DevCon is installed and ready on the
Upload Drivers tab and then re-run the migration. Select Use DevCon in Step 6 of the P2P or V2P
migration wizard.
NOTE: After successful use of DevCon during a migration, Windows Device Manager might
show yellow exclamation points (!) next to duplicate keyboard and mouse entries. Right–click the
device that has the yellow exclamation point and update the driver. The device should be
rediscovered and changed from an unknown device to an HID device. Devices that cannot be
rediscovered through this method are duplicates and can be removed using the right-click menu.
To attempt to solve the mouse and keyboard issues without restarting the migration, see “USB
mouse or keyboard drivers are not loaded after an X2P Windows migration” (page 65) .
USB mouse or keyboard drivers are not loaded after an X2P Windows migration
After a successful Windows migration, the mouse and keyboard drivers might not be loaded. As
a result, the mouse and keyboard do not work on the destination server.
Cause
Insight Control does not inject any drivers for the USB keyboard or mouse on the target server.
Because these are plug–and–play devices, Windows automatically detects the devices and loads
the drivers. In some scenarios, the USB keyboard and mouse drivers might fail to load. Example
Postmigration 65