[Cronus]

Мне на ум приходят слова «Windows Server», «Roles» и «Print and Document Services»
Если на этом предприятии используется логин через Active Directory, ваша задача становится довольно простой:

For example, to give five users access to a particular printer, you could add all five user accounts, one at a time, to the printer permissions list. Later, if you wanted to give the same five users access to a new printer, you would again have to specify all five accounts in the permissions list for the new printer. Or, you could take advantage of groups with domain local scope. To do so, perform the following steps:

1. Create a group with domain local scope, and assign it permission to access the printer (this is the Resource group).
   
2. Put the five user accounts into a group with global scope (this is the Accounts group), and add this global group to the group having domain local scope. (Global groups are described in the next subsection.)

Now, when you want to give another five users access to this printer, you can simply add them to the global group that is a member of the domain local group which has permission to access the printer, and you are done. Doing so gives all five new members of the group access to the printer in one step. Using domain local groups in this way provides the following benefits:

• Membership of the domain local group is controlled by the administrator(s) where the resource (the printer) is located, not where the users are—which makes it in line with how administration is typically done.
  
• Because a domain local group is associated with an access token built when a member of that group authenticates to a resource in that domain, unnecessary network traffic (carrying of membership information) is avoided. (If, instead, you assigned a global group permission to access the printer, the global group can end up in a user's token anywhere in the forest, causing unnecessary network traffic.)

http://technet.microsoft.com/en-us/l.../bb727067.aspx