How to fix Event id 1111 TermServDevices printers not mapping in terminal server issue

A common problem when using a terminal server, or remotely connecting to a Windows XP or Vista desktop is that the system you are connecting to does not have the required drivers installed for you to be able to print locally. Each time you log in, the system event log will contain 1111  errors that are related to TermServDevices for each local printer that does not have drivers installed on the local system.

The simplest way to fix this is to download and run the Terminal Server Printer Redirection Wizard Tool  located here . When you run the tool, it searches the event log of the remote desktop for 1111 events, then asks you to install drivers for each printer that you wish to. The best thing to do is to run it on the remote desktop and download the drivers to a location on this same remote desktop for ease of installation.

6 thoughts on “How to fix Event id 1111 TermServDevices printers not mapping in terminal server issue

  1. shawn

    And it doesn’t work for my 1111. It appears that a workgroup PC we attached to the domain still have drivers on it for the old network. Even knowing the laptop it has not been booted up all week we get 1111 errors nightly…so I don’t think this 1111 fix is for every scenario…

    Reply
  2. Yigit Yilmaz

    i work with windows server 2008 standard 64 bit R2
    Error 6 : Terminal Server Printer Driver encountered a problem with the wmi subsystem on the server “servername”

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>