Installing 3th party printer drivers on a TS is *not* recommended.
Most of these drivers are not completely TS compatible, and are
known to crash the printer spooler or the whole server.
If your client printers are not autocreated, check the EventLog to
find the reason. If the server doesn't recognize the printer, map
the printer to a native driver on the server, by creating a custom
ntprintsubs.inf file. Details are explained here:
239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088
You can check the recommended native driver substitution for your
local printers here:
Client Printer Autocreation Matrix
http://www.printingsupport.com/matrix.htm
If you are running 2003 SP1 on your Terminal Server, you can
configure a Terminal Server Fallback Printer Driver. For more info,
check:
http://www.thelazyadmin.com/index.php?/archives/18-Terminal-Server-
Fallback-Printer-Driver.html#extended
Check to see if your Group Policy or local policy is set to
"Prevent Users from installing Print Drivers".
If this is NOT enabled, a user with a newer signed driver will
unknowingly and automatically propagate its' driver to the terminal
server, which means that your servers will use different driver
versions, even though you didn't intentionally install newer
drivers.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?Z2VtaXJraGFuaWFuQGhvdG1haWwuY29t?=