I’ve had a beta version of the PAC module available on Script Center repository for quite a while now. It adds several new features, including the following:
- Active Directory objects are supported
- Desired State Configurations (DSC) resources available to automate access control settings (see about_PowerShellAccessControl_DscResources)
- Supports filenames longer than 260 characters (PSv3 or higher)
- Shows inheritance source for file, folder, registry key, and Active Directory objects (PSv3 or higher)
The documentation isn’t finished, and there are still a few bugs that I’m aware of that need to be fixed. I’ve been using it in its current form for a while, though, so I feel that it’s pretty stable. Give it a shot and let me know if you have any issues and/or questions (you can post here or on the Q&A section on the repository page.
The biggest problem I have with it is the speed (especially when working with AD objects). I’ve been playing around with moving some of it to C#, and I’ve noticed an amazing speed improvement. At some point in the future, the module will have at least some C#. I may one day make the entire module a compiled module (the source code will always be included).
Other features that will come in the future:
- Central Access Policies (view/set assigned CAPs for files and folders and view central access rules associated with the CAP)
- Conditional/Callback ACEs will show conditions (very similar to ACL Editor)
- File/folder dynamic access control tags will be viewable (and one day settable)
- Get-EffectiveAccess will show limiting CARs when a CAP is assigned (right now, CAPs should be taken into account, but it won’t show which CAR is limiting access)
- Get-EffectiveAccess will allow you to add group/device claims
Rohn's Blog 