Print Server Redirected

[Giovanni Sealy]

allthe printers are first set up on local my local machine, then i give them a new name and IP address. Then after remoting into the file/print server with my admin account i add the port, then connect the printer to the port. before going to the office site i change the gateway.

When you connect using remote desktop you have the option of checking if your printers (printers at the machine you are calling in from) follow you to the machine you remoted into. When you go to remote desktop before you click connect go to show options and under the local resources tab you can shut this off. The re-directed printers are only available as long as you are connected by RDP.

The redirected printers are from the PC that you are using Remote Desktop on. The RDP client redirects printers installed on the PC so they can be used on the remote machine. This confused me the first time I played around with RDP and our print server!

The shared printer in the picture is connected locally and works fine, so I tried removing the redirected one but got the error Access is denied, unable to remove device. I get the same error for the fax.

This will stop your local printer from being redirected. In this case your local printer appears to be the same as the one being shared, which might explain the trouble printing to its redirected version.

you can also disable remote printing all together in settings for RDP client before you connect. You can also use RDP client on MAC to print locally from a MAC over RDP client .. I know right its crazy!

In many enterprise printing scenarios, including remote-desktop environments, printer redirection is a commonly used print-management strategy. But the reports of redirected printers not working are frequent, and there are numerous glitches associated with printer redirection that cause problems for admins and end users alike.

Hello,

I have a Windows Server 2019 Essentials with External PCs accessing the Server through RDP,

The problem is that most of the times on the remote session the redirected printers suddenly stop printing after a few minutes or hours eventhough they show up on "Devices and Printers" as redirected, and it will only work again most of the times if i SignOut on the Remote Desktop session and SignIn again.

On the local PCs the printers always work without any problem.

Please check 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. if so you can then try the below steps

I had a Windows Server 2012 R2 before and the redirected printers worked all the time with no problem.

Also i noticed it looks like all the redirected printers use Remote Desktop Easy Print, which made me also disable it on gpedit.msc, but nothing seemed to change and the problem persists.

I'm having the same issue with Server 2016. All of the above settings on this thread and the others are set as recommended. After restarting the server, some users can the redirected printers in Settings. Others still have the problem. The next day redirected items are missing.

We have a RemoteApp environment running on Server 2012R2 with one server acting as Connection Broker, Gateway, and Web Access and then Two RD Session Host servers. We have NAV published to all of NAV users Desktops and everything is working for the most part, but some users have started to have issues with printing settings. The printer in question is on a print server and deployed to users through Group Policy and basic settings (like defaulting to two sided) are configured on the print server. The users that are having issues have changed the defaults on their local machines and we do not have a policy set to overwrite local settings after the user has set it.

When the user logs into NAV and goes to print the redirected printer settings are the default settings from the print server, not the settings on the local machine. There have been no changes to the environment recently to make changes like this happen.

I added a print server role to our new 2008 R2 server and started adding printers to it that will be available to Remote Desktop sessions. When I added the Remote Desktop services role, I specified printer redirection, thinking that would be a good thing.

It sounds like you have the printers installed on the RDS server, which will become local printers to the users who have a session on the RDS server, and you have the same printers being redirected from the RDS client to their session (their local printers redirected to the RDS session). You only need to have one or the other, not both. Here are two methods to deal with this, although I would recommend option 1.

When I log into a Server 2008 Server as Administrator, and I view the Printers folder (or use the Print Management tool) I only see my printers, and printers created via a 3rd party tool, Screwdrivers. I don't see the redirected print queues created for remote desktop users. Is there any way to see or manage these print queues as an administrator?

i setup GPs under each computer OU for printer deployment, sharing them on a central server. no GPs are set under the user OUs everything is computer based, and the properties are set in the computer policies.

the GPs work to an extent - the printers show up, but so does all the other ones.. for example, i have a policy in dtsc that deploys the dtsc printers from the server. but dtsc can also see the lvm and nm printers even though the lvm and nm polocies are not linked under the dtsc ou? each printer has (redirect 1) listed at the end of it as well

You could create security groups for the computer groups, then add the computer accounts to each of the computer groups. Then set the Security Filtering of the group policy to add the printers to only apply the printer GPO to the group you want it to and remove Authenticated Users.

A while back, I worked on an interesting issue involving RDS EasyPrint. The issue was that the printers from the client were getting redirected in the RDS session using easy print driver. However no print job could be printed to these redirected printers. Interestingly, no events were reported in the event logs, the print job just appeared in the redirected print queue for a few second, and then vanished. We paused the print queue of the printer on the client, but no print job came through to the print queue.

So it seems like the job does leave the server for the client. Now, looking at the Process Monitor log collected from the client, I first went to the process tree view, and do see the tswpfwrp.exe process, as a child process of Mstsc.exe.

So it seems like we are failing to convert the XPS job we got from the server and send it to the print queue at the client. To ensure that we are headed in the right direction, I created a test XPS print job on my workstation and at command prompt ran the following command:

I have a user who prints to her home printer while connected via RDP to her work PC. Both home and work PCs are Windows 10, latest 1903, all updates. Printer is your basic Officejet Pro 8600. This worked without issue until I updated her client to 8.10.2.55 version, including the 1901 hotfix. It was impossible to resolve the issue until I fully uninstalled Sophos Encryption. I tried everything, including turning office Remote Easy Print via GPO and going with the local drivers, matching exactly. Same issue. It instantly fails on the office PC, with an immediate error. Nothing ever makes it to her home PC printer, via print queue, etc. As soon as I fully uninstall Sophos / Decrypt system, etc.....all RDP printing works to her home printer from her work PC, via RDP. I re-installed everything again, printing fails. So I know it's something with the encryption / Sophos Safeguard. I hate to roll her back to the older version, which I think was 8.0 something...but I may have to if there's no help.

Is it giving you any error message? Could you please try the steps provided in this article and see if you are able to print with Safeguard installed? Also,for testing purpose give it a try by excluding the mapped drive for the printers in the File Encryption policy and see if the behavior continues.

They do have file encryption enabled, but are not using it. Ironically, they will be soon and that was a feature I added recently to all of their workstations. But again, I have not enabled any file shares yet. Let me try the steps from that article and get back to you. Here is the error, which does appear to be exactly the same as described in the article. They are on 8.10 already.

We understand your concern regarding the version as well but the problem may occur due to the subversion of the 8.10. I'd request you to apply the workaround mentioned in the KB article suggest by Shweta however, I'd request you to open a support case here as the KB is specifically for the error which appears when files are on network share and they are encrypted.

I am upgrading the management center / server to 8.20 to see if it helps. I never realized this was available for download. Once I update this client with the new version, I will let you know if the problem persists.

Updated to version 8.20. Same problem, will not print. Only get instant error. I uninstalled ONLY the File Encryption component on the client PC, leaving just Native Device Encryption, and the RDP printing worked normally. So the issue is definitely the File Encryption component / driver / etc. I will respond to the Sophos case email now with all of the details.

Would you please suggest whether you have installed File encryption Build 29 on the machine where you have an issue? If yes, please refer to this article as build 29 is withdrawn as it has a few issues and bug. We suggest using build 28 which doesn't have such an issue with it.

3a8082e126