HP Virtual Connect Enterprise Manager Software - Manual (Page 41)

9 Post-migration tasks
Installing ProLiant Support Packs after migration
If you performed a Windows X2P migration, and you did not upload the Windows PSP executable
from the Upload Drivers tab prior to migration, then you must manually install the HP ProLiant
Support Pack (PSP) after a migration on the destination server.
You can configure Insight Control server migration to automatically install a PSP after the Windows
migration is completed on Step 6 of the migration wizard, Additional Migration Options. To use
this feature, you must upload the Windows PSP executable from the Upload Drivers tab in the
migration wizard prior to starting a migration.
For more information about required post-migration configurations, see “X2V post-migration tasks
(Windows)” (page 41) .
X2P post-migration tasks (Windows)
NOTE: For migration of domain controller source, post migration steps will be disabled.
After you complete a P2P migration, perform the following steps on the destination server:
1.
Log in with administrative rights.
2. At each of the Welcome to the Found New Hardware wizard screens, click Cancel.
3. When prompted to reboot the system at the System Settings Change Window, click No.
4. Install the latest PSP (if this option was not selected during the P2P installation).
5. View the Windows event log on the destination server and disable any services or drivers that
might have failed.
6. If necessary, verify the network connections. If NIC teaming is required on the destination
server, then NIC teaming must be re-established on the destination server after the migration
and installation of the PSP.
7. If the source and destination servers must be on the network at the same time:
a.
Change the host name of either server or consider reconfiguring the applications.
b. If the IP addresses are static, reassign them.
8. (Optional) Reassign drive letters to former dynamic disk partitions.
9. (Optional) Convert basic disks to dynamic disks. During migration, all dynamic disks are
migrated to the destination server as basic disks. Therefore, if dynamic disks are preferred on
the destination server, then basic disks can be manually converted back to dynamic disks.
10. Edit the boot.ini. For more information about editing the boot.ini, see “Editing the Windows
Boot.ini file after migration (Windows Server 2003)” (page 42)
11. If the Windows license is not a volume license, then reactivate it.
12. The mouse and keyboard might not be immediately active after the migration. Wait until all
required drivers are automatically installed by the guest operating system, and then reboot
when prompted.
X2V post-migration tasks (Windows)
After you complete a P2V migration, perform the following steps on the destination server:
1.
If you manually booted the virtual machine 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 destination virtual machine host remote console to configure the network connections for
the migrated virtual machine guest.
Installing ProLiant Support Packs after migration 41