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

Consider the following scenario. You deploy the Windows Preinstallation Environment (Windows PE) from a Remote Installation Services (RIS) server. This RIS server is running Microsoft Windows Server 2003. You perform this deployment to trigger a Pre-Boot Execution Environment (PXE) startup on a client computer. In this scenario, there may be a delay of up to 20 minutes before the client computer starts.

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.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

To deploy this hotfix to the Windows Server 2003 RIS server, follow these steps:

1. Extract the binaries to a temporary folder such as C:\Temp.
2. Replace the startrom.com and startrom.n12 files in following folder with the files from the C:\Temp folder:
   \RemoteInstall\OSChooser\<arch>\
3. On the image folder that has exhibits this problem, replace the startrom.com or startrom.n12 files in the following folder:
   \RemoteInstall\Setup\<Lang>\Images\<ImageName>\<arch>\templates

Notes

• Do not apply this hotfix on a Microsoft Windows 2000 Server-based RIS server.
• Only apply this hotfix on x86 or amd64-based versions of Windows Server 2003.
• Do not replace the startrom.com or startrom.n12 files in the templates folder of Windows 2000 images even if the image is on the Windows Server 2003 RIS server.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: