Configuring Printers for Terminal Services

I would like to know the easiest way to achieve the following:

Location 'A'
Terminal Server (W2K3 Server) named 'TS_A'
Primary Domain Controller (W2K Server/Active Directory) named 'PDC_A'
Printer named 'ShipPrinter_A' is a network printer shared as '\\PDC_A\Shipping' on IP 192.168.1.100

Location 'B'
Backup Domain Controller (W2K Server/Active Directory) named 'BDC_B'
Printer named 'ShipPrinter_B' is a network printer shared as '\\BDC_B\Shipping' on IP 192.168.2.100
Terminal Services Client (XP Pro) named 'Client_B' has added 'ShipPrinter_B' via Control Panel
Terminal Services Client (XP Pro) named 'Client_B' has a Local Printer named 'ClientPrinter_B'

Location 'C'
Backup Domain Controller (W2K Server/Active Directory) named 'BDC_C'
Printer named 'ShipPrinter_C' is a network printer shared as '\\BDC_C\shipping' on IP 192.168.3.100
Terminal Services Client (W2K Pro) named 'Client_C' has added 'ShipPrinter_C' via Control Panel
Terminal Services Client (W2K Pro) named 'Client_C' has a Local Printer named 'ClientPrinter_C'
Terminal Services Client (W2K Pro) named 'Client_C' has a PDF Print Driver installed named 'PDF_C'

Currently, both client computers see the following printers in a Terminal Services Session:
ShipPrinter_B on BDC_B (from Client_B)
ClientPrinter_B on Client_B (from Client_B)
ShipPrinter_C on BDC_C (from Client_C)
ClientPrinter_C on Client_C (from Client_C)
PDF_C on Client_C (from Client_C)

Neither computer sees 'ShipPrinter_A'

I would like 'Client_B' to see only 'ShipPrinter_A',  'ShipPrinter_B', and 'ClientPrinter_B' while in a Terminal Services Session

I would like 'Client_C' to see only 'ShipPrinter_A',  'ShipPrinter_C', 'ClientPrinter_C', and 'PDF_C' while in a Terminal Services Session

I have this issue compounded by additional computers and printers causing dozens of printers to choose from when printing in a Terminal Services Session.

A quick and easy solution (if this is possible) would be greatly appreciated.

Thank you.

btaplin
LVL 1
btaplinAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

btaplinAuthor Commented:
Also, clients are using 'Remote Desktop Connection' to connect to the Terminal Server.

0
kain21Commented:
Shared printer installs in a domain are user account specific... if ShipPrinter_A was installed under a different account than the users are using in their terminal services session then it needs to be installed manually in their account profile... also you could delete any other printers that aren't setup to local ports on the terminal server without affecting other users...  this would get rid of any other unwanted printers... as for the local client printers... sounds like they're being pulled across via the terminal services session which is the way you would want it for this setup...  One other thing... look in folder options under the terminal services user account profiles and make sure the "Automatically search for network folders and printers" option is off or the shared printers on the network will show back up after time....
0
btaplinAuthor Commented:
Thank you kain21,

Sorry, I have been away from the office for awhile and just flew back into town last night.

I think my problem exists because the users do not get their own 'desktop' when they log into terminal services. Instead, a single application loads, and when they quit, they are logged out of the server.

This was a quick and easy way for me to temporarily deal with a security issue. Shortly, I will have enough time to setup the required security levels in Active Directory for this server. At this point the users will have a 'limited' desktop and very specific access to 3 or 4 applications.

My thoughts are to setup the 6 network printers (approx) that users will be able to print to on the terminal server itself. I will also NOT allow the connecting users to map their local printers. Does this make sense or will I still have the same problem?

Thanks again.

btaplin
0
kain21Commented:
If you setup the 6 printers as local printers on the server then they would carry through to the individual profiles when they login.... you could set the security permissions on the printers themselves to allow only certain people to print to each printer...

note... they would have to be setup as local printers (i.e. TCP/IP port mapping or directly connected to the computer) for the printers to carry through to the individual profiles...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.