Matthew thanks for the info. I trirewd what you suggested but still have the problem of the Color laser printer beingreadded whenever the user logs in to the terminal server. I deleted the printer form the drivers tab in Server Properties, and from the registry as outlined in the article provided. Do you know of how I can prevent a user from automaticcally adding printers when they login to the terminal server. IN essence I want to lock down the printers on the Terminal Sevrer to only those that we can support and are guaranteed to work.
Dan Willi
----- Matthew Harris [MVP] wrote: -----
The problem is with the drivers those printers use. You
need to remove all those third party drivers that are
installed and replace them with drivers that came with the
Windows 2000 disks.
Check out this link for more information on how to remove
drivers....
support.microsoft.com/default.aspx?scid=kb;en-
us;135406&Product=win2000
-M
-----Original Message-----
We are constantly getting errors with the print spooler
stopping on the terminal server. I am running W2KSP4 with
the latest updates and patches. When some users log in to
the Terminal Server I get event ID 7031 and the spool
service stops. I deleted all of the printers and added
back only a few of the ones we need using on Microsoft
drivers and set the spool service to restart. I noticed
that one of the printers, HPColor Laser 4500, is added
back on its own when a remote user logs in and then I get
the spool errors again. Is there a way to stop having
printers add themselves back in terminal server? Our
remote users do a lot of printing in there home offices
and this has been a major pain. Thanks for any help.
