My terminal server is Windows 2003 SP1. Clients connecting to the server need their printers redirected to their local printer device. Some clients are using printers that the server already has drivers for. These clients work do not have a problem with printer redirection. To support new user connections, I started installing drivers for other printers. This has become a big headache to say the least.
I know there are third party print utilities such as Thin Print and Print2RDP but I would like to try Microsoft's fallback printer driver first. I am having trouble with Windows 2003 fallback printer driver, can't seem to get it working. I have enabled this setting in group policy to show BOTH PCL and PS if clients print driver is not found on the server. I then did a "gpupdate /force" on the terminal server. The client still could not print.
From my understanding, when the group policy for this object is enabled and a terminal user connects with a bizzarre printer attached to their local computer, the server will default to either an HP 500 Deskjet or an HP 500 Color Deskjet depending if their local printer is color capable or not. I have read everything I could find on the net about configuring the fallback driver and I don't think there is anything else to configure on the server. If I wanted to use a specific fallback driver some registry edits could be made to support that but I would be happy with the fallback drivers Microsoft supports. Correct me if I'm wrong about any additional configurations.
I enabled the fallback driver for PCL and PS then refreshed group policy on the TS server. I'm not exactly what the terminal user will see for a default printer in their TS seesion when connecting. I would guess they would see an HP Deskjet 500 if they had a monochrome printer. What do I need to do to get this to work?
The 3rd party solutions are quite expensive.