Filter
Top Products
Unable to boot Windows due to unsigned or corrupt drivers
Windows operating system does not boot after successful migration to any ProLiant Server in case
of unsigned or corrupt drivers.
Suggested action
To resolve this issue, perform one of the following:
• Manually remove any unsigned or corrupt driver from Source Server or from the Device
Manager.
• During a Windows boot, press F8 to select Disable Driver Signature Enforcement
mode.
• Use Windows recovery and browse the directory system32\drivers to remove any
unsigned or corrupt drivers.
Destination preparation
Destination server identification fails
The destination server identification fails in step 3 of the wizard.
Suggested action
Try the following:
1. Verify that the network adapter on the destination server is configured with a valid IP address,
subnet, and gateway.
2. Verify that the destination server is booted from the Insight Control server migration Boot CD
ISO and ready for migration.
3. Verify that the destination server can be reached from the application station and source
server. Communication on network ports 51125 and 51126 must be enabled by any firewall
between the CMS, the source server, and the destination server.
4. Verify that another Insight Control application is not already communicating with the destination
server.
IP address configuration fails on a manually booted virtual machine in Microsoft
Hyper-V for a P2V or V2V migration
You have manually created the virtual machine on Microsoft Hyper-V for a P2V or V2V migration
and booted the virtual machine manually with the Insight Control server migration Virtual Machine
Boot CD ISO. However, you cannot configure an IP address on the virtual machine.
Suggested action
Try the following:
• Ensure that the virtual machine that you have manually created has a legacy network adapter.
• Ensure that the legacy network adapter on the virtual machine is connected to the correct
virtual network switch on the host.
• Ensure that the Virtual network switch configuration on the Microsoft Hyper-V host is correct
and the virtual switch is connected to a physical network adapter with external network
connectivity.
Kernel panic occurs in booting a virtual machine to the Insight Control server migration
Virtual Machine Boot CD ISO
Insight Control server migration requires that the destination virtual machine has at least 1024 MB
of RAM to boot to the Insight Control server migration Virtual Machine Boot CD ISO.
54 Troubleshooting