How to troubleshoot Windows Server Update Services (WSUS)

In an try to make work simpler for pc directors, Microsoft developed a program known as to help directors with managing updates and hotfixes that the corporate releases for its merchandise. The WSUS is a vital a part of a Windows server. As and when Microsoft launches the updates on its web site, WSUS downloads it and distributes it throughout the community.

Windows Server Update Services Troubleshooting

how to troubleshoot windows server update services wsus - How to troubleshoot Windows Server Update Services (WSUS)

Prerequisites

1] Users utilizing WSUS three.zero SP2 on Windows Server 2008 R2 want to have replace KB4039929 or a later model put in on the system.

2] For these utilizing WSUS on Windows Server 2012 or a later model, the next updates or a later model want to be put in on the system:

  • Windows Server 2012 – KB 4039873
  • Windows Server 2012 R2 – KB 4039871
  • Windows Server 2016 – KB 4039396.

Troubleshooting connection failures with WSUS

Verify the next causes for troubleshooting connection failures with WSUS:

1] The WWW Publishing Service and Update Service needs to be operating on the WSUS server.

2] The WSUS web site or the default web site needs to be operating on the WSUS server.

three] Check the log on the location C:windowssystem32logfileshttperr for errors (the place C: is the system drive).

Troubleshooting High CPU utilization on WSUS server

Press CTRL+ALT+DEL and open the duty supervisor from the choices. It would present the CPU utilization. If the CPU utilization is excessive on the WSUS server, it is going to trigger the system to decelerate.

Causes of High CPU utilization on WSUS server

The causes for the excessive CPU utilization might be:

1] SUSDB is just not “clear.” This may confuse the shopper methods, and they’d begin scanning constantly in a loop.

2] Too many pending updates for the WSUS server to ahead to the shoppers. It often occurs after extended use.

In each these occasions, we want to clear up the WSUS server as the answer. Ideally, it has to be cleaned up after common intervals no matter whether or not we face the difficulty or not. The step-by-step process to do the identical is as follows:

1] Back up the WSUS database

It is perceived that backing up the WSUS database can enhance the efficiency of the server. It’s a prerequisite earlier than operating the clean-up wizard.

2] Run the WSUS Server Cleanup Wizard

The course of to use the server cleanup wizard is defined here on Microsoft.com. However, is the shopper methods are already scanning the information.it is going to add to the load. Should that be the case, we might re-index the WSUS database and decline outdated updates as defined within the following steps:

three] Re-index the WSUS database

Reindexing the WSUS database may help our trigger particularly if the database is fragmented.

You want to run the next instructions.

First, use the FULLSCAN choice to replace the statistics:

Use <dbname>
Go
Exec sp_msforeachtable 'replace statistics ? with fullscan'
Go

Then the indexes might be rebuilt:

Use <dbname>
Go
Exec sp_msforeachtable 'DBCC DBREINDEX (''?'')'
Go

four] Decline outdated updates

Since within the case talked about above, the shopper methods are scanning the WSUS database, and it has prompted excessive CPU utilization, the speedy treatment needs to be declining outdated updates because it helps cut back the load on the system.

1] Change the port for the WSUS web site: Select WSUS Administration Web Site > Edit Bindings and the edit the WSUS console to join to the brand new port. Run the script and synchronize with USS.

2] Decline the updates: You can use the Powershell script through the use of -skipdecline parameters to decide the online variety of declined updates. Then run the identical -skipdecline once more to decline these updates.

For additional particulars, it’s possible you’ll go to Microsoft Support here.

Leave a Comment