Wsus client not reporting but updating
On the client run gpresult or to make sure that the details of the WSUS server exist.
If not then a couple possible causes include: To address this, you need to make sure that the group policy is successfully updated on each client and that the WSUS setting is properly configured.
If you suspect your issue may be related to issues with the Automatic Update or BITS services, here are few links that can be helpful in troubleshooting these types of issues: KB331716 – List of known issues for Background Intelligent Transfer Service (BITS) KB969632 – Background Intelligent Transfer Service (BITS) does not start in Windows XP, and you receive a message in the System log: “The Background Intelligent Transfer Service service terminated with service-specific error 2147500037 (0x80004005)” KB883614 – You receive a “Windows Update has encountered an error and cannot display the requested page” error message when you try to install an update KB959894 – Error message: “The necessary service “Automatic Updates” (WUAUSERV) is not started or Background Intelligent Transfer Service (BITS) is disabled.
Here’s a cool tip and a cool tool that was sent to me by Joe Tindale, one of the top Support Escalation Engineers in our WSUS group.
Each server was set up from scratch and Windows was installed manually on each of them (i.e.
So it has got to be something with the clients, right?Some clients have been affected by a known issue with Windows Server 2003 and IIS.In some cases this transient issue will prevent clients from checking in, because they receive incorrect responses from the server after a number of attempts.One of these servers is successfully downloading updates from our WSUS server and the other is not.Both servers are VMware ESXi VMs running Microsoft Windows Server 2008 R2 Standard x64 SP1.