Microsoft KB Archive/937227

= 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 =

Article ID: 937227

Article Last Modified on 10/31/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
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:

Stop 0x0000007B



CAUSE
This issue occurs when the physical computer does not load the  registry subkey when the computer starts. Instead, the physical computer loads a different subkey, such as.



RESOLUTION
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  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:  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:  Click Start, click Run, type regedit, and then click OK. In Registry Editor, locate the following registry subkey:

 Note the value of the Current registry entry and the value of the Default registry entry. These values will match.  In Windows Explorer, locate the following folder:

%Systemroot%\Program Files\Microsoft VSMT\P2V\

</li> Right-click ServiceDriver.xml, point to Open With, and then click Notepad.</li> In the file, replace each instance of &quot;ControlSet001&quot; 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 &quot;ControlSet001&quot; with &quot;ControlSet002.&quot;</li> Click Save to save the changes.</li> In Windows Explorer, locate the following folder:

%Systemroot%\Program Files\Microsoft VSMT\P2V\ \Patches

</li> Right-click Storage.xml, point to Open With, and then click Notepad.</li> In the file, replace each instance of &quot;ControlSet001&quot; based on the value that you noted in step 1c.</li> Click Save to save the changes.</li> Repeat steps 8 and 9 for the following files: <ul> StorageSCSI.xml</li> Uniproc.xml</li></ul> </li></ol>

Keywords: kbtshoot kbexpertiseinter kbprb KB937227

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.