Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Security and account managing cmdlets should support System roles and Creator-Owner role. #596
As requested in issue #595 "Everyone" as well as dynamic & special roles were hard to work with using the built in cmdlets.
It should be possible to work with them in the following manner:
#get "Everyone" role from "default" domain Get-role -Identity "default\Everyone" #get "Creator-Owner" dynamic role Get-role -Identity "Creator-Owner" #get "Everyone" dynamic role Get-role -Identity "\Everyone" #Create ItemAcl with the above roles. New-ItemAcl -Identity "default\Everyone" -PropagationType Any ` -SecurityPermission DenyInheritance -AccessRight * New-ItemAcl -Identity "Creator-Owner" -PropagationType Any ` -SecurityPermission DenyInheritance -AccessRight * New-ItemAcl -Identity "\Everyone" -PropagationType Any ` -SecurityPermission DenyInheritance -AccessRight *
Since this is fixed on platform level - other cmdlets dealing with roles should also accept it now.
added a commit
Mar 4, 2016
For the benefit of users that come here... we discussed it on the call - it is consistent with how we do it in other cases. The
Having it specified as