Where a user absolutely needs to print to a usb printer and not one of our network printers I just install the print driver for that particular printer on the terminal server s. Cumbersome yes, but better than the bloody head prints on my desk trying to get "easy print" to work easily.
Could be that the local printer is using host based drivers which wont work well with easy print. If thats the case, try using a universal driver just for terminal services, as that will typically bypass the host-based drivers which dont play nice. I remembered an old issue we had once with printing to a local printer via a remote desktop session. In order to get the printer working I had to add it to the server. That way the server had the printer drivers and could deal with the print outs.
There was a great TechNet article describing the order Windows uses to build the print outs when remote desktopping. Can't locate the article right now but I'll post it if I find it later. For now, if possible you may try going to the Windows server and adding a printer which uses the same driver that matches the local user's printer. Depending on the type of printer you may have to actually hook one up to the server with USB to get the driver to install.
Oh, and all of our printers are IP, it's just this one printer the user has bought in from home she has on her desk that she wants to print to. I've had this issue on one of our clients networks - with around 15 users each with a USB printer plugged into their local machine, using Terminal Services to print back to their local printer. You can imagine the fun i had. This is the best solution I came up with, and is working for all 15 of my clients machines through Terminal Services.
The only other problem you might encounter, when the user logs off and logs back on - it may show as limited access and you might not have permission. If this happens - let me know, there's a fix for that as well! The user's local machines are not joined to the domain as they are remote users so just got them all up and running on the terminal server. Forgot your password? UniTwain Universal Twain Driver.
Server 3. Client 3. Latest Release - Major Update 3. BUG FIXES - Solved issue with automatic client update on older versions - Solved a problem when temp log files were created on the server - Fixed issue with Open locally for Mac clients - Fixed compatibility issue for older Mac clients - Solved problem with GDI error on redirected printer - Solved problem with offline printer redirection.
Show All Releases. Releases Major Release 3. Minor Release 3. Mac Client Release 1. Major Release 3. Server Release 2. Minor Release 2. That worked. Hopefully we can get it to work without 3rd party. Thanks again. Since the RDP file issue is resolved, please find "redirectprinters:i: 1 " in the rdp file of remoteapp and make sure the value is 1. It created a Remote desktop virtual pritner but did not redirect any other printer. You might need to capture some dumps or traces to further investigate the issue, which I suggest to contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.
Remote Desktop Services Installation. Setting up Remote Desktop Services for my small business. I have configured the clients to redirect and use the printer driver that the client is using. This is resulting in Windows RDS server installing the same driver on initial connection which is fine. However, the printer once redirected continues to use "MS Publisher Imagesetter" and not the correct driver that was auto-installed.
I wonder if the reason for this is that the driver that gets installed on RDS is x64 and the clients are using x86 drivers. It tried installing the HP driver x86 version, but Windows Server complains and says that x86 drivers cannot be installed. I've submitted an issue explaining my findings and a workaround here.
Btw Microsoft's Remote Desktop application from Mac App Store is broken in this regard as there is no way to specify a specific printer driver and it always sets the driver to "MS Publisher Imagesetter" regardless of what is installed on the server. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Have you had this problem before? Hi, Your article was really helpful, I followed each and every step. Printer is showing in devices and printers in control panel. Please help. It did not help me.
0コメント