Link to home
Start Free TrialLog in
Avatar of ChrisKremer
ChrisKremer

asked on

How to stop W2k3 Term Svr from logging Event ID:1111 Printer "Driver X is Unknown" errors in the system log

When my terminal server users login I keep getting errors in the system log similar to the one below. I understand why this error is coming up.  I do not need or want to install these printer drivers on the server.  I use Screwdrivers for terminal server client printing and it works great.  I just want to get rid of the error logging in the system events.

Any Ideas would be greatly appreciated!

Thank you!

Event Viewer - System Log

Event Type:      Error
Event Source:      TermServDevices
Event Category:      None
Event ID:      1111
Description:
Driver hp officejet 4200 series fax required for printer hp officejet 4200 series fax is unknown.
Contact the administrator to install the driver before you log in again.
Avatar of caddlady
caddlady

Easiest ways:

Do not allow them to bring printers with them when they logon to TS

or

Install the driver on the server
Avatar of ChrisKremer

ASKER

caddlady

Thank you for your recommendation.

Installing the printer drivers is not an option.

I have tried to set a group policy that restricts adding the printer but it does not work. I still keep getting the errors.

How would "not allow them to bring printers with then when they login to TS" ?

Thank you for your input. Obviously this is a complex issue otherwise their would have been other posts.
Do you use AD?

One way to stop it is:     if you look at a user's properties, there is an Environment tab that deals with the Startup Environment when that user connects via TS.  Uncheck the box that says "Connect Client Printers at Logon".

ASKER CERTIFIED SOLUTION
Avatar of caddlady
caddlady

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
caddlady;

 Thank you for your suggestions and for helping me to solve my issue! The printers errors are not logged in the system log any more. I finally have resolved all the windows logging errors in the event viewer.

ChrisKremer