Skip to main content

Filesystem v 0.992

Just over a year after I published the first version of this module, and too many revisions to count later, I am fast approaching 1000 downloads!  This update takes the number of functions past 50 too!  Thanks to everyone who have given me great feedback! 

The latest release can be downloaded here. For more info on the module see here.

Bug Fix

removed the discovery error on load

Added Functions

get-sharePermission (not sure why it took so long for this one to appear)
get-NTFSBlockedInheritance - to compliment get-NTFSExplicitPermissions, this return the path of a folder if inheritance has been blocked

updated Function

get-NTFSExplicitPermissions - added an exclude parameter in the same way that get-NTFSPermission works




  1. Minor bug?

    When I create a new folder and share, and then add-ntfspermission, my script adds the permission, but the inherited permissions are not included.

    The only way I can get these to populate is either from a remote access to the folder to select the security tab, advanced, change permissions and select the "Replace all child permissions....etc" checkbox. Or on the server where the folder's been created, select the folder and when I get the prompt I don't have permissions..."continue?" Select continue and everything fine, permission entries are then populated.



    1. can you post your code please? changing the names of anything important of course :) I'll try to emulate your issue


    2. Hi there

      Apologies, just seen your response.

      Unfortunately, I've changed the code somewhat and don't have the original. I believe, my workaround was to create the folder first using New-Item as per:-

      New-Item -Path \\server\d$\foldername -ItemType Directory
      Add-NTFSPermission -path \\server\groups\$folder -object $resourcename -Permission Modify | Out-Null
      New-FileShare -name $folder -server servername -path path | Out-Null




Post a Comment

Popular posts from this blog

PowerShell 3 behavioural change

It's taken me way too long to get into PowerShell 3, I guess opportunity hasn't shown it's self until now and so, here, my V3 journey begins.

I was asked to debug a script that would run fine in PS v2 and not in v3.  The issue was a that a variable length was being checked and was failing in v3.  This is why...

In v2 if a variable is undefined, this test returns false

PS C:\windows\system32> $var.length -eq 0

In v3 the same test returns true....

PS C:\windows\system32> $var.length -eq 0

Not a biggie, but as in this case, a script has broken so something to consider!



Enable Powershell Remoting (WinRM) via Group Policy

I have been doing some testing on enabling WinRM via group policy, being that WinRM is the service that Powershell v2 sets up it remoting capabilities. Here are the GPO settings that you need to configure WinRM ....

set the winrm service to auto start

Computer Configuration \ Policies \ Windows Settings \ Security Settings \ System Services

Windows Remote Management (WS-Management)  set Startup Mode to Automatic

start the service

incorporated in to the above - you may need a restart.

create a winrm listener

Computer Configuration / Policies / Administrative Templates / Windows Components / Windows Remote Management (WinRM) / WinRM Service / Allow automatic configuration of listeners

IPv4 filter: *

* is listen on all addresses, or if you only want a particular IP address to respond use an iprange eg - don't forget that this IP range has to be valid for all hosts that fall in the scope of the GPO you are creating.  You can use -, - …

compare-object in Powershell - comparing mulitple values

I'm starting to use compare-object more and more, and one thing I noticed, is that you can compare 2 objects based on multiple attributes. here is how it is constructed...
Compare-Object -ReferenceObject $object1 -DifferenceObject $object2 -Property a,b,c,d,eIf a,b,c and d are the same, but e is different, compare object will return a difference. In the following example, I use "-eq $null" as a check because by default compare-object returns $null if the objects are the same.
#create an array of objects to check against

$collection = @()
foreach ($entry in ("aaaaa","bbbbb","ccccc","ddddd")){
   $store = "" | select "a","b","c","d","e"
   $store.a = $entry*1
   $store.b = $entry*2
   $store.c = $entry*3
   $store.d = $entry*4
   $store.e = $entry*5
   $collection += $store

#create an object similar to those in the array
$object = "" | select "a","b…