Setup Prod Offscrub 〈Easy × Handbook〉

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.

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" )

Get-Service | Where-Object $_.StartType -eq "Disabled" | Export-Clixml -Path "C:\OffScrubBackup\services_before.xml" Restore script: setup prod offscrub

foreach ($svc in $servicesToStop) if (Get-Service -Name $svc -ErrorAction SilentlyContinue) Stop-Service $svc -Force Set-Service $svc -StartupType Disabled Write-Host "Disabled: $svc"

| Service Name | Required? | OffScrub Action | |--------------|-----------|------------------| | Spooler | Yes (printing) | Keep | | WSearch | No (search indexing) | Disable | | SysMain | No (Superfetch) | Disable | | Themes | Yes (UI stability) | Keep | The most common production-ready implementation is a PowerShell script that wraps Set-Service , Stop-Process , and Disable-ScheduledTask . Use Infrastructure as Code (Terraform + Ansible) to

Write-Host "OffScrub completed - $(Get-Date)" In production, you need rollback capability and exclusion logic . A. Create an undo script Before disabling anything, export current state:

Write-Host "Starting Production OffScrub - $(Get-Date)" Share your exclusion list or horror story in

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.