ScriptingGuy in this blog has dealt with and ably addressed the various limitations of the original system of setting permissions in Windows using Powershell, which was that you had to manipulate ACLs, never particularly easy, and also had the horrible 260 character path abortion of Windows 32 API to contend with. By providing the NTFSSecurity module, permissions have become much easier to configure in Powershell. All this is great because I have some permissions work to do in some of my scripts. Even on my home computer I would like to set permissions with a script command rather than muck around with Windows Explorer (waiting for it to update all the permissions on a big folder is quite time consuming).
How to edit file system permissions in Powershell
by
Tags: