RDS and Printing

Question

Afternoon

Could really do with some help with this.

We have RDS, recently upgraded from Server 2016 to 2019 (April 2020). We have 4 hosts, 1 connection broker server and another gateway server. We also have a print server running on server 2016.

RDS is in general working fine and until 3 weeks ago, so was our printing.

Our users will normally connect a printer to their RDS session via the print server - that part of the process works fine, the printer is showing as available and even shows the ink status.

However most cannot now print, the users are not getting an error and from their point of view, the print job should go through. It even registers briefly on the print queue. Our print server does have an error on the servers Events section

The document Print Document, owned by user, failed to print on printer Eye Permit Office. Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 120665. Number of bytes printed: 65577. Total number of pages in the document: 4. Number of pages printed: 0. Client computer: servername. Win32 error code returned by the print processor: 2152796175.

We are geographically spread out so as stop gap, I have installed key printers on site DC's and they can connect and print that way.

Our Group Policies haven't changed and apart from Windows Updates (I have tried uninstalling the latest batch just in case), there has been no other changes to the setup.

If anyone else has any thoughts, I'd be very grateful to try them.

Many thanks

Graham

Answer 1

HI
“RDS is in general working fine and until 3 weeks ago, so was our printing. ”
1.we can run below powershell command on issue RDsession host server then check which update patches we installed before 3 weeks ago.
$QFE = Get-hotfix -computername $server | select-object -property Description,HotFixID,InstalledBy,InstalledOn | out-file c:\windows\temp\$server.txt
change $server to hostname

2.what's the issue printers model ?
3.If you print "test page" on both printer server and session host server respectively, do they all cannot print and print jobs stay in queue?
How to Print a Test Page in Windows
https://www.dell.com/support/article/sg/en/sgbsd1/sln153411/how-to-print-a-test-page-in-windows?lang=en

4.which printer policy did you use ?
did you deploy printer policy on printer server by using “the users that this GPO applies to(per user)” or “the computers that this GPO applies to(per machine)” like picture ?
did you deploy printers from printer server to both client win10 computer and RDsession host server ?

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731292(v=ws.11)?redirectedfrom=MSDN

5.if we install the latest update on one of issue session host server,will can not print issue also happen on this RDsession host server ?

Answer 2

Hi and thanks for replying.

The printers are Ricoh and test prints via the print server work fine. I have noticed something which may help though. The print drivers are all set to the PCL6 V4 Driver for Universal print, however when the user connects to the printer via their RDS session, the driver shows the Ricoh driver for the model. Showing the printer properties as administrator shows the PCL6 V4 driver.

Currently we don't deploy printers via Group Policy

As mentioned, the servers are currently up to date but I have rolled back one of them to before the issue started but this has had no effect.

Printer redirection is disabled by group policy and as we want our users to decide what printer to set as default, the Turn off Windows default printer management policy is Enabled.

Thanks

Graham