HP Insight Control - Manual (Page 72)

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, re-run the migration and enable auto installation
of PSP with Static IP configuration, in Step 6 of the P2P or V2P migration wizard. After the
migration is complete, you can resolve this issue by deleting the ghost devices:
1. With Remote Desktop using the static IP address provided in Step 6 of the P2P or V2P
migration wizard, connect to the destination server.`
2. Open a command prompt on the destination server and enter the following:
set devmgr_show_nonpresent_devices=1
devmgr.msc
3. In the device manager select view, and then select Show Hidden Devices.
Look for ghost keyboard and mouse devices with a yellow or red sign.
4. Right click the ghost device, and then select uninstall.
5. Reboot the destination server.
Mouse does not work on the destination server's iLO after a Linux X2P migration
The mouse does not work on the destination server's iLO after a Linux X2P migration.
Suggested action
To resolve this issue, deselect High performance mouse mode on the remote console of destination
server iLO.
USB Mouse or Keyboard Drivers Not Loaded After a X2P Windows Migration
After a successful Windows migration, the mouse and keyboard drivers may 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.
Since these are plug and play devices, Windows automatically detects the devices and loads the
72 Troubleshooting