Get-windowsfeature -name Updateservices -

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 : Available Two hours later, after running Install-WindowsFeature and a reboot: get-windowsfeature -name updateservices

Alex opened PowerShell as an administrator—no GUI, no clicking through Server Manager. Just a blinking cursor. The goal was simple: verify whether the core WSUS role, including its management console and database components, was installed on WSUS-01. Get-WindowsFeature -Name UpdateServices is your precise

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

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.

Alex typed:

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.