Terminal Server 2003 Client Printers

[joelrob]

We have 2 Windows Server 2003 Terminal Servers that are constantly mapping printers from the client computers. I've disabled client printer mapping in both the Terminal Server Configuration and the Terminal Server section of the Group Policy.

No matter how I set it, it always maps the default printer of the client computer and sets it to the default printer. I have a script in place that sets the default printer to be an RDP enabled local printer on the server, and the script works, but before the login is complete the default printer is re-set to the client's default printer.

Anyone else run into this and found a workaround?

 

[wallst32]

What SP level are you on?

It sounds like the policy to "map client's default printer only" is enabled; I would check that.

 

[joelrob]

The settings for Printer Redirection in the Group Policy are as follows:

Do not set default client printer to be default printer in a session - Enabled

Do not allow client printer redirection - Enabled

Specify terminal server fallback printer driver behavior - Not configured

I've also disabled printer redirection in the Terminal Server Configuration manager, and on the RDP login webpage. Still every time I log onto the server, my local printer gets mapped and set as default.

 

[cmeagan656]

On the client, in the Remote Desktop Connection properties of the connection that you use to connect to the terminal server make sure that that the checkbox next to printers on the local resources tab is not checked.

Cheers

 

[joelrob]

Thanks for the input, but we use the Remote Server Login webpage with TSWeb on IIS. The setting there is:

MsRdpClient.AdvancedSettings2.RedirectPrinters = FALSE

but we still get the printers mapped.

 

[joelrob]

Just to verify it's not an issue with the code on the webpage, I opened an RDP session directly, cleared the "map printers" and connected, still getting my local printer mapped.