HP PART NUMBER: 461487-401A manual Suggested action

Page 67

Reinstall the mouse and keyboard drivers by using one of the following methods:

Reinstall the PSP.

Update the drivers in Device Manager.

Confirm that all of the following criteria are met:

The source server has a PS/2 mouse and keyboard.

The destination server has a USB mouse and keyboard.

The destination mouse and keyboard do not work.

Then, use the following procedure:

1.Attach a USB mouse and keyboard (by using a USB or PS/2 dongle) to the source server.

2.On the source server, resolve any devices that display a yellow exclamation point (!) in Device Manager (if any). Verify that the mouse and keyboard function on the source server.

3.Attach a USB mouse and keyboard (by using a USB PS/2 dongle) to the destination server.

4.Perform a P2P migration without using the PSP.

5.Install the latest Microsoft Service Pack on the destination server.

6.Install the latest PSP on the destination server.

7.Remove the (dongle-attached) USB mouse devices and keyboards from the source and destination servers.

Mouse does not work on the iLO of the destination server after a Linux X2P migration

The mouse does not work on the iLO of the destination server after a Linux X2P migration.

Suggested action

Deselect high–performance mouse mode on the remote console of destination server iLO.

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.

Suggested action

Use the following procedure:

1.Log on to the destination server by using the keyboard.

2.Press the Windows Key+Pause/Break to open System Properties.

3.Use the arrow keys or Tab key and the Enter key to open Device Manager.

4.In Device Manager, use the arrow keys or Tab key to move to VMware Pointing device, and then press the Application key. Click Uninstall. The VMware Pointing Device entry disappears from the list of devices.

5.Use the arrow keys to move to any selection of the Device Manager list, press the Application key, and then select Scan for hardware changes. A PS/2 compatible–mouse appears in Device Manager.

Drive letters are not the same in the migrated virtual machine guest after migration

The drive letters on the migrated virtual machine guest are not the same after migration.

Suggested action

Depending on the operating system, perform the following task:

Postmigration 67

Image 67
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Related products Installing and configuring server migration softwareServer migration introduction OverviewRight configuration Overview of migrating a server Migration checklistServer migration concepts Server migration componentsMigration screen HP Insight Control server migration software tabsHP Insight Control server migration software tabs Part II Premigration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying system requirements for the application station Planning the migration Resizing Linux file systems Disabling firewalls Preparing software for migrationVerifying licenses for software to be migrated Migration securityGenerating static or dynamic certificates Installing ProLiant Support PacksInstalling Service Pack for ProLiant Disabling antivirus softwarePreparing software for migration Part III Migration Preparing a Microsoft Hyper-V source server Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Verifying Linux source server requirementsDeploying Agents Removing guest toolsChoosing server migration Agents Deploying server migration AgentsNavigate to server migration Source Agent Server migration agent install screen Navigate to server migration Source Agent Linux Source Agent screen Virtual machine hosts PrerequisitesLinux destination size requirement Physical destination serversBooting the destination server ILO boot prerequisites Manually creating and booting a virtual destination serverPrerequisites for VMware ESX migration Page Minimum source server prerequisites for all migrations Migrating the serversIf you use a firewall, see Disabling firewalls Preparing for a Windows server migrationSource virtual machine prerequisites Preparing for a Linux server migrationSource physical server prerequisites SAN migrations in Windows Starting the migration wizard Launching server migration by using the Deploy menuIdentify the source server Launching server migration by using Quick LaunchQuick Launch Starting the migration wizard X2P postmigration tasks Windows Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration Postmigration tasksX2V postmigration tasks Windows Edit the boot.ini file to activate a graphical boot processX2V postmigration tasks Linux X2P postmigration tasks LinuxValidating Windows migrations Viewing migration logsValidating the migration Validating Linux migrationsPart IV Troubleshooting and support User interface TroubleshootingServer migration wizard hangs HP SIM Source server identification fails Source preparationLinux Source Agent window does not appear on Rhel 64-bit Migration Agent deployment failsPerform any one of the following on the source server Incorrect LUN size is detected in of the migration wizardDestination preparation Unable to boot Windows due to unsigned or corrupt driversDestination server identification fails Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Large volumes fail with a server thread error Drivers cannot be installed or injected onto a boot diskMigration process 2011/03/14 141934 The job failed Migration hangs if the source server is shut downReiserFS volumes are blocked for Linux migration Ntfs resize error message appearsMigration fails during the disk cloning phase SAN-connected destination server displays a blue screen Error occurs during data copy of Linux migrationHP Smart Array B320i controller name is not displayed Destination server boots with an invalid IP addressPostmigration Linux migration to servers with iSCSI storage fails to bootHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Guest OS ID guest name is not valid Server is unresponsive during PSP installation Multiboot kernel must be loaded before modules Suggested action Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesWebsites HP authorized resellersRelated information DocumentsRelated documentation Typographic conventionsTIP Documentation feedback Applying old server migration standalone licenses Basic hardware design of a three-node duster Premigration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter