Server 2016 not updating from wsus


The Configuration Manager team has published its own guidance for this scenario.

Note that WSUS still ignores all deferral policies that have been configured, and that any deferral policies you do configure will only affect offering and download of updates for Microsoft products.

Force the client to check for updates by issuing the wuauclt /detectnow command.

After a few moments the Windows XP machine should appear in the created computer group on the WSUS server.

Now that our WSUS server is working, we need to take care of the clients, and there are two ways: editing the registry, or configure the local group policies. To begin go to the Windows XP client and click Start Windows Update.

As you can see in the Windows Update folder we have a bunch of GPO for the Windows Update configuration.

Now, all you have to do is go to every client in your network and double-click this registry file to import the settings.

Go to any one of these two clients and open the registry editor using Start Run type regedit then hit OK.As mentioned in Demystifying "Dual Scan", configuring a combination of policies on Windows 10 1607 can result in those clients automatically [and unexpectedly] scanning against Windows Update, as well as subsequently ignoring deployment instructions from WSUS.We heard feedback from on-premises administrators that they needed the deferral policies only for ad hoc scans against Windows Update, a scenario which was not supported.While the new policy (dubbed "Disable Dual Scan") is enabled, any deferral policies configured for that client will apply only to ad hoc scans against Windows Update, which are triggered by clicking "Check online for updates from Microsoft Update": Windows updates from Configuration Manager, supplemental updates from WU - a modified "on-premises" scenario.Here the expectations are the same as with the previous scenario, except that Config Manager recently took a change to remove some underlying policies that make this scenario work differently than described above.Expand HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Update. Here you can see all the settings we configured previous using the local group policy editor.

You must have an account to comment. Please register or login here!