Re: Print Groups
- From: Steven <Steven@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Oct 2008 13:13:07 -0700
Alan,
The consept makes perfect sense but I'm getting errors. On my test
environment I get 6 out of 6 replies indicating "succceeded" however after
those 6 successful replies I get pSecurityDescriptor not recognized, "C" is
not recognized, IO is not recognised and DWO is not recognised. So I have to
believe I am missing something in the syntex. Can you offer any advise??
Note: Permissions did not change even though indicated suceeded.
--
Steve
"Alan Morris [MSFT]" wrote:
Your descriptor will differ, do not cut and paste this data for your use..
Setup a printer with the security setting you desire.
This example takes the modified security descriptor from a printer shared
from the server, displays current security, then sets the security on a
printer shared from a clustered spooler.
G:\>setprinter -show \\standalonemachine\standalone 3
pSecurityDescriptor="O:BAG:DUD:(A;OIIO;RPWPSDRCWDWO;;;BA)(A;;LCSWSDRCWDWO;;;BA)(A;;SWRC;;;AU)(A;CIIO;RC;;;CO)(A;OIIO;RPWPSD
RCWDWO;;;CO)(A;OIIO;RPWPSDRCWDWO;;;PU)(A;;LCSWSDRCWDWO;;;PU)(A;;SWRC;;;PO)"
current security from cluster shared printer
G:\>setprinter -show \\cluster\sharedfromcluster 3
pSecurityDescriptor="O:BAG:DUD:(A;OIIO;RPWPSDRCWDWO;;;BA)(A;;LCSWSDRCWDWO;;;BA)(A;;SWRC;;;AU)(A;CIIO;RC;;;CO)(A;OIIO;RPWPSD
RCWDWO;;;CO)(A;OIIO;RPWPSDRCWDWO;;;PU)(A;;LCSWSDRCWDWO;;;PU)"
setting the new security descriptor
G:\>setprinter \\cluster\sharedfromcluster 3
pSecurityDescriptor="O:BAG:DUD:(A;OIIO;RPWPSDRCWDWO;;;BA)(A;;LCSWSDRCWDW
O;;;BA)(A;;SWRC;;;AU)(A;CIIO;RC;;;CO)(A;OIIO;RPWPSDRCWDWO;;;CO)(A;OIIO;RPWPSDRCWDWO;;;PU)(A;;LCSWSDRCWDWO;;;PU)(A;;SWRC;;;PO)
"
Set printer on '\\cluster\sharedfromcluster' succeeded.
you can set all the printer on the cluster or remote machine
G:\>setprinter \\cluster 3
pSecurityDescriptor="O:BAG:DUD:(A;OIIO;RPWPSDRCWDWO;;;BA)(A;;LCSWSDRCWDW
O;;;BA)(A;;SWRC;;;AU)(A;CIIO;RC;;;CO)(A;OIIO;RPWPSDRCWDWO;;;CO)(A;OIIO;RPWPSDRCWDWO;;;PU)(A;;LCSWSDRCWDWO;;;PU)(A;;SWRC;;;PO)
"
Printer (1 of 825): \\cluster\Xerox
Set printer on '\\cluster\Xerox' succeeded.
Printer (2 of 825): \\cluster\HP
Set printer on '\\cluster\HP' succeeded.
..................................
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steven" <Steven@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:958DC2C1-0B58-47B2-9AAF-8767E4DF38B1@xxxxxxxxxxxxxxxx
excellant, I love it, can you give me a better example so I don't mess
things
up? One for test and then one for all printer objects on a server. Sorry
to
ask but I don't have much time to dedicate to this, wish it was 2008
server.
Note: this needs to be done on a cluster as well as a dozen or so
standalone
servers.
--
Steve
"Alan Morris [MSFT]" wrote:
use \\clusteredprintservername rather than "" to perform the operations
remotely.
Printername == \\cluster\modifiedsecurityprinter
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Alan Morris [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OfgGLUyIJHA.3708@xxxxxxxxxxxxxxxxxxxxxxx
I have some good news and bad news
first the good news
setprinter.exe in the Windows resource kit to to set all the printers
on a
machine with specific permissions. Change the settings on one printer,
then view the settings, then change them for all the printers on the
server.
setprinter -examples 3
Used to set print queue security. Note: Security settings can only be
set
as a whole. No
support is provided for partial modifications.
To see current settings:
SetPrinter -show PrinterName 3
To change security settings (see "Security Descriptor String Format" in
MSDN or SDKdocs for details):
*** WARNING: this could make the print queue inaccessable and require
the
use of a
registry editor to fix ***
SetPrinter PrinterName 3
"pSecurityDescriptor=O:BAG:DUD:(A;CIIO;RC;;;CO)(A;OIIO;GA;;;CO)(A;;SWRC;;;WD)(A;CIIO;GX;;;WD)(A;;L
CSWSDRCWDWO;;;BA)(A;OICIIO;GA;;;BA)(A;;LCSWSDRCWDWO;;;PU)(A;OICIIO;GA;;;PU)"
to change this for all printers on the server
SetPrinter "" 3
"pSecurityDescriptor=YOUR_SECURITY_DESCRIPTOR_FROM_BASE_CONFIG
now the bad news
the setting will need to be updated for each new printer
but I have some good news
Server 2008 + supports changing the default printer security
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Steven" <Steven@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F7DEA2E-BB82-4C02-985A-4DD9FF068A31@xxxxxxxxxxxxxxxx
I was told in general questions to post this question here:
I have an existing print cluster with hundreds of printers on a
Win2003R2, I
need to create a new group (or edit Power Users group) and give them
Manage
Documents ONLY, the 4 default groups do not give me what I need. How
can
I do
this without touching each and every print object as well as make it
the
default for new printer objects?
--
Steve
--
Steve
- Follow-Ups:
- Re: Print Groups
- From: Steven
- Re: Print Groups
- References:
- Re: Print Groups
- From: Steven
- Re: Print Groups
- From: Alan Morris [MSFT]
- Re: Print Groups
- Prev by Date: how many virtual IPs do I need
- Next by Date: Re: Print Groups
- Previous by thread: Re: Print Groups
- Next by thread: Re: Print Groups
- Index(es):
Relevant Pages
|
