This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 12%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hi all, found this script https://www.netwrix.com/how_to_export_folder_permissions.htmlbut only shows the subfolders under \fs1\Shared. If I need to include \fs1\Shared in the report also, can anyone help? Thank you!
This should work.
$path = "c:\temp" # The folder to analyze
$Report = @()
$FolderPath = @($path) # put top level folder first
$FolderPath += (Get-ChildItem -Directory -Path $path -Recurse -Force).FullName # append subfolder names
Foreach ($Folder in $FolderPath) {
$Acl = Get-Acl -Path $Folder
foreach ($Access in $acl.Access)
{
$Properties = [ordered]@{'FolderName' = $Folder;
'ADGroup or User' = $Access.IdentityReference;
'Permissions' = $Access.FileSystemRights;
'Inherited' = $Access.IsInherited}
$Report += New-Object -TypeName PSObject -Property $Properties
}
}
$Report | Export-Csv -path "C:\data\FolderPermissions.csv"
Thank you for your help as always.
Using the recurse switch will analyze the folder and subfolder. Without recurse, you only get the files in the root folder.
If your account does not have access to read the files, then you will get access denied errors and won't be able to calculate the full size of the folder.
$folders = "c:\temp", "c:\programdata", "c:\users"
$results = @()
foreach ($folder in $folders) {
$size = [math]::Round((Get-ChildItem -Path $folder -Recurse | Measure-Object -Property Length -Sum).Sum / 1GB,2)
$results += [pscustomobject] @{
"Folder" = $folder
"Size" = $size
}
}
$results
If you have many servers to analyze, then using Invoke-Command to run the analysis remotely will be faster because it eliminates the file I/O network traffic. In that case you would not refer to the share name, you point to local drive, E:\Data\SharedFolderName.
I don't know why your comment got deleted, but here is the script that was in my reply.
If you have a lot of servers with lots of files, then using Invoke-Command to execute the script against the local file system (E:\Data\SomeSharedSolerName) will run faster because it eliminates the network traffic.
$folders = "c:\temp", "c:\programdata", "c:\users"
$results = @()
foreach ($folder in $folders) {
$size = [math]::Round((Get-ChildItem -Path $folder -Recurse | Measure-Object -Property Length -Sum).Sum / 1GB,2)
$results += [pscustomobject] @{
"Folder" = $folder
"Size" = $size
}
}
$results
Just lovely. Now the deleted comments reappear.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
$FolderPath is the child directories under the given path. To include the path then just append it to your arrays you get back. The returned data is an array of file system objects. So you technically need a file system object for the root path as well. But since you don't seem to be using anything other than the filename here then you can simplify the code by just storing the filename.
$sourcePath = '\\fs1\Shared'
$files = dir -Directory -Path $sourcePath -Recurse -Force | Select-Object -ExpandProperty FullName
$files += $sourcePath
Then replace any references to $Folder.FullName with simply $folder as it now is just the full path.
If you really want to keep using file system objects then the code would look like this.
$files = dir ...
$files += Get-Item $sourcePath
Note that I'm assuming Get-Acl will work on the file share path. I've never tried it. If it doesn't then you'll need to get permissions a different way because a file share isn't a regular directory.