So you have a printer installed on your Microsoft Windows computer, but the printer is not showing in your Remote Desktop session? There are a few things to check when you experience this issue.
1. Check that Printers Are Enabled on Connection
Ensure that you have the Printers option selected in your Remote Desktop settings. You can check this by bringing up the Remote Desktop Connection screen, selecting Local Resources and ensuring the Printers option is selected.
2. Check Server Settings
If you are connecting to a Windows Server box, ensure the settings on the server don’t disable the sharing of Printers. Login to the server, and perform these steps.
Windows 2016 & 2019
In these versions of Windows Server, RDP settings are controlled in Group Policy.
- Launch “gpedit.msc“.
- Navigate to “Computer Configuration” > “Administrative Templates” > “Windows Components” > “Remote Desktop Services” > “Remote Desktop Session Host“.
- Expand “Printer Redirection“.
- Ensure that “Do not allow client printer redirection” is set to “Not configured” or “Disabled“. Another setting you may want to check is the “Redirect only the default client printer“. This policy should also set to “Not configured” or “Disabled” if you want more than just the default printer to be available to use.
Windows 2012
- Open “Server Manager“.
- Select “Remote Desktop” Services.
- Select “Collections“.
- Select “Tasks“, then choose “Edit Properties“.
- Under the “Client Settings” tab, ensure the “Windows Printer” is enabled.
Windows 2008
- Go to “Start” > “Administrative Tools” > “Remote Desktop Services” > “Remote Desktop Session Host Configuration“.
- Select “Connections“, right-click the name of the connection > “Properties” > “Client Settings” > “Redirection“. Ensure that “Windows Printer” is not checked.
3. Ensure Drivers Are Installed On Server
Check that the printer drivers for the printer you are attempting to use are installed on the computer you are connecting to. If the drivers haven’t been installed on the computer you are connecting to, the printer won’t appear at all.
Mike C says
Thank you so much! This article really helped. I was struggling to figure out what was going on. I tried a different remote app a couple of days ago and came back to RDP. Upon trying to print today, none of the MS Office apps had printers listed even though they show up under settings in Win10. Anyway, I found this site and it is just what I needed. I use a MacBook Pro to log on to a PC so thought I would pass this along since the RDP for Mac looks nothing like the screenshots above. In the latest version of MS RDP for Mac upon opening the app to login a window displays that shows a preview of your remote computer desktop. In order to get to the printer menu options click the “pencil” or edit icon in the bar at the bottom of this preview window. Note; you will have to hover your pointer over this bar to see the “pencil” or edit icons. This will open another window with multiple tab choices.. Select “Devices & Audio” and then check mark “Printers” in order to have them show on the remote session.
Cam says
DaDuke your comment on the length of the computer name was my issue :) Thanks, mate. Cam.
TMa says
@DaDuke: Wow, you are right. Really missleading feature when testing success using “Printers and Devices” screen after connection. , Thanks.
Oliver Benning says
it will work for simple printers. I tried on the MFP, and I could not take the device remotely. Apparently for the RDP session this is a complex device. I had to use third-party software for sharing https://www.flexihub.com/
Tamar says
Rod Vel, this was the answer to my printer problems! Thanks, man.
DaDuke says
Dont forget the fact, that printer might noct showing up in “Printers and Devices” if the local computername is longer than 14 characters.
The redirected printers will work and print in applications, but they doesnt show up in “Printers and Devices”.
Rod Vel says
Local setup: Epson L455 on Windows 10.
RDP: Windows Server 2003.
Problem: Printer won’t show up on server.
Cause: Windows 10 installed the printer automatically
Solution: Install driver by yourself, overriding Windows 10 installation. Close your session and login again