Write-Host "Getting Share." -ForegroundColor Yellow #The share name you want to monitor share permissions on Write-Host "Created folder $TodayResultFolder located at $CSVPath" -ForegroundColor Yellow $TodayResultFolder = New-Item -ItemType Directory ($CSVPath + $ResultsFolderName) -ErrorAction Silentl圜ontinue Write-Host "Creating today's folder to store results in." -ForegroundColor Yellow #Creates todays folder to store results in #CSV path where the results will be stored $ResultsFolderName = ((get-date).ToString("MMddyyyy")) Write-Host "Getting today's date." -ForegroundColor Yellow
#Powershell monitor folder for new files install
The script does require the NTFSSecurity module which you can install by launching PowerShell and running Install-Module -Name NTFSSecurity If you want to monitor multiple folders/shares then set up a separate scheduled task for each and don’t forget to change the path where the results are stored and make it different than where other ones are stored so they do not overwrite one another. This is helpful if you need to troubleshoot an issue when setting it up in your environment.įor best results I recommend setting up a scheduled task that will run this script daily.
When the script runs the console will show what it is doing each step of the way. This can come in handy if you have it monitor multiple files/shares The body of the e-mail will tell you which folder/share had a permission change. Since Office 365 requires authentication the script will create a credential PSObject and export it, this will allow it to import the credential object the next time it runs to authenticate to Office 365 without it being stored in plain text.
To send mail we used the Send-MailMessage cmdlet. In my example I had it send mail using Office 365 by specifying my smtp server as in the script. If both NTFS and Share permissions changed it will e-mail you both attachments, if only one (NTFS or Share) changed it will only e-mail you the one that changed.
When the script sees that permissions have changed for either NTFS or Share it will e-mail you and the attachment like the one pictured above. The Account column will show you which account the permission changed for. The CSV file also shows you what permission changed and what it changed to in the From and To column. This allows you to get an overview what has changed and when, that will span more than a single day. A folder is created each day its ran with the name that follows MMddyyyyĮach time the script runs it will append any permission changes to the results CSV file instead of overwriting any previous results. The next day it will run it will import the previous days results and compare them to the results of that day’s. The folder name is the date which is formatted as MMddyyyy. To keep historical data I made it create a new folder for each day it runs. I wanted to know when permissions changed, how they changed (Read permission changed to Write permission), keep historical permission data I can reference, and lastly e-mail me the changes when they changed. # Here, we are counting the files and saving the result into a variable.Recently I set out to find a way to get PowerShell to monitor NTFS and File permissions on a folder and file share. # Here, we are defining the variables for the folders and the thresholds for the folders. # - New-eventlog -logname Application -source CountFileMonitor Set-ExecutionPolicy Unrestricted # to create the "CountFileMonitor" event source. You have to execute the below commands one time over an elevated powershell window # The following commands needs to be executed on the servers where you want to count the # Description: A PowerShell Script to Count Files with SCOM Requirements A third Alert Generating Rule to generate an Alert once the threshold has been exceeded. A second Event Collection Rule to collect the Event Logs created by the Script.ģ. A Timed Command Rule to execute the Powershell Script.Ģ. To use this Script with SCOM three Rules are required :ġ. Of course it can be used as a standalone Script too. The PowerShell Script below is intended to count files with SCOM.
0 kommentar(er)
