Terminal Services Printing in W2K3

[Teknoratti]

The following link was given when I searched an Event ID in the Microsoft KB.

http://support.microsoft.com/default.aspx?scid=kb;en-us;239088

Is this still prevelant in W2K3? If a client has a locally attached printer and a driver installed, when they connect to a TS does the TS and client have to have the same instance of print driver in order for the TS to pick it up.

I would be sure the client pc had to have the print driver installed, in order to communicate with the printer. Or does the print server on the TS send the job directly to the printer?

 

[irweazel]

the print drivers need to be installed on the terminal server. You may need to make sure that this is installed by an administrator as with our build users are prevented from installing print drivers

 

[Teknoratti]

Yes I know they need to be on the TS but does the same instance of driver have to be on the client too?

 

[dkediger]

I do believe TS does match printer drivers. I've seen somewhere an article about hacking .INF files to fool TS printing.

However, that should be obviated with 2003 Server SP1. There is a new TS Group Policy for Fallback Printer Driver Behaviour. Basically allows you to specify to use generic PCL or PostScript if the specific matching printer driver isn't found.

See the first link at:

http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx

 

[Huevo]

What are the steps for installing a printer that is attached locally to a pc and is using RDP to a terminal server

 

[58sniper]

Grab the drivers for 2003. If there isn't one, grab the XP driver.

On the TS box, go into properties, click FILE>SERVER PROPERTIES, and go to the DRIVERS tab. Click ADD and install the drivers there. DO NOT GO THROUGH THE ADD PRINTER WIZARD.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)