HP PART NUMBER: 461487-401A manual Drives do not appear on the migrated operating system

Page 68

1.Open Windows Disk Management.

2.Correct the incorrect letter assignment in the migrated virtual machine guest by 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.

Suggested action

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 by using the appropriate disk administrator or manager.

Mouse and keyboard do not work after a Microsoft Hyper-V virtual machine is migrated to a ProLiant server

Suggested action

If the mouse and keyboard do not work after you migrate a Microsoft Hyper-V virtual machine to a ProLiant server, reboot the destination server.

If rebooting does not solve the issue, try the following:

Remove Microsoft Hyper-V Integration Tools on the source virtual machine before you perform a migration.

Rerun the migration, but select Automatic PSP installation in the migration wizard so that the PSP is installed automatically on the destination server after a migration.

Rerun the migration, but select Use DevCon in the migration wizard so that DevCon is installed automatically on the ProLiant server at the end of the 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.

Suggested action

For more information, see the following website:

http://support.microsoft.com/kb/269155/en-us

Virtual machine hosts Integrated Components that are not installed on the destination virtual machine after migration

Suggested action

Try the following:

1.Power down the destination virtual machine.

2.Add a CD-ROM drive to the virtual machine.

3.Power up the virtual machine, and then restart the installation of the Integrated Components.

68 Troubleshooting

Image 68
Contents HP Insight Control Server Migration 7.2 User Guide Legal Notices Contents Postmigration tasks IV Troubleshooting and supportMigrating the servers Contents CD ISO Contents Support and other resources Glossary Index Part I Overview and concepts Installing and configuring server migration software Server migration introductionOverview Related productsRight configuration Migration checklist Server migration conceptsServer migration components Overview of migrating a serverHP Insight Control server migration software tabs Migration screenHP Insight Control server migration software tabs Part II Premigration tasks Verifying system requirements for the application station Preparing hardware for migrationVerifying hardware and operating system support Planning the migration Resizing Linux file systems Preparing software for migration Verifying licenses for software to be migratedMigration security Disabling firewallsInstalling ProLiant Support Packs Installing Service Pack for ProLiantDisabling antivirus software Generating static or dynamic certificatesPreparing software for migration Part III Migration Preparing the source server and deploying the Source Agent Verifying Windows source server requirementsVerifying Linux source server requirements Preparing a Microsoft Hyper-V source serverRemoving guest tools Choosing server migration AgentsDeploying 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 Prerequisites Linux destination size requirementPhysical destination servers 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 Installing ProLiant Support Packs after migration Installing Service Pack for ProLiant after migrationPostmigration tasks X2P postmigration tasks WindowsEdit the boot.ini file to activate a graphical boot process X2V postmigration tasks WindowsX2P postmigration tasks Linux X2V postmigration tasks LinuxViewing migration logs Validating the migrationValidating Linux migrations Validating Windows migrationsPart IV Troubleshooting and support Server migration wizard hangs TroubleshootingUser interface 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 serverDestination server identification fails Unable to boot Windows due to unsigned or corrupt driversDestination preparation Migration might appear If expected volumes do not appear, try one of the following Automatic booting of the destination physical server fails Suggested action Migration process Drivers cannot be installed or injected onto a boot diskLarge volumes fail with a server thread error 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 How to contact HP Subscription serviceSupport and other resources Information to collect before contacting HPHP authorized resellers Related informationDocuments 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