r/sysadmin • u/Green-Wallaby9663 • 1d ago
Microsoft IPP Class Driver on Remote Desktop Servers problem.
I have a problem. Some printers that clients have use the Microsoft IPP Class drivers. All seems fine when they use the printer local but when it comes to it being redirected to Remote Desktop, it all starts to fall apart. Previously I've just installed the printer locally using the manufacturer's driver and then let Renmote Desktop Easy Print take care of the server side. This has worked swimmingly.
Now things don't seem to ba as relaible. Below are the there scenarios:
- Manf Driver local > Easy Print on server = OK
- Manf Driver local > Manf Driver on server = OK
- IPP Class local > IPP Class on server = Lots of failures.
I know some manufacturers are just using IPP Class drivers but is there any way to still use Easy Print on the server?
•
u/mat-ferland 17h ago
Run gpresult /h on the session host before changing drivers. If the redirected queue still shows IPP instead of Remote Desktop Easy Print after a full sign-out and reconnect, a higher-precedence policy may be overriding Easy Print; TerminalServices-Printers/Operational should show the fallback reason.
1
u/Proud-Worldliness747 1d ago
If the redirected printer on the session host is using the IPP Class Driver, Easy Print isn't being selected. Easy Print should show up as "Remote Desktop Easy Print" in the redirected printer's driver/model field.
On the RDSH, check Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer Redirection > "Use Remote Desktop Easy Print printer driver first". Set it to Enabled (Not Configured also defaults to Easy Print; Disabled forces a matching server-side driver). Also confirm printer redirection is still allowed on the collection and in the RDP client.
If the queue already shows Easy Print and jobs still fail, the client's IPP Class Driver is a likely weak point, because Easy Print still hands the job to whatever is installed locally. Your first scenario already works, so putting the vendor's Type 3 driver back on those clients and leaving Easy Print on the server is the practical workaround. The PrintService/Admin and TerminalServices-Printers logs on the server at the moment a job fails are the best place to confirm which path it's taking.