Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've been chasing the following issue for half a year now at our company and ask for help on the matter:

Users of a branch office (x86 clients) loggon to a Windows Server 2008 R2 x64 terminal server and carry over their printers as redirected printers. Necessary drivers are installed on the terminal server.

Now with 3 new printers (all Hewlett Packard) the printers are redirected just fine, but the printer device settings (duplex, trays) are not taken over from the client to the terminal session.

Background info:

At the branch office all printers are installed on a windows server 2003 x86 server and shared with the clients. settings on the local network are taken over as they should

Strangely it works without problems with a few older HP printers still in the network. Also, we had that problem before our upgrade to ws2008 as well, but with the ws2003 servers you could manually edit printer device settings with an administrator account. However, with ws2008 the owner of the redirected printers is SYSTEM and all options are greyed out. Addionally modifications are lost when the user logs off and on again.

I am thankful for any solution

share|improve this question
    
Do you have to use the printers through the terminal server client? Is there any chance you can simply map to the printers directly within the terminal server session? –  Zoredache Feb 28 '12 at 18:54
    
BTW, you are certain the correct driver is being used and not the EasyPrint driver right? –  Zoredache Feb 28 '12 at 18:56
    
Thanks for replying. The driver is used correctly - no EasyPrint. About directly mapping: the clients are ultimately connected to the terminal server within a VPN environment. If there is a way to go backwards on that and connect the printer from the terminal session I sadly don't know it –  LumenAlbum Feb 28 '12 at 22:31
    
I see, I was just hoping I could suggest an alternative that might work. We have a similar situation with Canon print drivers while connecting hosted application. AFAIK, there is no solution. –  Zoredache Feb 28 '12 at 22:37
    
Thanks anyway. So far I could postpone this problem by writing a program in C# that manipulates the necessary values in the registry. however that is only a workaround and no permanent solution in the administrative sense –  LumenAlbum Feb 28 '12 at 23:26

1 Answer 1

I am having the exact same problem at different clients/sites/servers. Printer options (like optional trays) are not available from within an rdp session. Printer driver is correctly installed, printing works. After taking over ownership we can add additional trays, but after logoff/logon, the printer is recreated without the extra options. Do you want to share te source of the program in C# you wrote?

share|improve this answer
1  
Please don't write comments like this as answers - it contributes nothing to the problem and should be a comment instead. –  SvW Nov 8 '12 at 8:51

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.