Eric's Technical Outlet

Learning the hard way so you don't have to

Problems with P->V of OEM Windows Server 2003

When virtualized, an OEM installation of Server 2003 will detect hardware changes and attempt to force activation before allowing you to log on. Unfortunately, most OEM keys have been deactivated at the licensing center, so this will usually fail. You cannot update the key to a retail or volume key, as they are actually different products.

The normal path to convert to a different key type is to run an upgrade or repair install from the different media type. This path has generally failed in my attempts. It appears that some security settings are applied at some level that prevents the virtual hard disk driver from being activated properly. This results in an 0x0000007b blue screen on the first reboot after an upgrade/repair attempt. Once the machine is in this state, I have not found any method of repairing it. Through trial and error, I found a few workarounds that avoided that particular stop error, but resulted in other problems that rendered the VM unusable. The most typical outcome was a complete inability to direct any keyboard or mouse input to the VM.

These problems may be unique to my particular environment. This domain has seen a long line of inheritance through many administrators, some more competent than others. I’ve found more than a few security settings that just don’t make sense, and it is possible that some survived my attempts to remove them.

The path I take to successfully virtualize these machines is as follows:

  1. Ensure you know the password for a local administrator account on the server.
  2. Move the physical server into a domain OU that blocks group policy inheritance.
  3. Run GPUPDATE /FORCE on the server.
  4. Download the SubInACL package to the server. You may also wish to copy the lines from step 15 into a batch file for easier processing later (don’t forget to remove the hyphens at the beginning of each line).
  5. Use SCVMM to convert the physical server to virtual; do not connect it to the network.
  6. Boot the virtual server into Safe Mode, using the local administrator account.
  7. Enter the following two commands at a command prompt:
    SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
    START DEVMGMT.MSC
  8. In Device Manager, go to the View menu and select “Show Hidden Devices”
  9. Remove any OEM devices and disk drives; especially focus on SCSI disks and controllers (for Dell, look for PERC). Also remove any Unknown devices.
  10. Back at the command prompt, enter the following two lines:
    REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service"
    NET START MSISERVER
  11. Go into Add/Remove Programs and uninstall Hyper-V Integration Services
  12. Use the Action menu in Hyper-V Manager to insert the Integration Services CD. Copy the files to a temporary folder on the virtual server.
  13. Insert the relevant Windows CD (Server 2003 R1 or R2, Volume or Retail) and run an upgrade installation. You may get a fatal COM error during the installation, but the install will complete.
  14. Once the upgrade has completed, install SubInACL if you haven’t already.
  15. Run the following commands at a command prompt:
    CD /D "%ProgramFiles%\Windows Resource Kits\Tools"
    SUBINACL /SUBKEYREG HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f
    SUBINACL /SUBKEYREG HKEY_CURRENT_USER /grant=administrators=f /grant=system=f
    SUBINACL /SUBKEYREG HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f
    SUBINACL /SUBDIRECTORIES %SystemDrive% /grant=administrators=f /grant=system=f
    SUBINACL /SUBDIRECTORIES %windir%\*.* /grant=administrators=f /grant=system=f
    SECEDIT /CONFIGURE /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose
  16. Reboot the server and install Integration Services from step 12.
  17. Restore the server to its original OU and reattach it to the network.
  18. If the server uses .Net, you will need to run a repair install on the relevant version and reboot.
Advertisements

3 responses to “Problems with P->V of OEM Windows Server 2003

  1. Niall Mullen December 12, 2014 at 12:31 pm

    Acronis not acromyms!! Bloody iPhone autocorrect!!!

    Like

  2. Niall Mullen December 12, 2014 at 12:29 pm

    I have done 2 P2V’s of 2003 server. both worked. First tried it with acronyms and concerted the .tib image to VMware and the other time used disk2vhd.

    Had a horrible experience trying to restore a 2003 DC with afailed RAID card by installing fresh from CD and retoring a system state. After applying the ntbackup system state it blue screened. Luckily had a repocixating DC and migrated the shares to that box. Also implemented DFS while I was at it.

    Like

  3. Pingback: Using Disk2VHD for Hyper-V P2V (Physical to Virtual) Conversions

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: