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.
Do not run OffScrub on domain controllers or SQL servers without overrides.
foreach ($taskPath in $tasksToDisable) Get-ScheduledTask -TaskPath $taskPath setup prod offscrub
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" )
Write-Host "Starting Production OffScrub - $(Get-Date)" Why would you do this in production
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:
$backup = Import-Clixml -Path "C:\OffScrubBackup\services_before.xml" foreach ($svc in $backup) Set-Service $svc.Name -StartupType $svc.StartType Do not run OffScrub on domain controllers or
If you manage a Windows environment—especially one involving Remote Desktop Services (RDS), Citrix, or VMware Horizon—you’ve likely heard of OffScrub . It’s a powerful script from Microsoft’s SysInternals suite (specifically part of PSExec and the Windows Assessment Toolkit) used to selectively disable or stop non-essential background processes, services, and scheduled tasks.
| 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 .