ProLiant servers running Microsoft Windows NT Server 4.0 that have been migrated may not Function

[Jennifer Bacco_1]

DESCRIPTION
ProLiant servers running Microsoft Windows NT Server 4.0 that have been migrated using the HP ProLiant Essentials Server Migration Pack physical-to-virtual machine (P2V) or virtual-to-virtual machine (V2V) migration do not start the base Remote Procedure Call (RPC) Service. All services that rely on this service do not work therefore, the server is not operational. Networking is not available, nothing is operational except login, logout and shutdown.

During the migration, the registry key for the Hardware Configuration HKEY_CURRENT_CONFIG\System is purged. The following minimum set of subkeys must be present:

HKEY_CURRENT_CONFIG\System
HKEY_CURRENT_CONFIG\System\CurrentControlSet
HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control
HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class
HKEY_CURRENT_CONFIG\System\CurrentControlSet\Enum
HKEY_CURRENT_CONFIG\System\CurrentControlSet\Services

All services in the active Hardware Configuration are considered to be deactivated if the above keys are absent.

Note: The HP ProLiant Essentials Server Migration Pack extends the functionality of the HP ProLiant Essentials Virtual Machine Management Pack to provide integrated physical-to-virtual machine (P2V) and virtual-to-virtual machine (V2V) migrations. The Server Migration Pack simplifies server consolidation process.

P2V machine migration enables migration of a physical machine to a virtual machine guest within a Microsoft® Virtual Server or VMware virtual machine host.

V2V machine migration enables migration of a virtual machine guest between virtualization layers, including Microsoft Virtual Server 2005, VMware ESX Server, and VMware GSX Server.

For additional information on the HP ProLiant Essentials Server Migration Pack refer to the HP ProLiant Essentials Server Migration Pack User Guide located at the following URL:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00306314/c00306314.pdf

SCOPE
Any ProLiant server that has been migrated to Microsoft Windows NT Server 4.0 using the HP ProLiant Essentials Server Migration Pack physical-to-virtual machine (P2V) or virtual-to-virtual machine (V2V) migration.

RESOLUTION
To perform the migration, adapt the migration profiles either by manually editing them or by exchanging them:

To manually adapt the migration profiles, perform the following:
On the CMS where VMM & SMP is installed, locate the directory \bin\profiles
Edit the three files GSX.xml, ESX.xml and Virtual Server.xml and locate the following entries:


delete
SYSTEM\CurrentControlSet\Hardware Profiles\0001\System\


Replace with the following:


delete
SYSTEM\CurrentControlSet\Hardware Profiles\0001\System\CurrentControlSet\Services\s3\



OR

To exchange the migration profiles, perform the following:
On the CMS where VMM & SMP is installed, locate the directory [vmm install directory]\
bin\profiles.
Replace the three files (ESX.xml, GSX.xml, and Virtual Server.xml) with the three files (ESX.xml, GSX.xml, and Virtual Server.xml)
(see the attachment)
For servers that already have been migrated, perform the following:

With Notepad.exe create the file hwfix.reg with the following content and merge the fix content with the registry.

--- begin hwfix.reg ---
REGEDIT4
[HKEY_CURRENT_CONFIG\System]
[HKEY_CURRENT_CONFIG\System\CurrentControlSet]
[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control]
[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class]
[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Enum]
[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Services]
--- end hwfix.reg ---

[Jennifer Bacco_1]

2nd attachment (GSX.xml)

[Jennifer Bacco_1]

3rd attachment (Virtual Server.xml)