[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Can't print or change printer properties in RDP session

Posted on 2012-08-31
9
Medium Priority
?
8,960 Views
Last Modified: 2012-11-30
I have a new bare installation of win server 2008 r2 foundation set as DC with 8 local PCs connected on the LAN, installed RDS & 5 CALs for remoting. I have 3 win xp pro client PCs that remote in to run 1 application. I have installed printer drivers on the server that the remote PCs use. I installed Print & Document services & Remote Desktop services.

The local users on the LAN have no problems at all printing. The remote PC users have no problem connecting to the server & the user's session shows the local  printer  when remoting in but when a test page is sent to it, nothing is printed. If I try to look at the printer properties, such as sharing, security, etc., they are greyed out. Even if I remote in as admin, my printers transfer but all property options are greyed out. If I choose to look at the security & choose the user such as admin, the option boxes to allow print, manage docs, manage printers, etc. are all greyed out. I have added users to the printer operators group but still no change.

Is there a setting in group policies that I am missing or do I need to install or uninstall roles?

Thanks
0
Comment
Question by:mimi8118
  • 4
  • 4
9 Comments
 

Author Comment

by:mimi8118
ID: 38356144
I installed Print & Document services & Remote Desktop services roles.
0
 
LVL 18

Expert Comment

by:Netflo
ID: 38357200
Hi,

You may not be aware, but Server 2008 R2 has a feature called Easy Print, which gets around the need to install printer drivers on the server itself, as it was required on Server 2003.

I must say it does work flawlessly. Locally defaulted printers seamlessly map across into the RDS environment. You're going to need to apply a few updates for everything to work as expected.

- For your Windows 7 clients, it will work out of the box as is.
- For Vista clients, I would recommend updating the RDC client to 7.0: http://support.microsoft.com/kb/969084
- For your XP clients, you need to update them to RDC 7.0 and install .Net 3.0 SP1: http://support.microsoft.com/kb/969084 and http://www.microsoft.com/en-us/download/details.aspx?id=21

I would recommend uninstalling the printer drivers you have installed and setup, as this may duplicate the printers that appear on the RDP session and confuse users and yourself when troubleshooting.

For more information see this link: http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx

Let me know how you get along.
0
 

Author Comment

by:mimi8118
ID: 38365195
Thanks for your response. I found that even with updates to the client PCs, Easy print still had some problems with some printers. I changed the group policy for remote desktop services / printer redirection from "not configured" to "enabled" which forces easy print to be used first. No luck, even with print driver installed on server. I then changed it to "disabled" and it printed immediately & allowed sharing, properties, etc. to work. Not greyed out anymore.
Hmmmmm.....??

Thanks.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 18

Expert Comment

by:Netflo
ID: 38365798
I would like to say remove the printer drivers you've installed for say one of your printers and let Easy Print try, even though you have configured GPO.

Just to ask, when you mentioned that you've "still had some problems with some printers", could you describe in a little more details what problems you've been having? Print output not as expected? What make / models are these printers?
0
 

Author Comment

by:mimi8118
ID: 38365977
Most problems were on my test printer, HP Color CP1518ni.
It would show up as default printer in my session but I could not get it to print a test page or txt page. Nothing ever got to the printer. I would go into the properties of the printer but any & all settings that should be able to be changed such as sharing, user permissions, etc. were greyed out. I've already tried what you recommended with no luck. As soon as I disabled easy print, all worked fine. I agree that having print drivers on the server is not recommended but easy print from XP PCs, even with the updates, wouldn't work.
Thanks,
0
 
LVL 18

Expert Comment

by:Netflo
ID: 38365991
Can you disable "enable advanced printing features" on your HP and try again.

How to disable "enable advanced....": http://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures
0
 

Author Comment

by:mimi8118
ID: 38366032
I removed the pseudo HP printer from the server & it printed & properties are working fine.
When the pseudo printer driver is removed, does it leave anything behind? Will I have to reboot the server to completely remove it? Just for future referenceeeeeeeeeeeeeeeeeee.

Thanks for your help!!!
0
 
LVL 18

Accepted Solution

by:
Netflo earned 2000 total points
ID: 38370319
If you remove the driver, its gone. No reboot is required. You're welcome :)
0
 

Expert Comment

by:nmxsupport
ID: 38648241
The advanced print options are greyed out when I connect to my remote desktop server - even logged in as domain admin.  How can I change the advanced print options?

thanks
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Suggested Courses

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question