Microsoft KB Archive/929162

= Up to 20 minutes may pass before the PXE starts on a client computer when you deploy Windows PE from a Windows Server 2003-based ADS server =

Article ID: 929162

Article Last Modified on 6/27/2007

-

APPLIES TO


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

-



SYMPTOMS
When you deploy the Windows Preinstallation Environment (Windows PE) from an Automated Deployment Services (ADS) server that is running Microsoft Windows Server 2003, up to 20 minutes may pass before the Pre-Boot Execution Environment (PXE) starts on the client computer.

Note This problem occurs most frequently on legacy-free systems that emulate an 8042 keyboard controller chip in the system's firmware. However, other hardware configurations may also exhibit this problem.



CAUSE
This problem occurs because the transfer of the RAM disk image takes 15 to 20 minutes.



RESOLUTION
To deploy this hotfix to the ADS server, install the hotfix on the server. Then, manually replace the Startnbs file in the repository folder for any pre-existing repositories.

Note Repositories that are created after you install the hotfix will use the updated Startnbs file. These repositories do not require any manual updates.

To manually replace the Startnbs file, follow these steps:  Open the following Microsoft ADS installation folder:

\tftproot\nbs\boot\x86

This folder contains the updated Startnbs file. Copy the updated Startnbs file to each repository folder in the following location:

\tftproot\nbs\boot\x86\



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
No prerequisites are required.

Hotfix replacement information
This hotfix does not replace a previously released hotfix.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about a similar problem that affects Windows Server 2003 RIS server, click the following article number to view the article in the Microsoft Knowledge Base:

906425 A PXE client computer is slow to start when you deploy Windows PE from a Windows Server 2003-based RIS server

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbfix kbhotfixserver kbqfe kbprb kbexpertiseinter KB929162

-

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

© Microsoft Corporation. All rights reserved.