Print Operators

[Guest]

I need to certain users access to manage the printers on our print servers.

Currently we have a Domain Local Group (PrintOps-D) who is a member of a Global Group (PrintOps-G).  A user is added to PrintOps-G.

The PrintOps-D group is added to the local Print Operators group on the print server.  

In Printer Management the local Printer Operators is added to the Security tab of the sever with Print, Manage Print, Manage Documents and View Server permissions.  These permissions are then copied down to any new printer that is created.  

When looking at a printers properties as a PrintOps-G user everything is greyed out (Image 1).  If you goto the security tab and look at the effective permissions it suggest the user has all the required permissions (Images 2 and 3).

 

If I take the PrintOps-G group and add it directly to Print Management security the user can manage printers as desired.

 

Any idea what is the issue with the built-in Print Operators group?

 

1.

 

2. - Has server name removed

 

3. - Has username removed

[sc302 Veteran]

are your groups members of other groups that would deny rights or not give them rights?

[Guest]

Sadly not. I've gone bare bones and put the user in just two custom groups. One to allow RDP to the print server and the PrintOps group.

To make sure I'm not going mad I've even setup a test print server. Made the groups and group policies from scratch on a test domain. I can replicate the same issues.

Also if it was a deny the effective permissions should show that.

[+KibosJ Subscriber²]

As far as I'm aware you have to add your new group (PrintOps-G) to EVERY printer's security tab before they can manage it.

 

It's a pain and the only way I could allow manage access to printers on our print server :(

 

From what I could see, Print Operators group actually does nothing at all or at least for me, I could never get it to work.

[sc302 Veteran]

there is something up with the config, possibly a gpo effecting it or a parent directory/folder/server causing issues.

[+KibosJ Subscriber²]

Hmmm, maybe this will help :) not at work this week so can't check myself

 

http://support.microsoft.com/kb/940724

[Guest]

Print Operators was set on each printer. It's not that.

I've done live production and then went about creating new test users, groups, group policies and domain. I get the same issue on both sides. If its config related its a default config causing it.

These are 2008 R2 print servers. So its not that article.

I've been pretty much everywhere with this and as a last resorted posted it here.