This is tricky, since printers are mapped on a per-user basis and Win2K3 does not allow you to selectively map printers -- it's all or nothing. One option, if all of these 10-20 printers are not required for the applications running on the Terminal Server, is to share the essential printers with the network and let the users connect through network shares. Another option is to use a third-party printer management tool for Terminal Services that allows you to control which printers are mapped, or at least restrict it to the default.
Dig Deeper on Enterprise infrastructure management
Saving Costs Utilizing the Hidden Print Management of Windows 2003/2008, a video from BriForum 2009
Improved Terminal Services resource management in Windows Server 2008
Configuring Printers for Users - Terminal Services for Windows Server 2003
Managing Printer Drivers - Terminal Services for Windows Server 2003
Related Q&A from Christa Anderson
Expert Christa Anderson advises how to map images on a network share for user on a terminal server. Continue Reading
Expert Christa Anderson offers some ideas for monitoring who is connecting to a terminal server, and when they are connecting. Continue Reading
Expert Christa Anderson suggests some third-party software producst that can help in using a scanner with Terminal Services. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.