Client computer not updating wsus

Rated 4.72/5 based on 990 customer reviews

I do have them checking for updates every hour from my WSUS server though, and to expedite the process I run a Power Shell script to force it to check & install after the script I'm installing apps manually (we're still in POC/demo mode). Updates#Download updates.$Session = New-Object -Com Object Microsoft. I can confirm that it's going against the correct wsus server.Here's the script, which I didn't write, but don't have the link handy ATM. I've cloned my deployment task sequence with the only difference being that one is using the 1511 media and the other the 1607.If you google the issue, it appears that Windows 1607 doesn't play nice with WSUS.

client computer not updating wsus-26

The Synchronization Schedule for WSUS server has been kept at hrs.

Also adding KB3176929 made no difference (both of these are referenced by multiple threads)Get-Windows Update Log is of no help since I guess it needs some symbols to make the data readable. I understand that it should be doing that per configuration, but something is wrong and narrowing down the issue might be a helpful next step.

WSUS server has both of the Windows 10 related updates (including the one that required additional steps after installation). Windows 1511 updates no problem and you can even start the 1607 update from WSUS if I approve it for a computer. Download()#Install updates.$Installer = New-Object -Com Object Microsoft. I've heard there are settings which were in 1511 (?

To accomplish client self-update, WSUS Setup creates a virtual directory under the WSUS website named Selfupdate.

This virtual directory holds the WSUS-compatible Automatic Updates. Using Group Policy to point client computers to your WSUS server should eventually cause an Automatic Updates detection and client self-update.

Leave a Reply