Sometimes, printer drivers names can differ between different Windows versions. This is problematic when connecting to a remote desktop server, as the printer’s name is used to look up the correct driver to use. When the printer driver names do not match, event ID 1111 will occur in the Windows Event Log, for example:
Driver RICOH Aficio 2018 PCL 6 required for printer RICOH Aficio 2018 PCL 6 is unknown. Contact the administrator to install the driver before you log in again.
When you look at the installed driver list on the remote desktop server, we see:
Ricoh Aficio 2018 PCL6
Note the lowercase manufacturer and the removed space between “PCL” and “6”. The solution is to create a mapping file that matches up the printer’s names, again allowing successful waste of paper.
Modify the registry
First we must tell Remote Desktop Services where to find our mapping file. To do that, open the registry and navigate to the following key:
Add two new string values
- Value Name: PrinterMappingINFName
- Value Data: C:\printmap.inf
- Value Name: PrinterMappingINFSection
- Value Data: Printers
Create the mapping file
Next, create a plain text file, C:\printmap.inf, with the following content:
“RICOH Aficio 2018 PCL 6” = “Ricoh Aficio 2018 PCL6”
“Brother DCP-560CN Printer” = “Brother DCP-560CN”
The format of the “Printers” section is as follows:
Left-hand side: name as presented by the client (what the client reports and what you see in the event log)
Right-hand side: correct printer name as listed on the server (the driver’s name listed in print management)
You can add multiple printers.
Logoff and logon
The user should log off and log back on again. The printer should now be installed and the event ID 1111 shouldn’t occur anymore.