Wsus server not updating client status
After you set up a client computer, it may take a few minutes before it appears on the Computers page in the WSUS console (this console is available to admins running their own WSUS server, but not for admins who point their clients at the CITES WSUS server).
For client computers configured with an Active Directory-based GPO, it can take about 20 minutes after Group Policy refreshes (that is, applies any new settings to the client computer).
In part 4, I will be covering Enforcement status of Update Deployments (which is much different than compliance).
In part 3, I will be covering Viewing Update Compliance in the SCCM Console, what it means, and what it doesn’t mean, and what it really means to tell you if only you listen.
A packet trace will confirm that traffic is being sent to the proxy rather than the local WSUS server.
The reason this happens is twofold: Since the Group Policy setting that directs clients to a WSUS server typically uses the server's FQDN, manually checking for updates causes traffic to be sent to the proxy server instead of directly to the WSUS server, and error 0x80244021 results.
Microsoft goes on to explain why this update is critical…
Windows 10 feature updates (denoted by the “Upgrades” classification in WSUS) are staged in encrypted packages to Windows Update several days prior to the actual go-live date.