Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows Server » Important Areas to Master on WSUS

Important Areas to Master on WSUS

Posted on 17/05/201806/12/2023 Christian By Christian No Comments on Important Areas to Master on WSUS
WSUS updates

Exploring the crucial “Areas to Master on WSUS” is essential. Formerly known as Software Update Services (SUS), WSUS, developed by Microsoft, empowers administrators to manage update distribution in a corporate computer network efficiently. Please see Windows Server Update Services: Windows 2016 Servers does not show up on WSUS console, and WSUS clients appear and disappear from the WSUS Update Services console.

For more articles I have written, see Configuring WSUS Email Notification to Work With Office365. How to setup and configure Windows server update services (WSUS), and Targeting WSUS Client with the Registry keys: How to configure WSUS Clients to get Updates from the WSUS server using Registry settings.

Understanding Update Applicability and Installation

Installed and not applicable

This means applicable updates. This means that the particular patch is for Windows Server 2012 as an example. Also, all of your systems that report to your WSUS server.

Looking for Areas to Master on WSUS? If your server is Windows Server 2012, patches might appear as installed/not applicable, as they're not meant for those systems.

Here is how to Start, Stop and Restart Windows Server Update Services (WSUS) via PowerShell and CMD.

Explanation: If you have four servers reporting to WSUS which are 2 windows 2012 and 2 windows 2008 servers, MS.Netframeork Update for server 2012. This will show up as 50 installed / not applicable. Each of those servers (meaning 50% of the total computers reporting to WSUS need this).

Install 1/4 WSUS

This meaning  a Groups configured for install (The (1/4) means you have approved it for one of your four targets groups.)

Exploring the WSUS Admin Console, we discover that under the “Approval” column, certain updates display as “Install (1/3)”. These are key Areas to Master on WSUS for effective update management.

Answer: The parenthetical numbers document how many groups are configured for Install (All computer groups/Unassigned group/ Test Server Group) etc.

In the first case, one of three groups has the update approved for install. In the second case, the update is approved for all computers and is inherited to all groups.

This can be seen from the update status which shows the computer installed and not applicable 

Please see How to apply Windows Updates from WSUS to the server using AWS RunCommand. How to Configure SSL between WSUS servers (Upstream and Downstream Servers), and Windows Server Update Services Commands, WAUACLT, PowerShell and USOClient

Installed / Not applicable 100%

This means the updates is not applicable to any client whatsoever.

I hope you found this blog post on Important Areas to Master on WSUS useful. Please feel free to leave a comment below.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server

Post navigation

Previous Post: Client Visibility Issues: Fix WSUS Clients appear then disappear in the console
Next Post: How to apply Windows Updates from WSUS to AWS Instances

Related Posts

  • powershell commands lede 1024x276 1
    PowerShell Remoting: Guide to Windows Management Instrumentation Scripts
  • wsus logo e1653651564255
    How to configure Windows server update services Windows Server
  • image 23
    Copy Deployment Share between Servers without using linked Deployment Shares Windows
  • sadx
    Error 0x80070002: When trying to mount an image file Windows Server
  • 33
    The wim file needs to be remounted: Fix error 0xc1510114 Windows Server
  • 10.0.17763.1 error
    Fix Windows 10 Setup 1809 build 10.0.17763.1 is not supported Error Windows Server

More Related Articles

powershell commands lede 1024x276 1 PowerShell Remoting: Guide to Windows Management Instrumentation Scripts
wsus logo e1653651564255 How to configure Windows server update services Windows Server
image 23 Copy Deployment Share between Servers without using linked Deployment Shares Windows
sadx Error 0x80070002: When trying to mount an image file Windows Server
33 The wim file needs to be remounted: Fix error 0xc1510114 Windows Server
10.0.17763.1 error Fix Windows 10 Setup 1809 build 10.0.17763.1 is not supported Error Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • Mendeley Cite with MSWord Issue resolved
    Mendeley Cite ECITE40001 Error: Fix issue using Microsoft Word Desktop application Mac
  • Hide or Show User Accounts from Login Screen on Windows 10 and 11
    How to Hide or Show User Accounts from Login Screen on Windows 10 and 11 Windows
  • FTP
    How to install and configure an FTP Server on Windows Server Windows Server
  • systemd services
    How to use Systemd Timers on Linux Linux
  • Ping request could not find the hos
    Ping request could not find the host: Verify if the name is entered correctly Windows
  • windows subsystem
    What is Windows Subsystem for Linux Windows Server
  • WMi tools   WMI Explorer
    Query and display Windows information via WMI Explorer Network | Monitoring
  • HiveNightmare
    Workaround for “SeriousSAM or HiveNightmare” registry vulnerability for Windows 10 and 11 Security | Vulnerability Scans and Assessment

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,811 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.