HP PART NUMBER: 461487-401A manual X2V postmigration tasks Windows

Page 45

X2V postmigration tasks (Windows)

After you complete a X2V migration, perform the following steps on the destination server:

1.If you manually booted the virtual machine by using the server migration Virtual Machine Boot CD ISO, disconnect the ISO and then manually reboot or shut down the virtual machine.

2.Add necessary network configurations to the migrated virtual machine guest. To do so, access the remote console for the destination virtual machine host to configure the network connections for the migrated virtual machine guest.

3.(Optional) Add a CD-ROM component to the destination virtual machine. The CD-ROM might be required to install additional Integrated Components.

After the virtual machine reboots, you must perform the following steps on the destination virtual machine guest for hypervisors:

1.Modify the system host name.

2.Install the proper guest tools.

3.Check the network connections and re-establish network connectivity. If an IP address conflict occurs when you are setting the static IP address, see the following website for more information:

http://support.microsoft.com/kb/269155/.

4.View the Windows event log on the destination server and disable any services or drivers that might have failed.

5.If applicable, reassign drive letters of dynamic disk partitions by using the disk manager to correspond with the original state. The virtual machine guest automatically detects new hardware and installs the required drivers.

6.The mouse and keyboard might not be immediately active on the migrated virtual machine guest. Wait until the guest operating system automatically installs all required drivers, and then reboot the migrated virtual machine guest when you are prompted.

7.Edit the boot.ini file. For more information, see “Editing the Windows boot.ini file after migration (Windows Server 2003)” (page 45).

Editing the Windows boot.ini file after migration (Windows Server 2003)

Edit the boot.ini file to activate a graphical boot process:

1.Remove the /bootlog and /sos options from the boot.ini file. These options are automatically inserted during the migration process so that the boot process is logged in detail for onscreen analysis. The active boot entry displayed during boot is highlighted, and the original boot.ini entry appears as HP Insight Control Preserved: [name], where

[name] is the operating system.

2.To retain the original boot parameters, copy all valid flags from the original entry and other appropriate boot flags as applicable, such as adding the /3GB flag (if the destination virtual machine is configured with sufficient RAM).

X2V postmigration tasks (Windows) 45

Page 44 Page 46
Image 45
Page 44 Page 46
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 Server migration introduction Installing and configuring server migration softwareOverview Related productsRight configuration Server migration concepts Migration checklistServer migration components Overview of migrating a serverMigration screen HP Insight Control server migration software tabsHP 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 Verifying licenses for software to be migrated Preparing software for migrationMigration security Disabling firewallsInstalling Service Pack for ProLiant Installing ProLiant Support PacksDisabling antivirus software Generating static or dynamic certificatesPreparing software for migration 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 Removing guest toolsDeploying 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 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 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 Installing Service Pack for ProLiant after migration Installing ProLiant Support Packs after migrationPostmigration tasks X2P postmigration tasks WindowsX2V postmigration tasks Windows Edit the boot.ini file to activate a graphical boot processX2V postmigration tasks Linux X2P postmigration tasks LinuxValidating the migration Viewing migration logsValidating Linux migrations Validating Windows migrationsPart IV Troubleshooting and support Troubleshooting User interfaceServer 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 wizardUnable 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 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 Subscription service How to contact HPSupport and other resources Information to collect before contacting HPRelated information HP authorized resellersDocuments WebsitesRelated 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
Top Page Image Contents