Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/924393

From BetaArchive Wiki
Knowledge Base


When you use Automated Deployment Services (ADS) on a Microsoft Windows Server 2003-based computer to deploy a Sysprep image to a virtual machine, the virtual machine may stop responding

Article ID: 924393

Article Last Modified on 10/3/2006



APPLIES TO

  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)



SYMPTOMS

On a Microsoft Windows Server 2003-based computer, you use Automated Deployment Services (ADS) to deploy a Sysprep image to a virtual machine. Then, the deployed virtual machine may stop responding at the startup screen. When you restart the virtual machine in safe mode, it will stop responding when the Acpitabl.sys file name is displayed on the screen.

CAUSE

This issue may occur if the hardware abstraction layer (HAL) version of the Sysprep image is set to Multiprocessor. A virtual machine only supports the Uniprocessor HAL version.

RESOLUTION

To resolve this issue, you must create a Sysprep image that is set to the Uniprocessor HAL version.

WORKAROUND

To work around this issue, follow these steps:

  1. Install Virtual Server 2005 Migration Toolkit (VSMT) on the ADS server.

    Note To obtain VSMT, visit the following Microsoft Web site:
  2. Open ADS Management on the ADS server, and then click the Devices node in the left pane.

    Note If the virtual machine has been removed from ADS, you would have to add the virtual machine as an ADS device.
  3. Right-click the device entry, and then click Properties.
  4. Click to select boot-to-da in the Default job template list, and then click OK.
  5. When the status of the device entry displays Connected to DA in the ADS Management console, right-click the device entry, and then click Run job.
  6. Click Create a one-time job on the Job Type page, and then click Next.
  7. Click Task Sequence on the Command Type page, and then click Next.
  8. When you are prompted to provide the task sequence file, click Browse, and then locate the following folder:

    C:\Program Files\Microsoft VSMT\Patches\Source\

    Under this folder, you will find the following subfolders, depending on the operating system and the service pack that the Virtual Server 2005-based computer is running.

    • Microsoft Windows NT with Service Pack 6 (SP6)
      The subfolder is named 4.0.1381. Under this subfolder, you will see a subfolder named SP6. Open the SP6 subfolder, and then select Uniproc.xml.
    • Microsoft Windows 2000 with Service Pack 3 (SP3) or with Service Pack 4 (SP4)
      The subfolder is named 5.0.2195. Under this subfolder, you will see a subfolder that is named SP3 or SP4. Open the subfolder that corresponds to the appropriate service pack, and then select Uniproc.xml.
    • The original release version of Windows Server 2003 or Windows Server 2003 with Service Pack 1 (SP1)
      The subfolder is named 5.2.3790. Under this subfolder, you will see a subfolder that is named SP1. If the computer is running Windows Server 2003 with Service Pack 1 (SP1), open the SP1 subfolder, and then select the Uniproc.xml file. If the computer is running the original release version of Windows Server 2003, open the 5.2.3790 subfolder, and then select the Uniproc.xml file.
  9. Run the job for the device.
  10. As soon as the job finishes, set the device in the virtual machine to use boot-to-hd as the default job template, and then restart the virtual machine.

Note The Sysprep image that contains the post-SP1 hotfixes for Windows Server 2003 SP1 or the post-SP4 hotfixes for Windows 2000 SP4 will update the Ntoskrnl.exe file or the Ntkrnlpa.exe file. If this is the case, make sure that you include the updated file in the corresponding subfolder for the operating system. For more information about how to include these hotfixes in VSMT, see the VSMT Help file.

STATUS

This behavior is by design.

Keywords: kbexpertiseadvanced kbtshoot kbprb KB924393