Terminal Services provides printer redirection, which routes printing jobs from a server to a printer that is attached to a client computer or to a shared printer that is available to the client computer. When a user establishes a remote session with a terminal
server, the redirected printer will be available to applications running in the remote session.
By default, a Windows Server 2008 terminal server first tries to use the Terminal Services Easy Print driver. If the client computer does not support this driver, the terminal server looks for a matching printer driver installed on the terminal server. You
can either install a matching printer driver on the terminal server, or you can create a custom printer mapping file.
Event Details
| Product: | Windows Operating System |
| ID: | 1111 |
| Source: | Microsoft-Windows-TerminalServices-Printers |
| Version: | 6.0 |
| Symbolic Name: | EVENT_NOTIFY_UNKNOWN_PRINTER_DRIVER |
| Message: | Driver %1 required for printer %2 is unknown. Contact the administrator to install the driver before you log in again. |
Resolve
Reinstall the printer driver or modify a custom printer mapping file
To resolve this issue, do either of the following:
- Install or reinstall the printer driver on the terminal server.
- Create or modify a custom printer mapping file.
To perform these tasks, refer to the following sections.
Install or reinstall the printer driver on the terminal server
If the printer driver installed on the client computer is an OEM driver, and a driver is available from the printer’s manufacturer, replace the OEM driver with the driver that is available from the printer manufacturer. If you are installing a third-party
driver, make sure that the driver is a Windows Hardware Quality Labs (WHQL) signed driver.
Important: After you install the printer driver, terminal server clients must log off and then log on to the terminal server before the printer driver changes take effect.
To install the printer driver, use either of the following methods.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Method one
Run the printer’s Setup program to install the printer driver .inf file on the terminal server.
Method two
To install the driver by using the Add Printer Driver Wizard:
- On the terminal server, click Start, click Run, type
control printers, and then click OK. - On the File menu, click Server Properties.
Note: If the File menu is not visible, right-click an empty area of the
Printers dialog box, and then click Server Properties. - Click the Drivers tab.
- Click Add, and then follow the instructions in the Add Printer Driver Wizard to install the printer driver .inf file.
Create or modify a custom printer mapping file
You can create or modify an existing custom printer mapping file to define mappings from client-side to server-side drivers on the terminal server.
To perform this procedure on the terminal server, you must have membership in the local
Administrators group, or you must have been delegated the appropriate authority.
To use a custom printer mapping file:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
- On the terminal server, open Registry Editor. To open Registry Editor, click
Start, click Run, type regedit, and then click
OK. - If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click
Continue. - Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd registry subkey.
- Add the following values:
Name: PrinterMappingINFName
Type: String (REG_SZ)
Value data: Name of the .inf file to which you want to redirect lookups.
Example: c:\windows\inf\ntprintsubs.inf
Name: PrinterMappingINFSection
Type: String (REG_SZ)
Value data: Name of the section in the .inf file to which you want to redirect lookups.
Example: Printers
After you add the new registry values, create or modify the .inf file that you specified in the
PrinterMappingINFName registry entry to include the user-defined mappings from the client-side to server-side drivers. Follow the format used in the following example:
;NTPRINTSUBS.INF
;Printer mapping file for client-side to server-side drivers
[Printers]
"OEM Printer Driver Name" = "Windows Server 2008 Driver Name"
For example:
"HP DeskJet 720C Series v10.3" = "HP DeskJet 722C"
The left side of the equation is the exact name of the printer driver associated with the client-side print queue that is being redirected to the server. The exact name of the printer driver appears on the
General tab, next to Model when you view the printer properties on the client computer. (You can also click the
Advanced tab and view the driver name in the Driver list.) The right side of the equation is the exact name of the server-side driver equivalent that is installed on the terminal server.
Important: You must restart the Print Spooler service on the terminal server for the changes to take effect.
To perform this procedure on the terminal server, you must have membership in the local
Administrators group, or you must have been delegated the appropriate authority.
To restart the Print Spooler service:
- On the terminal server, open the Services snap-in. To open the Services snap-in, click
Start, point to Administrative Tools, and then click
Services. - If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click
Continue. - In the Services pane, right-click Print Spooler, and then click
Restart. - Confirm that the Status column for the Print Spooler service displays
Started.
Verify
To verify that printer redirection is working properly, establish a remote session with the terminal server and check that the redirected printer is available and is functioning as expected.
Related Management Information
Terminal Services Printer Redirection
Terminal Services
-
#1
Привет, с довольно частой периодичностью на некоторых серверах в журнале событий регистрируются event с кодом 1111, источник — TerminalServices-Printers,
Код:
Драйвер HP Color LaserJet CP4020 Series PCL6 для принтера !!server1!CP4525 не опознан. Обратитесь к сетевому администратору, чтобы он установил нужный драйвер.Что это за принтер, почему он подключается к этому серверу? Что за ошибка? Ничего не понимаю
-
#2
эта ошибка говорит об ошибках при переназначении вывода на принтер, когда заходишь на сервер терминалом. если в терминальной сессии ты управляешь сервером, и не печатаешь — забудь про нее. чтоб глаза не мозолила в свойствах клиента (например rdp) убери галку на «сопоставлять принтеры»
если есть необходимость печати из терминала гугли -печать из терминальной сессии
В просмотре событий появляется ошибка:
Имя журнала: System
Подача: Microsoft-Windows-TerminalServices-Printers
Дата: 31.08.2012 13:03:01
Код события: 1111
Категория задачи:Отсутствует
Уровень: Ошибка
Ключевые слова:Классический
Пользователь: Н/Д
Компьютер: comp.domain.ru
Описание:
Драйвер XXX для принтера YYY не опознан. Обратитесь к сетевому администратору, чтобы он установил нужный драйвер.
Xml события:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-Printers" Guid="{952773BF-C2B7-49BC-88F4-920744B82C43}" EventSourceName="UmrdpService" />
<EventID Qualifiers="0">1111</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-08-31T09:03:01.000Z" />
<EventRecordID>15242</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>comp.domain.ru</Computer>
<Security />
</System>
<EventData>
<Data>XXX</Data>
<Data>YYY</Data>
<Binary>00000000BA0E0000</Binary>
</EventData>
</Event>
Связана она с тем, что Вы пытаетесь использовать совместно локальные ресурсы, в данном случае принтеры, подключаемого компьютера на сервере. Другими словами, если Вы с ноутбука подключаетесь к серверу терминалов и на ноутбуке у Вас установлены устройства принтеров, то сервер пытается их использовать. Но поскольку сервер работает на другой операционной системе, то на ней могут отсутствовать драйвера для подключённых на ноутбуке принтеров. Отсюда и возникает ошибка.
Теперь ясно, как от неё избавиться:
- Установить соответствующие драйвера на сервер терминалов и тем самым предоставить возможность в течении подключённого сеанса печатать документы на этих принтерах.
- Не использовать принтеры как совместные ресурсы. Для этого нужно снять галочку «Принтеры» на вкладке «Локальные ресурсы» в свойствах подключения.
- Remove From My Forums
-
Question
-
Hey,
I keep gettin these events in one of my DC’s mainly the DC holding all the network printers for all the clients. No client has any issues printing, but these have started to appear on my Zenoss monitoring box. Which I have since setup to ignore these events.
But doesn’t help the fact that they are still apearing in event viewer. Normally I always attempt to resolve these ting on my own but have yet to come up with a solution due to the following conditions. Please bare with me.Reading up more on this from here…
http://support.microsoft.com/?kbid=239088So I get for the most part its due to driver mappings not being correct for both cleint and server, and to fix it create a manual .inf file and create a registry entry to point to it.. HOWEVER…
Some Event ID 1111’s also contain printer resources on the client that cannot and must not be redirected like fax drivers or software printers.
These are the type of events showing up, CutePDF writer, WebEx Doc Loader, etc, all seem to be software printers, which shouldn’t be fixed using this method…
I have also checked other fourms created such as these..
http://social.technet.microsoft.com/Forums/en-US/ec9096c3-ab18-4360-bcb3-26b6b09d1a91/error-in-event-managertermservdevicesevent-id-1111
I attempted to see if these were populated at a RDP connection but they did not appear when making RDP connections.
http://social.technet.microsoft.com/Forums/en-US/f567be02-1bc0-4a6c-a6b7-61347df612fa/error-1111
Falls under the usual physical printer driver mappings..
I’m stuck now, how do I get rid of these errors from appearing in my event log. I like to stay proAtive and have clean logs whenever possible. Please help. Thanks
Answers
-
-
Edited by
Monday, September 2, 2013 7:49 AM
-
Marked as answer by
Frank Shen5
Thursday, September 5, 2013 1:32 AM
-
Edited by