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" )
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.
foreach ($svc in $servicesToStop) if (Get-Service -Name $svc -ErrorAction SilentlyContinue) Stop-Service $svc -Force Set-Service $svc -StartupType Disabled Write-Host "Disabled: $svc" setup prod offscrub
if ((Get-WindowsFeature -Name AD-Domain-Services).Installed) Write-Error "This is a Domain Controller. OffScrub aborted." exit 1
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: You can start with the (part of the
When done correctly, OffScrub can significantly reduce memory and CPU overhead on VDI/RDSH hosts, sometimes improving user density by 15–25%. When done wrong, it can take down a production farm in minutes.
Get-Service | Where-Object $_.StartType -eq "Disabled" | Export-Clixml -Path "C:\OffScrubBackup\services_before.xml" Restore script: foreach ($svc in $servicesToStop) if (Get-Service -Name $svc
foreach ($taskPath in $tasksToDisable) Disable-ScheduledTask -Verbose
$tasksToDisable = @( "Microsoft\Windows\DiskDiagnostic*", "Microsoft\Windows\Power Efficiency Diagnostics*" )
$backup = Import-Clixml -Path "C:\OffScrubBackup\services_before.xml" foreach ($svc in $backup) Set-Service $svc.Name -StartupType $svc.StartType