HP PART NUMBER: 461487-401A manual Preparing for a Windows server migration

Page 36

NOTE: Before uploading the SPPs, ensure that the destination server has a minimum disk space of 1 GB.

DevCon binary

When the DevCon binary is uploaded here before migration, it will be available when selecting additional migration options in the migration wizard. When DevCon is selected during migration, it is automatically installed at the end of Windows migrations. HP recommends that you use DevCon only if you face issues with mouse and keyboard devices on the destination server after a migration. For more information about DevCon or to download the executable, see http://support.microsoft.com/kb/311272 (or search for “DevCon” on the microsoft.com website.) Do not extract the binary that you download from the Microsoft website before uploading it here.

Preparing for a Windows server migration

The following sections list prerequisites for a Windows server migration.

If you use a firewall, see “Disabling firewalls” (page 20) .

Comply with all minimum prerequisites as listed in “Minimum source server prerequisites for all migrations” (page 35).

Windows source server prerequisites

For Windows migrations, verify that the following source server prerequisites are completed:

If Windows Server 2003 is installed, verify that the disks are initialized as MBR disks. Insight Control server migration does not support GPT-based disks.

During migration, the migration agent initiates an operating system reboot on the source physical server. Verify that the operating system is on the first boot order. Insight Control server migration supports migration of source servers that have operating systems installed on the primary drive (Hard Disk 0) and the primary drive loaded first in the boot order.

Record the drive letter or mount point to disk-partition mapping for dynamic disk partitions before you perform the migration. Any simple (non-extended) dynamic disk partitions are converted to basic disk partitions. You might have to manually reassign the mapped drive letters after the migration.

Before you migrate a source server with BitLocker Drive Encryption enabled and drives encrypted using BitLocker, decrypt the drives on the source server and disable BitLocker.

On the Windows source host, clear the Don’t allow exceptions check box under the General tab of the Windows Firewall section.

On the Windows source host, check the File and Printer Sharing check box under the Exceptions tab of the Windows Firewall section.

Source physical server prerequisites

If you are migrating from a physical source server, verify that the following prerequisites are completed:

36 Migrating the servers

Image 36
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 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 Preparing hardware for migration Verifying hardware and operating system supportVerifying system requirements for the application station 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 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 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