Hotfix information
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
Windows Server 2003, Automated Deployment Services 1.0
Restart requirement
You do not have to restart your computer after you apply this update.
Hotfix replacement information
This hotfix does not replace any other updates.
File information
The English version of this update has the file attributes (or later) 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 tool in Control Panel.
Date Time Version Size File name
--------------------------------------------------------------
17-Jun-2004 21:49 5.2.3790.184 305,152 Osloader.ntd
An update is available that lets you specify the client port that clients will use to contact the ADS Deployment Agent Builder service.
After you apply this update, you can add the new, optional
/RDCLIENTPORT parameter to the Boot.ini file on the ADS server. Then, clients will use the specified port to connect to the server.
To install the update and modify the Boot.ini file, follow these steps:
- Run the hotfix installer package on the ADS server. When prompted, specify a folder to extract the files to. The Osloader.ntd file is extracted to the location that you specify.
- Copy the Osloader.ntd file to the following folder:
%systemdrive%\Program Files\Microsoft ADS\tftproot\nbs\boot\x86
- Rename the existing Ntldr file in this folder to Ntldrold.
- Rename the Osloader.ntd file to Ntldr.
- Use a text editor, such as Notepad, to modify the Boot.ini file in the following folder:
%systemdrive%\Program Files\Microsoft ADS\tftproot\nbs\boot\x86
- Type /RDCLIENTPORT=port at the end of the appropriate line, where port is the port that you want to specify.
For example, to specify port 8089, add the following text to the end of the appropriate line:
/RDCLIENTPORT=8089
- Restart the computer.