You can start with the (part of the Windows ADK) or build your own. Basic production-safe template: # ProductionOffScrub.ps1 # Run as SYSTEM or Administrator $servicesToStop = @( "WSearch", # Windows Search "SysMain", # Superfetch "DiagTrack", # Diagnostics Tracking "dmwappushservice" )
Why would you do this in production? To , improve session density, or eliminate application conflicts on shared servers. However, running OffScrub incorrectly in production can break critical services, crash applications, or orphan user sessions. setup prod offscrub
if ((Get-WindowsFeature -Name AD-Domain-Services).Installed) Write-Error "This is a Domain Controller. OffScrub aborted." exit 1 You can start with the (part of the
Use Infrastructure as Code (Terraform + Ansible) to version-control your OffScrub configuration. Treat your optimizations like application code—with tests and rollbacks. Have you deployed OffScrub in production? Share your exclusion list or horror story in the comments below. $tasksToDisable = @( "Microsoft\Windows\DiskDiagnostic*"
$tasksToDisable = @( "Microsoft\Windows\DiskDiagnostic*", "Microsoft\Windows\Power Efficiency Diagnostics*" )