Windows TS Printer Redirection Issues
Windows Remote Desktop Printer Redirection Issues
"Do not allow client printer redirection" in Group Policy Settings is
enabled
Multifunction print devices may not be redirected because of COM, LPT, or
USB ports
Need
to upgrade remote desktop version
Printer
redirection is disabled in client Remote Desktop
Printer Redirection Issues in Windows 2008
Printer redirection issue with Vista client
Printer Redirection Troubleshooting Tools
Remote Desktop (Terminal Server) Device Redirector is disabled
Redirection non-supported printer to Terminal Server
Registry may prevent printer redirection from functioning
The default printer changes after logon TS
The TS doesn't have printer driver
installed
Windows Printer
Mapping Check Box is disabled
Case 1:
The TS doesn't have printer driver installed. If only some printers are
not redirected after connecting to remote computer, it could printer driver
issue.. On the remote computer, you may see Event ID: 1111 and
Description: Driver drivername required for printer printertype is unknown. The
resolution is installing the printer driver directly on the remote computer. If
the computer is Windows 2003 Server Service Pack 1, you may try the
Fallback Driver Capability instead. The policy for this is located under
Computer Configuration\Administrative Templates\Windows Components\Terminal
Services\Client / Server data redirection\Terminal Server Fallback Printer
Driver Behavior. Note: The
terminal server fallback printer driver is not included with Windows
Server 2008. Although the Specify
terminal server fallback printer driver behavior Group
Policy setting still exists, it can only be used for computers running
Windows Server 2003 with SP1 or Windows Server 2003 with Service Pack 2
(SP2).Case 2:
Printer redirection is disabled in client Remote Desktop.
When Printer redirection fails for a computer only, you may want to check
the settings on the Remote Desktop on the problematic client and make sure
that the Printers check box is checked to allow redirection as shown below.

Case 3:
Windows Printer
Mapping Check Box is disabled. To check the status
of Windows Printer Mapping, open the Remote Desktop Configuration
(Terminal Services Configuration if it is Windows 2003 or previous version).
Right click on RDP-Tcp and select properties.

Then select the Client Settings tab. Ensure that the
Windows Printer (Windows Printer Mapping if it is Windows 2003) checkbox is
not selected. If it is, that means that the Terminal Server will not allow
client Printer Redirection.

Case 4:
"Do not allow client printer redirection" in Group Policy Settings is
enabled. Printer Redirection can also be configured
through Group Policy. The policy to prevent client printer redirection is
located in the following container: Computer Configuration\Administrative
Templates\Windows Components\Remote Desktop Services (Terminal Services if
it is windows 2003)\Remote Desktop Session Host (or Client / Server Data
Redirection). The name of the policy setting is "Do not allow client printer
redirection" as shown below

If this configuration is enabled, it
will prevent client printer redirection.
Case 5:
Remote Desktop (Terminal Server) Device Redirector is disabled.
The server side component responsible for printer redirection is RDPDR.SYS.
You can check the status of the Remote Desktop (Terminal Server)
Device Redirector in Device manager as shown below. If the Remote
Desktop (Terminal Server) Device Redirector is disabled, then device
redirection will not work.
Make sure that Remote Desktop (Terminal Server) Device Redirector is
in enabled status. You can also use the following command to recreate this
device: devcon -r install %windir%\inf\machine.inf root\rdpdr.

Case 6:
Registry
may prevent printer redirection from functioning.
If you have implemented the mentioned in Microsoft KB Article 268065 it will
prevent printer redirection from functioning. As per this KB if the registry
value fEnablePrintRDR is set to 0, Printer Redirection will fail even if the
Print Spooler is started on the Terminal Server. This will not register any
events. As part of your standard troubleshooting you should check whether
the following value exists: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\Wds\rdpwd\fEnablePrintRDR.
Case 7: Need to
upgrade remote desktop version. In some cases, it
could be the Remote Desktop Client version on the problem machine. You
should always ensure that you are running the latest RDP Client on your
client machines.
Case 8:
Multifunction print devices may not be redirected because of COM, LPT, or
USB ports. In other cases, some multifunction
print devices may not be redirected unless you are running Windows Server
2003 on your local computer because they use DOT4 ports. Only W2K3 redirects
printer port names that do not begin with COM, LPT, or USB. If you are using
a Windows XP machine use the workaround mentioned in Microsoft KB Article
302361.
Printer
Redirection Troubleshooting Tools: Terminal
Server Printer Redirection Wizard tool is a very useful tool to troubleshoot
printer redirction issue. This utility scans the Terminal Server's
System Even log and detects all Event ID 1111 events with a source of "TermServDevices".
The tool then scans the registry for installed Version 3 MINI drivers, and
prompts the Administrator to substitute an installed driver for each of the
printers that failed redirection. Any changes are written to a file where
the custom redirected printer mappings are stored. The details can be found
this post:
TS Printer Driver Redirection Wizard reports Error 3
Related posts:
TS Prot print port is unavailable
Vista printer can't be redirected when using
Can 32-bit client redirect printers to a system running 64 bit
Printer on XP cannot be redirected to the
Microsoft Remote Desktop Connection V6 Issues
RDC over VPN can't print to local
Use XP printer when RDP to Vista
Post your questions, comments, feedbacks and suggestions
Contact a consultant
Related Topics
2008 R2 Easy Print - Lots of Issues - Looking for Checklist
Easy Print color printing problems using Server 2008 TS
Easy Print redirection not working with Win 7 64bit client
Event ID 372: The
document failed to print
Printer Errors on Server 2008 R2 Remote Desktop Server
Printer
Redirection doesn't work in Windows 2008
Printer Redirection with easy print not working as Desired
Printer
Redirection works only one printer but others
Server 2008 R2 easy print printers show up but do not work
Terminal
Services Easy Print driver doesn't work
Terminal Services Easy
Print is disabled
The Easy Printer doesn't work if login using /admin switch. Again this is
from Microsoft:
TS 2008 - Printer not being Redirected
Windows 2008 R2 Remote Desktop Easy Print Issue
XP connects fine remotely but Windows Easy Print is issue
|