HP Insight Control User Manual
Page 161
6.
Install the latest PSP on the destination server.
7.
Remove the (dongle-attached) USB mice and keyboards from the source and the destination servers.
Mouse does not work on the destination ESX virtual machine after a V2V migration
The mouse might stop working on the destination ESX virtual machine after a V2V migration. To resolve this
issue, use the following procedure:
1.
Log in to the destination server using the keyboard.
2.
Navigate to the Device Manager by right-clicking My Computer and selecting Manage.
3.
Right-click VMware Pointing device and select Uninstall. The VMware Pointing Device entry
disappears from the list of devices.
4.
Select Scan for hardware changes. A PS/2 compatible mouse appears in the Device Manager.
DNS error appears in the destination server after migration of domain controller
This error occurs when the static IP address is assigned to the NIC, which is not connected to the network
on the destination server. To correct this issue:
1.
Reconfigure the NIC connected to the network to accept a static IP address.
2.
Assign the same IP address to the NIC that the DNS server has.
3.
Restart the server.
Drive letters are not the same in the migrated virtual machine guest after migration
Depending on the operating system, perform the following task:
1.
For Windows Server 2003 systems, select Control Panel
→Administrative Tools→ Computer
Management
→Disk Management.
2.
Correct the incorrect letter assignment in the migrated virtual machine guest using the disk administrator
or manager.
Drives do not appear on the migrated operating system
After a successful migration, some migrated volumes do not appear in Windows Explorer.
Depending on the operating system, perform the following task to assign a driver letter to the volume so it
is visible in Windows Explorer:
1.
For Windows Server 2003 systems—Select Control Panel
→Administrative Tools→Computer
Management
→Disk Management, and then verify that the disk manager has initialized all disks.
2.
Assign the driver letter in the migrated virtual machine guest using the appropriate disk administrator
or manager.
Mouse and keyboard do not work after migrating a Microsoft Hyper-V virtual machine
to a ProLiant server
If the mouse and keyboard do not work after migrating a Microsoft Hyper-V virtual machine to a ProLiant
server, reboot the destination server.
If rebooting does not solve the issue, uninstall Microsoft Hyper-V Integration Tools on the source virtual
machine before performing a migration. If you cannot uninstall the tools, then select Automatic PSP
installation
on the destination server Migration Wizard so that the PSP is installed automatically on the
destination server after a migration.
Static IP address cannot be assigned on the destination server after migration
Assigning a static IP address on the destination server might result in an error similar to the following:
The IP address xxx.xxx.xxx.xxx you have entered for this network adapter is
already assigned to another adapter.
This scenario can occur if the IP address is assigned to a network adapter on the source server. For more
information, see
.
Post-migration
161