Printer tray assignments on a print server may not transfer to the client computer when you install a network printer in Windows 2000

This article has been archived. It is offered "as is" and will no longer be updated.
For a version of this article that applies to Microsoft Windows XP and Microsoft Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
870981 Tray assignments are not retained when you install a network printer in Windows XP or in Windows Server 2003
If you install a network printer on a Microsoft Windows 2000-based client computer from a Windows 2000-based print server, the tray assignments on the printer may not transfer to the client computer. When you view the tray assignments on the client computer, the tray appears as not available.
This problem may occur if the client computer uses a language version of Windows 2000 that is different from the version that is used by the print server.
To resolve this problem, install this hotfix on both the print server and the client computer.

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.

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, submit a request to 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.


To install this hotfix, you must have Microsoft Windows 2000 with Service Pack 4 (SP4) installed on your computer.

Restart requirement

You do not have to restart your computer after you apply this hotfix. However, when you install this hotfix, the server may spend up to two hours regenerating the parsed binary printer description files (.bud files) that are used to increase spooler efficiency for the drivers. During this time, Print Spooler cannot receive incoming print jobs and may return messages to clients that indicate that the print queue is full. This is a one-time parsing operation and does not occur after the parsed binary .bud files are successfully regenerated. Therefore, we recommend that you schedule this hotfix installation to allow for this delay. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
832219 Users cannot print after you install a service pack, update rollup, or printer hotfix on a server in Windows 2000

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 tool in Control Panel.
   Date         Time   Version              Size  File name   -----------------------------------------------------------   06-Mar-2004  00:41                     14,088  Locale.gpd   06-Mar-2004  00:41                     25,489  P6disp.gpd   06-Mar-2004  00:41                      3,293  P6font.gpd   19-Nov-2004  07:20  0.3.1296.1        676,864  Pcl5eres.dll   06-Mar-2004  00:41  0.3.1296.1        169,472  Pclxl.dll   06-Mar-2004  00:41                     10,375  Pclxl.gpd   06-Mar-2004  00:41                      1,156  Pjl.gpd   19-Nov-2004  07:20  0.3.3790.231      133,120  Ps5ui.dll   06-Mar-2004  00:41                     26,038  Pscript.hlp   06-Mar-2004  00:41                    792,644  Pscript.ntf   19-Nov-2004  07:20  0.3.3790.231      464,896  Pscript5.dll   06-Mar-2004  00:41                    969,400  Pscrptfe.ntf   06-Mar-2004  00:41                     14,362  Stdnames.gpd   06-Mar-2004  00:41                        698  Ttfsub.gpd   19-Nov-2004  07:20  0.3.1296.1          8,704  Tty.dll   06-Mar-2004  00:41                     12,505  Tty.gpd   06-Mar-2004  00:41                         62  Tty.ini   19-Nov-2004  07:20  5.2.3790.120       39,936  Ttyres.dll   19-Nov-2004  07:20  0.3.1296.1         16,384  Ttyui.dll   06-Mar-2004  00:41                     14,387  Ttyui.hlp   19-Nov-2004  07:20  0.3.3790.231      248,832  Unidrv.dll   06-Mar-2004  00:41                     21,225  Unidrv.hlp   19-Nov-2004  07:20  0.3.3790.231      198,144  Unidrvui.dll   19-Nov-2004  07:20  0.3.1296.1        619,520  Unires.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about how software update 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 terminology that is used in this article, 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

Article ID: 870980 - Last Review: 10/26/2013 10:08:00 - Revision: 4.0

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Advanced Server
  • kbnosurvey kbarchive kbautohotfix kbbug kbfix kbwin2000presp5fix kbqfe kbhotfixserver KB870980