Saturday, April 10, 2010

Using Printers With Remote Desktop Protocol

The updates to the Terminal Services and Remote Desktop Protocol printing functionality in Windows 2008 and 2008 R2 has been great in our experience. However, on occasion, it’s not always as seamless as you would hope.

That’s not to say that it’s Microsoft’s fault – it’s usually a result of the printer manufacturers. Due to the myriad of drivers available for even a single printer model, printer names get mismatched and sometimes it’s just a few characters like a version number or a dash that causes problems.

For example, a LaserJet 5 could appear as a LaserJet 5 Series, Laserjet 5 Series PCL6, etc. depending on the version of the driver and the exact printer model.

Instead of removing and reinstalling the matching driver, Microsoft has a workaround in this KB. To summarize, you’ll see event ID 1111, 1105 or 1106 in the system logs. Create a registry key and a corresponding .inf file that matches the printer name variations. Works great.

There’s also a Printer Driver Redirection Wizard that automates the creation of the .inf file if you need more help.

1 comment:

Lisa Ray said...

Being a system admin, this post was very helpful to me. I really appreciate your technical knowledge! Drivers Download