Skip to main content


Took me quite a while to get this figured out, so might as well add to the pool of searchable Google results.

Problem: You have a clustered print/file server running Server 2008/R2 and you must make NTFS security changes to each printer.  You want to allow the IT Helpdesk people to manage documents.  You have 200+ printers.  Doing them one-by-one leads you to thoughts of suicide or worker's comp from limb amputation.

Solution: Quick little Powershell/subinacl combo! (see below)

Key things I learned in this was that WMI is not really supported for clustering, win32_clustershare was accidentally left out of Server 2008 SP2, and that a cluster's 'shares' are only visible on the active node (obviously, in hindsight).


If anyone has suggestions to better the script, please post them.  I am pretty new to scripting (the act of, not knowledge of).  Some limitations I know of already are that it doesn't check for existing permissions - if existing permissions are present, it deletes them and then adds in the new permission set, even if they are identical.


  1. Hotfix (KB971403) if running 2008 SP2 (requires reboot)
  2. 'subinacl.exe' with correct path (or updated script path)
  3. Script contents in a .PS1 file
  4. Ability to run scripts on the server
  5. Script must be run on the 'Active' node in the cluster
  1. # Mass printer security change, Chris Trotter, April 2012
  2. # Set the 'shares' variable, type '1' is a printer object
  3. $shares = gwmi -query "select * from win32_clustershare where type='1'" | select Name
  4. # Loop that applies each actual share path into the subinacl.exe arguments
  5. # Note also that the AD domain\group and security level (M) are hard-coded
  6. foreach($objitem in $shares){c:\scripts\subinacl.exe /printer $ /grant="testlab.local\IT Helpdesk Print Queue Management"=M}


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…