A migrated virtual machine image may not start successfully, even when all the scripts run successfully on a Microsoft Windows Server 2003-based computer that is running Automated Deployment Services

Consider the following scenario:

• You have a Microsoft Windows Server 2003-based computer that is running Automated Deployment Services (ADS).
• On this computer, you use Virtual Server 2005 Migration Toolkit (VSMT) to migrate a physical computer onto a virtual machine image.

In this scenario, the virtual machine may not start successfully, even though all the scripts run successfully. Additionally, you may receive the following Stop error after the virtual machine starts:

This issue occurs when the physical computer does not load the HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001 registry subkey when the computer starts. Instead, the physical computer loads a different subkey, such as HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue, use Registry Editor to examine the HKEY_LOCAL_MACHINE\SYSTEM\Select\Current registry subkey. Determine the value of the Current registry entry and the value of the Default registry entry. Then, change the VSMT scripts before you perform the migration. To do this, follow these steps:

1. Before you run the VSMT scripts on the physical computer, use Registry Editor to determine the value of Current registry entry and the value of the Default registry entry. To do this follow these steps:
   1. Click Start, click Run, type regedit, and then click OK.
   2. In Registry Editor, locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\Select
   3. Note the value of the Current registry entry and the value of the Default registry entry. These values will match.
2. In Windows Explorer, locate the following folder:
   %Systemroot%\Program Files\Microsoft VSMT\P2V\MachineName
3. Right-click ServiceDriver.xml, point to Open With, and then click Notepad.
4. In the file, replace each instance of "ControlSet001" based on the value that you noted in step 1c.
   
   For example, if the value that you noted in step 1c is 0x00000002, replace each instance of "ControlSet001" with "ControlSet002."
5. Click Save to save the changes.
6. In Windows Explorer, locate the following folder:
   %Systemroot%\Program Files\Microsoft VSMT\P2V\MachineName\Patches
7. Right-click Storage.xml, point to Open With, and then click Notepad.
8. In the file, replace each instance of "ControlSet001" based on the value that you noted in step 1c.
9. Click Save to save the changes.
10. Repeat steps 8 and 9 for the following files:
    • StorageSCSI.xml
    • Uniproc.xml