shonadle
asked on
Best Printing Option for Terminal Services?
I have a new customer and this office (mostly Windows 7 workstations) is a remote office which remotes into a Windows 2003 server using that version of Terminal Services. When a user from this office printers, it's through the generated printers from these sessions. Most of the printers are USB only and are shared through the PC making the connection.
Users try to print through printers from other user sessions which causes problems as those sessions become disconnected over time. I've thought about setting up a printer on the remote server using the external IP number of this office and allow the printing to work through the router. But I wondered if there was a better way? I'm not a terminal services expert and in other software I found when you go to print, it can generate the local printer dialog to pop up for the user in the local session. But I am sure Windows Terminal Services doesn't support this. Maybe there is some software that will work with it and help this along? Or does anyone have any other ideas on what to do?
Users try to print through printers from other user sessions which causes problems as those sessions become disconnected over time. I've thought about setting up a printer on the remote server using the external IP number of this office and allow the printing to work through the router. But I wondered if there was a better way? I'm not a terminal services expert and in other software I found when you go to print, it can generate the local printer dialog to pop up for the user in the local session. But I am sure Windows Terminal Services doesn't support this. Maybe there is some software that will work with it and help this along? Or does anyone have any other ideas on what to do?
ZabagaR
When a user RDP's to a terminal server, and they can see the other terminal user's mapped printers, it means those users accounts on the terminal server are "power users" or "administrators" (or at least elevated above power user). If those users that RDP to your terminal server are just in the Users group on the server, they will only see their own printers mapped back in their own session. Can you check that out?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
xBouchardx, is it really expensive? I don't know these customers very well yet so I have a feeling the will not be investing in a huge priced solution.
ZabagaR, I didn't look to see what level of permissions they had, but I did verify the printers that show up, some are from their own session and then they can see sessions of others. I thought about just connecting them locally to these shared printers but wasn't sure how to turn off seeing the other session printers so they don't have a bunch of duplicates.
ZabagaR, I didn't look to see what level of permissions they had, but I did verify the printers that show up, some are from their own session and then they can see sessions of others. I thought about just connecting them locally to these shared printers but wasn't sure how to turn off seeing the other session printers so they don't have a bunch of duplicates.
It could be cheap or expensive depending their/your viewpoint. I think a single license for it is around $900 for the year and I don't remember much more about it since I haven't set it up in a few years. Call their sales number from the website and they could tell you within seconds how much it would cost to license your environment. If you can afford it, it is well worth it. By far the best terminal printing solution I've ever used.
ASKER
Thanks xBourchardx. I'd prefer to wait and make sure there isn't a way to work it via Terminal Services straight first.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.