Microsoft KB Archive/239111
Changes to Client Printer Device Settings Are not Detected by Terminal Services
The information in this article applies to:
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows 2000 Server
When you connect to a computer running Windows 2000 with Terminal Services installed, any locally attached client printers are automatically created for each Terminal session. Also, the printer configuration information is cached on the Terminal Server computer during logon. Therefore, the server does not have to obtain the settings from the client each time the printer is used.
Whenever you make a change to the printer configuration on the client, the server is notified of the change and updates the cached information for all printer configuration tabs. The only exception to this rule is whenever a change to the device settings tab is made on the client. Changes to this tab do not cause the cached information on the server to be updated.
The current printing model does not support listening for changes to the device settings for each printer.
If you need changes made to the client printer device settings tab, make the changes on the client, then make a change to another tab of the configuration page for the printer. By making a change on a another tab, the server is notified that there has been a configuration change to the printer. This causes the server to rebuild all cached information, including the device settings.
Microsoft has confirmed this to be a problem in Microsoft Windows 2000.
Additional query words:
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbprb
Last Reviewed: December 29, 1999