WSUS not synchronizing with Microsoft Update
|
If you are having problems with the synchronization of updates, look at the some of the following rough patches for some assistance: Show ■ Check proxy server settings from the WSUS console. If your proxy server supports authentication, make sure you have the correct user name, password, and domain. Also be aware that by using basic authentication, you are sending your credential information in plaintext over the wire. ■ Verify the name of the upstream WSUS server. This must be spelled exactly. If you suspect other communication or name resolution problems, try pinging the upstream server from the downstream WSUS server that is having the problems. Just make sure when pinging that you are using the same naming convention used in the WSUS console. ■ Check the update storage options you have configured. If you are using a chain of WSUS servers together in a hierarchy, the entire hierarchy must use the same update storage option; otherwise, the synchronizations fail. Consequently, if the upstream server stores content locally, each of the downstream WSUS servers must store content locally as well. Make sure that each WSUS server in the chain uses the same option for update storage. ■ Verify permissions on the update storage directory. Check to see that the folder where you download update files has "Read" permissions for NETWORK SERVICE and for Authenticated Users, whether or not the server you download the update files to is an upstream or downstream machine. The directory is c:\Update Services\UScontent. (See Figure 11.1) Figure 11.1 Verifying Permissions  Make sure the upstream WSUS server actually has updates available. There are a couple of scenarios where there might be a mismatch in update availability. In the first scenario, an upstream server is reinstalled; thus, the list of classifications and updates that the administrator selects changes. A future synchronization will fail when a downstream server asks for updates that do not exist on the upstream server. In the second scenario, you might configure a downstream server to retrieve updates from a different upstream server with another set of products and classifications selected. Either of these scenarios would result in mismatched update numbers.There are a few ways to fix this: (1.) Specify the missing updates on the upstream server and then synchronize from the update source; (2.) make sure you cancel the updates that are not on the upstream server and decline the old updates on the downstream server; or (3.) if the missing updates are available on the upstream server, then the error is transient, and things will eventually fix themselves. Try restarting the Background Intelligent Transfer Service (BITS) service.You can do this from the Services Microsoft Management Console (MMC) under Administrative Tools in the Start menu (see Figure 11.2). Figure 11.2 Restarting BITS Figure 11.2 Restarting BITS ■ Try restarting the WSUS service. Again, this can be done from the Services MMC console under Administrative Tools in the Start menu. Try to synchronize again. ■ Make sure your environment supports Hypertext Transfer Protocol (HTTP) v1.1. If you are receiving errors regarding the Range protocol being unsupported, you must change a setting from the command line. Stop the WSUS service and issue the following command: "%programfiles%\Update Services\tools\osql\osql.exe" -S SQL_InstanceName -E -b -n -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1". Replace the SQL_instanceName as appropriate. Then, restart the WSUS service and perform the synchronization again. Some Independent Advice_ We have found that a lot of WSUS problems are solved by the timeless Windows fix: reboot. If you do not want to take down the whole machine, just restart the BITS service and the WSUS service and try again. Continue reading here: Console Access Issues Was this article helpful? Starting from 23 July 2022 WSUS synchronization started failing with error: "A dependency of the update was not found on the server and was not provided by the upstream server.". WSUS does not have upstream server, it syncs from Microsoft. When I open synchronization report - there are IDs of updates, that that fail with this error. The first ID is 3435b461-7ec5-4ee6-af82-4682636e12cb : Revision 100 When I try Get-WsusUpdate -UpdateId 3435b461-7ec5-4ee6-af82-4682636e12cb I get error: The specified item could not be found in the database. Searching in Google or www.catalog.update.microsoft.com by UpdateID also give no results. How to resolve this synchronization error? How can I get information about this Update? Tried updating WSUS server itself - the error persist. Tried running WSUS cleanup wizard. While running cleanup wizard WSUS console crashed. After WSUS console crashed I waited about 1 hour thinking that cleanup wizard still running in background. After 1 hour I rebooted WSUS and run synchronization, but the error persist. How do I sync WSUS with Microsoft Update?Synchronize the WSUS server with Microsoft Update. Log in to SolarWinds Patch Manager as an administrator.. In the Patch Manager menu, expand Enterprise > Update Services.. Right-click the WSUS server and select Synchronize Server. ... . In the Task Options wizard, click Browse computers.. How do I force a client to update WSUS?Hi, Click Start -> Run. Then type wuauclt /detectnow. To refresh the client report on wsus use the parameter /reportnow.
How do I push WSUS updates immediately?To approve and deploy WSUS updates. On the WSUS Administration Console, click Updates. ... . In the All Updates section, click Updates needed by computers.. In the list of updates, select the updates that you want to approve for installation in your test computer group. ... . Right-click the selection, and then click Approve.. How do I force Windows 10 to update from WSUS?In the WSUS Administration Console, go to Update Services\Server_Name\Updates\All Windows 10 Upgrades. Right-click the feature update you want to deploy, and then click Approve.
|
