Get-windowsfeature -name Updateservices 🎁 💫

Get-WindowsFeature -Name UpdateServices The command ran almost instantly. PowerShell returned a concise table:

Display Name Name Install State ------------ ---- ------------- [ ] Windows Server Update Services UpdateServices Available The [ ] bracket was empty. The said “Available,” not “Installed.” Alex’s suspicion was confirmed: the WSUS role was not installed on the server named WSUS-01. No wonder patches weren’t deploying—the service wasn’t even there. get-windowsfeature -name updateservices

Alex’s predecessor had set up a Windows Server Update Services (WSUS) server years ago, naming it “WSUS-01.” But documentation was sparse, and the server had become a digital attic—crammed with old updates, syncing erratically, and suspected of not even being fully installed. Three critical security patches had been released over

Get-WindowsFeature -Name UpdateServices InstallState : Available Two hours later, after running Install-WindowsFeature and a reboot: a systems administrator

In the dimly lit server room of a mid-sized enterprise, Alex, a systems administrator, faced a familiar Monday morning dread. Three critical security patches had been released over the weekend, and the company’s 200 Windows servers were still unprotected. The problem wasn’t the patches themselves—it was control.

Invoke-Command -ComputerName Server02, Server03 -ScriptBlock Get-WindowsFeature -Name UpdateServices