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.
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 InstallState : Installed Alex smiled. The cmdlet’s simple output told a complete story—from absence to action, from unknown to known. In the world of system administration, sometimes the most powerful tool is the one that tells you exactly what you have, so you can decide what to do next. Get-WindowsFeature -Name UpdateServices is your precise, scriptable, and safe way to check if the WSUS server role is present on a Windows machine—saving you from manual GUI checks and enabling automated server management at scale. get-windowsfeature -name updateservices
Alex typed:
Invoke-Command -ComputerName Server02, Server03 -ScriptBlock Get-WindowsFeature -Name UpdateServices Alex’s predecessor had set up a Windows Server
Get-WindowsFeature -Name UpdateServices The command ran almost instantly. PowerShell returned a concise table:
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. In the world of system administration, sometimes the
“First thing’s first,” Alex muttered. “Is the feature even there?”
