txt input file or from Active Directory), highlighting systems with less than a certain (variable defined) percentage of free space, then generating a HTML report and emailing it to designated recipients. The script reports on disk space consumption/free space for multiple servers (either from a. Look down in the comments of the post for some updates to the script. A quick Google led me to this post that includes the same functionality of my VB script in glorious new PowerShell.

I had an old VB script on file that worked, but I figured it was time to get up to date with PowerShell. Next up, I wanted to deliver a report to the customer that showed any machines that were still at risk of running out of free disk space. That did the trick to clean up all of the archived event logs. #-And they lived happily ever after, the end. # Where-Object | remove-item -recurse -force #for all computers in file servers.txt (export from ADUC) #Delete files older than X days or meeting Y name filter A quick PowerShell script did the trick for me – I put together a multi-purpose script that could delete files by age or by name filter (or both) against a collection of machines. Then, I had to do a quick cleanup of a bunch of archived event logs – tens of gigabytes of files on some some the busier servers (domain controllers, print servers, file servers) – that were filling local system (C:) drives up. For domain controllers, reference this TechNet article with recommendations for ‘Strengthening Domain Controller Policy Settings’. For the floating VMware View workstations I dialed down logging to reduce Linked Clone growth rate as the log are not preserved across refresh/recompose operations. I also set up Audit Policies for each of the computer account types. The fix was easy, but I thought I would share for others who might run into the same issue.įirst, I set a group policy to configure appropriately sized logs and retention policies on domain controllers (Default Domain Policy), Servers, and Workstations respectively. Hard drives – physical and virtual – began to fill up, taking down critical services. But, the setting to archive event logs on each server and workstation in the domain persisted.

The need for the policy abated, then the policy was removed. I ran into an environment today where a group policy object (GPO) was configured at the domain level that set security logs to be archived to the C: drive when full.

Windows server 12