HP PART NUMBER: 461487-401A manual Hidusb.sys Hidkbd.sys Mouhid.sys

Page 66

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 66).

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 scenarios include a tampered source, a Microsoft Hyper-V VM source, or a migrated source that used PS/2 drivers.

Suggested action

Try the following:

•Reboot the destination server a second time after the migration. During the reboot, verify that Legacy USB is set to Enabled in the BIOS on the destination server. The PnP drivers should load automatically through the Hardware Setup Wizard.

•If the second reboot did not solve the issue, log on to the destination server by using Windows Remote Desktop to update the mouse and keyboard drivers.

NOTE: This solution will be successful only if Remote Desktop is enabled on the destination server and an IP address was configured with the migration wizard.

To use the server migration wizard to configure an IP address on the destination server, perform the following:

1.Upload the latest ProLiant Support Pack (PSP) supported by the source server to the Insight Control server migration Upload Drivers tab.

2.Select the option to reboot the destination server in step 6 of the migration wizard.

3.Select to install the PSP after migration. Enter any static IP addresses that are required. If a static IP address is not provided, DHCP will be assumed by default.

When you are logged on to Remote Desktop on the destination server, determine whether the proper mouse and keyboard drivers are installed on the destination server. To do this, do one of the following:

◦Verify that the mouse and keyboard appear as Unknown in Device Manager and have no drivers listed.

◦Verify that the server has the following files:

–Hidusb.sys

–Hidkbd.sys

–Mouhid.sys

66 Troubleshooting

Page 65 Page 67
Image 66
Page 65 Page 67
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents IV Troubleshooting and support Migrating the serversPostmigration tasks Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Overview Installing and configuring server migration softwareServer migration introduction Related productsRight configuration Server migration components Migration checklistServer migration concepts Overview of migrating a serverHP Insight Control server migration software tabs Migration screenHP Insight Control server migration software tabs Part II Premigration tasks Preparing hardware for migration Verifying hardware and operating system supportVerifying system requirements for the application station Planning the migration Resizing Linux file systems Migration security Preparing software for migrationVerifying licenses for software to be migrated Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksInstalling Service Pack for ProLiant Generating static or dynamic certificatesPreparing software for migration Part III Migration Verifying Linux source server requirements Preparing the source server and deploying the Source AgentVerifying Windows source server requirements Preparing a Microsoft Hyper-V source serverDeploying server migration Agents Removing guest toolsChoosing server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install screen Navigate to server migration Source Agent Linux Source Agent screen Physical destination servers PrerequisitesLinux destination size requirement Virtual machine hostsBooting the destination server Manually creating and booting a virtual destination server ILO boot prerequisitesPrerequisites for VMware ESX migration Page Migrating the servers Minimum source server prerequisites for all migrationsPreparing for a Windows server migration If you use a firewall, see Disabling firewallsPreparing for a Linux server migration Source virtual machine prerequisitesSource physical server prerequisites SAN migrations in Windows Launching server migration by using the Deploy menu Starting the migration wizardLaunching server migration by using Quick Launch Identify the source serverQuick Launch Starting the migration wizard Postmigration tasks Installing ProLiant Support Packs after migrationInstalling Service Pack for ProLiant after migration X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxValidating Linux migrations Viewing migration logsValidating the migration Validating Windows migrationsPart IV Troubleshooting and support Troubleshooting User interfaceServer migration wizard hangs HP SIM Source preparation Source server identification failsMigration Agent deployment fails Linux Source Agent window does not appear on Rhel 64-bitIncorrect LUN size is detected in of the migration wizard Perform any one of the following on the source serverUnable to boot Windows due to unsigned or corrupt drivers Destination preparationDestination 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 Drivers cannot be installed or injected onto a boot disk Large volumes fail with a server thread errorMigration process Migration hangs if the source server is shut down 2011/03/14 141934 The job failedNtfs resize error message appears ReiserFS volumes are blocked for Linux migrationMigration fails during the disk cloning phase Error occurs during data copy of Linux migration SAN-connected destination server displays a blue screenDestination server boots with an invalid IP address HP Smart Array B320i controller name is not displayedLinux migration to servers with iSCSI storage fails to boot PostmigrationHidusb.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 Support and other resources How to contact HPSubscription service Information to collect before contacting HPDocuments HP authorized resellersRelated information WebsitesTypographic conventions Related documentationTIP Documentation feedback Applying old server migration standalone licenses Premigration consideration steps for clusters Basic hardware design of a three-node dusterPerforming the migration Post migration considerations and stepsPost migration considerations and steps Page Glossary Index Page SPP Postmigration tasks Yellow bang ! appears on NIC adapter
Top Page Image Contents