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.
Because they're not joined to the domain i cant browse to their local machine. Do you think that because their local machines aren't joined, that any printers connected locally won't map when connected on the TS? This may be the cause, but i doubt it as when the user was on server they were able to use their printer fine, but we used tricerat screwdrivers whilst on server , but they dont do a compatible 64bit server version that works on our server!
If you're dealing with a remote user and you want to connect to a share, the most painless ways is to go to:. One of the limitations of remote access is poor name resolution especially when it comes to windows networking. But we managed to get it working! Had been messing around with GP alot recently locking down workstations etc whilst moving to the new server and must have accidently turned off one that had something to do with easy print cant remember the exact one that it's called now.
Ryan - all the machines in my case weren't on the domain either - but you can still share printers on the workgroup. When you connect to the printer from the TS you'll need to enter the credentials for that machine, that's all. What's the problem with the method i provided, where isn't it working?
How did you get it fixed in the end? To continue this discussion, please ask a new question. Which of the following retains the information it's storing when the system power is turned off?
Submit ». Get answers from your peers along with millions of IT pros who visit Spiceworks. On the TS server, Longhorn Server needs to be installed. That is all! No additional drivers need to be installed; no additional configuration needs to take place. On the TS client, the user must be running TS client 6. NET Framework 3. Both TS client 6. As mentioned above, the general idea behind the solution is to make a driver on the server that redirects all printing related work to the local machine.
The implementation of this solution comes in two pieces. The first piece is presenting the user with printing preferences through UI so that they may configure the print job on any printer they have.
Instead of creating some server side UI that will show the bare minimum of preferences users need such as number of copies, landscape v. When the user edits preferences for a print job on a redirected printer, the TS client will launch this UI from the local machine on top of the remote session. If users connect to RD servers through RD Gateway, make sure that the option to deny client printer redirection is disabled in the RD Gateway settings.
This print driver supports a variety of printer models. In this case, you can install the necessary print driver manually on the RDS server. And also check the correctness of the service permissions:. After the Remote Desktop Easy Print policy is activated, you can delete the native printer drivers from the server.
Go to the Drivers tab and remove all unnecessary drivers except Remote Desctop Easy Print select the drivers in turn and click Remove. By default, the number of redirected printers in the RDS session is limited to You should set MaxPrintersPerSession value to the desired maximum number of redirected printers.
0コメント