Link to home
Start Free TrialLog in
Avatar of regisit
regisit

asked on

Not getting TermServDevices error 1111 any more

Hi, at some point TermServDevices error 1111 has stopped being logged whenever someone logs into server using RDP. I don't know when, but it must have been some time back now. I manage several SBS 2003 networks and this was always a pain. But now I miss them!

I miss them because it indicates that RDP is no longer attempting to connect client-side printers. I've checked the client-side setting to make local printers available on the remote desktop. I've also checked that Terminal Services Configuration is set to "Use connection settings from user settings". But still no logs about missing printer drivers and no local printers being made available on the remote desktop.

It seems that remote printing to local devices has just been broken at some point. Anyone know whether something has changed to stop these messages? That would at least give me somewhere to start in trying to find out why local printers are not even attempting to show up on remote sessions.

Thanks.

P.S. Tried Q302361 and it made no difference.
Avatar of Hazem KUNNANA
Hazem KUNNANA
Flag of Saudi Arabia image

This is about wrong printer driver, that might have stopped because of many things:
The user's rdp client may have stopped passing printers to the session.
Your server's printer spooler may have stopped or has some errors.
The printer drivers in error may have been really loaded in some version on the server, so there are no errors.

Also, please see the page about the event:
http://www.eventid.net/display.asp?eventid=1111&eventno=660&source=TermServDevices&phase=1
ASKER CERTIFIED SOLUTION
Avatar of Henrik Johansson
Henrik Johansson
Flag of Sweden image

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
Avatar of regisit
regisit

ASKER

Thanks henjoh09, this has been disabled through group policy. I think I'd recall doing this manually across multiple servers, so it must have come down as part of some patch over the last 12-18 months.