<div>
1) You should approve those updates your computers need. &nbsp;The yellow flag indicates a needed, but not installed update.<br />
<br />
2) This is such a terrible ratio, I don't bother with it unless I suspect there's a problem.<br />
<br />
3) In the tree on the left is a branch called &quot;Computers&quot;. &nbsp;Drilling down into that will tell you which computers are subject to WSUS, and what their individual status' are.
</div>


Network Administrator

DP230

<div>
<blockquote>
Percentage of Installed/Not applicable: it is better to have it small or high?
</blockquote>
<br />
if the update is not needed or not applicable by any machines, it would show 100%<br />
if you had a lot of those, then you would need to run the cleanup wizard as you might have updates that are no longer needed but taking up disk space<br />
<br />

<blockquote>
How can I check the update results of all PCs on WSUS server?
</blockquote>
<br />
if you click on computers on the left, it will break it down by group as to how many need updates, how many failed, etc.<br />
clicking on updates on the left also shows pretty pie charts showing how many updates are needed by clients
</div>


<div>
The view options you've chosen will always show you large numbers of updates that have been downloaded to your WSUS server but aren't needed by any of your workstations or servers. &nbsp;What you're not seeing in this view is whether any of those updates are actually needed by the machines on your network. &nbsp;You need to qualify your view here first. &nbsp;I suggest that you use &quot;Any except declined&quot; in the Approval box and &quot;Failed or Needed&quot; in the Status box. &nbsp;Also, I normally show the &quot;Failed&quot; and &quot;Needed&quot; columns instead of &quot;Installed/Not applicable.&quot; This will give you a much better &quot;macro&quot; picture of which updates are pending for the machines on your network.<br />
<br />
Then you can move to the Computers list as others mentioned above and look at individual groups of machines or even individual workstations or servers, and see what updates they need in particular.
</div>


<div>
Hi, okay can you suggest the methodology of using WSUS? I mean step by step, this is the first time I use this server.<br />
<br />
Currently I just approve all updates.<br />
<br />
<b>Should it be like this?</b><br />
1. Synchronize updates from WSUS to Microsoft<br />
2. Check update and classify the updates, order from the most updates which are needed by PCs<br />
3. Approve the updates from step 2<br />
4. Cleanup / Reset updates from WSUS<br />
5. How to check results on WSUS without going to individual PC?<br />
<br />
Do you think update Drivers is really necessary?
</div>


<div>
&quot;Should it be like this?&quot;<br />
Pretty much. &nbsp;I intentionally drag my feet on most updates that aren't security updates because Microsoft sometimes releases bad code and I don't want to be the one to find it. &nbsp;I also only bother with &quot;cleaning up&quot; updates a couple times a year. &nbsp;And again, you can check the status of a PC by looking at the &quot;Computers&quot; branch of the left-hand tree. &nbsp;<br />
<br />
I generally don't use WSUS to update my drivers, but I'm in a small organization and might change my mind if I had hundreds or thousands of computers to manage.
</div>


<div>
<div class="content wysiwyg-content">
Hi Experts, I got these question regarding WSUS management<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2019/12_w51/1439139/Capture.JPG" target="_blank" title="Capture.JPG (118 KB)"><img alt="Capture.JPG" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2019/12_w51/800_1439139/Capture.JPG" /></a><br />
For 1 - yellow warnings at the left: I noticed that some updates have them and some do not have. Should I approve the updates which do not have yellow warnings? Most of them said about the not applicable PCs<br />
<br />
For 2 - Percentage of Installed/Not applicable: it is better to have it small or high? And can you suggest for better operation of WSUS?<br />
<br />
And 3 - How can I check the update results of all PCs on WSUS server?<br />
<br />
Many thanks!
</div>
</div>


Capture.JPG

Hi Experts, I got these question regarding WSUS management



For 1 - yellow warnings at the left: I noticed that some updates have them and some do not have. Should I approve the updates which do not have yellow warnings? Most of them said about the not applicable PCs

For 2 - Percentage of Installed/Not applicable: it is better to have it small or high? And can you suggest for better operation of WSUS?

And 3 - How can I check the update results of all PCs on WSUS server?

Many thanks!

Questions about WSUS server (p2)

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Windows Server Update Services (WSUS), previously known as Software Update Services (SUS), is a computer program developed by Microsoft that enables administrators to manage the distribution of updates and hotfixes released for Microsoft products to computers.

WSUS

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.