A support ticket was recently logged with us saying something along the lines of “When using the Terminal Server we cannot print to the printer in our office”.
This a first seems quite a simple fault to resolve… but is it?
The usual simple stuff was checked such as are the printer drivers both present on the Terminal Server and the clients machines which they were. The printer was mapping correctly from the client computer over to the Terminal Server but when the user was clicking Print on the Terminal Server, nothing was happening, not even anything showing up in the printer queue. The most unhelpful point regarding this fault is that nothing is either logged in Event Logs on the Terminal Server or the client computer, so fault finding on the issue takes a bit more thought.
After bringing the computer back to the office where I work and trying to print onto a different printer, but using a different Terminal Server it printed out fine…. This must mean that it was a configuration issue on the Terminal Server itself.
After some googling into the issue the following recommendations were found:
- Ensure that Client Printer redirection is enabled in Group Policies
- Users are able to print locally directly to printer
- LPT Port redirection is enabled on the Terminal Server
- The group “Everyone” is allowed full access to C:\Windows\System32\Spool folder on the Terminal Server
- Ensure that RDP is version 6.1 or 7.0
- .NET FrameWork 3.5 SP1 is installed on Client and Terminal Server
All of the above were true. It turns out that it was an issue with the Terminal Services Easy print driver taking presidence. To disable this setting, edit the following Group Policy Setting:
Computer Configuration/Policies/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Printer Redirection/"Use Remote Desktop Easy Print Driver first"
Set it to disabled then carry out gpupdate/force.
Users will now be happy as they can now print.