HP Virtual Connect Enterprise Manager Software manual Hidusb.sys Hidkbd.sys Mouhid.sys

Page 61

NOTE: After successfully using DevCon during a migration, Windows Device Manager may show yellow exclamation points (!) next to duplicate keyboard and mouse entries. Right click on the device with the yellow exclamation point and update the driver. The device should be rediscovered and changed from an unknown device to be an HID device. Devices which cannot be rediscovered using this method are duplicates and can be uninstalled using the right-click menu.

To attempt to solve the mouse and keyboard issues without restarting the migration, see “USB Mouse or Keyboard Drivers Not Loaded After a X2P Windows Migration” (page 61)

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 drivers. In some scenarios, the USB keyboard and mouse drivers may 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

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

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

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

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

1.Upload the latest ProLiant Support Pack 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 following migration. Enter any static IP addresses required. If a static IP address is not provided, DHCP will be assumed default.

Once logged into Remote Desktop of destination server, check to see if the proper mouse and keyboard drivers are installed on the destination server. To do this, do one of the following:

Verify if the mouse and keyboard appear as Unknown in the Device Manager and have no drivers listed

Verify if the server has the following files:

Hidusb.sys

Hidkbd.sys

Mouhid.sys

Post-migration 61

Image 61
Contents HP Insight Control Server Migration 7.0 User Guide Legal Notices Contents Migrating the servers IV Troubleshooting and supportPost-migration tasks ISO Contents Contents Applying old server migration standalone licenses Support and other resourcesGlossary Index Part I Overview and concepts Server migration introduction Installing and configuring server migration softwareOverview Related productsProduct Description Server migration concepts Migration checklistServer migration components Overview of migrating a serverMigration screen HP Insight Control server migration software tabsServer migration concepts Part II Pre-migration tasks Verifying hardware and operating system support Preparing hardware for migrationVerifying application station system requirements Planning the migration Resizing Linux file systems Verifying licenses for software to be migrated Preparing software for migrationMigration Security Disabling firewallsDisabling antivirus software Installing ProLiant Support PacksGenerating static or dynamic certificates Part III Migration Verifying Windows source server requirements Preparing the source server and deploying the Source AgentVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverChoosing server migration Agents Uninstalling guest toolsDeploying server migration Agents Deploying AgentsNavigate to server migration Source Agent Server migration agent install dialog Navigate to server migration Source Agent Linux Source Agent screen Linux destination size requirement PrerequisitesPhysical destination servers Virtual machine hostsBooting 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 migrationPreparing for a Linux server migration SAN migrations in Windows Starting the migration wizard Launching server migrations using the Deploy menuVerify Source Physical server Quick Launch Launching server migrations using Quick LaunchAvailable operations Post-migration tasks Installing ProLiant Support Packs after migrationX2P post-migration tasks Windows X2V post-migration tasks WindowsX2P post-migration tasks Linux Edit the boot.ini file to activate a graphical boot processViewing migration logs X2V post-migration tasks LinuxValidating the migration Validating Linux migrationsPost-migration tasks Part IV Troubleshooting and support User interface TroubleshootingSource preparation Server migration wizard hangsMigration Agent deployment fails Source server identification failsSuggestion action Linux Source Agent window does not appear on Rhel 64-bitIncorrect LUN size detected in of the migration wizard Destination preparationDestination server identification fails Suggested action CD ISO Auto booting destination physical server fails Manually migrate these disks after a successful migration Large volumes fail with server thread error Drivers cannot be installed or injected onto boot diskMigration process Java.lang.OutOfMemoryError Java heap space ReiserFS volumes are blocked for Linux migration Ntfs resize error messageMigration hangs if source server is shut down Migration fails during the disk cloning phase Error during data copy of Linux migration SAN-connected destination server displays blue screen Destination server boots with an invalid IP addressPerform one of the following Post-migrationHidusb.sys Hidkbd.sys Mouhid.sys Suggested action Drives do not appear on the migrated operating system Server is unresponsive during PSP installation Destination virtual machine fail to boot after X2V migrationReboot the server and then reinstall PSP manually Support and other resources How to contact HPInformation to collect before contacting HP Documentation feedback HP authorized resellersRelated information Related documentation Typographic conventionsTIP Applying old server migration standalone licenses Basic hardware design of a three-node duster Pre-migration consideration steps for clustersPost migration considerations and steps Performing the migrationPost migration considerations and steps Glossary Index Index SIM Websites