Remote session printing



  • I am trying to collect more information about printing through a remote desktop session from MacOS to a terminal server for a client.
    Works fine through Windows, and previously worked well from the Macs. One of the Macs takes as long as 25 minutes for the print job to hit the queue.
    I am posting to see if anyone here has knowledge of how print jobs are routed through the remote connection that can help me troubleshoot this.

    Thanks!



  • Can you just connect the printer to the computer direct IP?



  • The other oddity is that it does this with multiple clients on the Mac and also will not map printers mapped at login via GPO. It works fine to log in as the same user via RDP on a PC. But something with anything printer mapping/redirection when connecting from a Mac does not work.



  • @Aaron-Studer said:

    Can you just connect the printer to the computer direct IP?

    No and that's not the issue. We need printers on the Mac redirected into the remote session. But even ones mapped from the DC to the RDS server are not mapping but only when a user logs in from a Mac. It makes no sense. It just broke and I think it might be a Windows update.



  • did the driver name of the Mac's printer driver change? I know for the windows ones to work there needs to be a driver mapping setup.



  • @Dashrender said:

    did the driver name of the Mac's printer driver change? I know for the windows ones to work there needs to be a driver mapping setup.

    How would it have changed and what do you mean by driver mapping? When you install the printers you just install the x86 and x64 drivers to the server's local install. When you share them, it just grabs the appropriate driver and pushes it. I'm not sure what you mean by driver mapping.



  • @ajstringham said:

    @Dashrender said:

    did the driver name of the Mac's printer driver change? I know for the windows ones to work there needs to be a driver mapping setup.

    How would it have changed and what do you mean by driver mapping? When you install the printers you just install the x86 and x64 drivers to the server's local install. When you share them, it just grabs the appropriate driver and pushes it. I'm not sure what you mean by driver mapping.

    It's been a long time since I've dealt with TS. But if memory serves, there is a Printer name of sorts that the client will send back to the server (over the RDP connection) so the server knows what driver to use for the clients local printer. Back in the day it wasn't uncommon for server drivers to be 'named' something else inside the INF file than what the client was called. If these don't match up the server would not know what the printer on the client was.



  • @Dashrender said:

    @ajstringham said:

    @Dashrender said:

    did the driver name of the Mac's printer driver change? I know for the windows ones to work there needs to be a driver mapping setup.

    How would it have changed and what do you mean by driver mapping? When you install the printers you just install the x86 and x64 drivers to the server's local install. When you share them, it just grabs the appropriate driver and pushes it. I'm not sure what you mean by driver mapping.

    It's been a long time since I've dealt with TS. But if memory serves, there is a Printer name of sorts that the client will send back to the server (over the RDP connection) so the server knows what driver to use for the clients local printer. Back in the day it wasn't uncommon for server drivers to be 'named' something else inside the INF file than what the client was called. If these don't match up the server would not know what the printer on the client was.

    I could see that if you're using thin-clients but that's not what's going on here. RDP grabs the printer info and redirects it into the session. It's mapped and ported through via the Remote EasyPrint driver. However, it's not a driver disconnect. It's a straight up disconnect of anything printing. That's the really bizarre part.



  • @ajstringham said:

    RDP grabs the printer info and redirects it into the session.

    Is this part of the newer (ok anything newer in the past 3 years) version?


Log in to reply