This log Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.
Provides information about the deployment on the client, including software update activation, evaluation, and enforcement.
In this process, Client will create local GPO with WSUS Settings by leaving automatic updates .
If you do not disable automatic updates (Via GPO) leaving the door open for the WUA to do things on its own outside the control of Config Mgr including installing any updates approved directly in WSUS (including new versions of the agent itself which are automatically approved) and rebooting systems which have a pending reboot.
For some reason,if the client says non-compliant from your sccm reports,try to refresh compliance state using $SCCMUpdates Store = New-Object -Com Object Microsoft. From above log, Assignment has total CI = 6 ,means ,the assignment has total 6 patches particular assignment group and patch count .
If the count of patches are less than what it supposed to be,then you may have to refresh the machine policy ,initiate software update scan and wait for a while before client start downloading the policies.
Neither of these is desirable in a Config Mgr managed environment and thus the recommendation for disabling automatic updates.
As for the rest of the Windows Update GPO settings, they are meaningless in the context of Config Mgr so it doesn't really matter what you set those to if you disable automatic updates,more from If you choose to create a GPO for WUA, you must configure the Windows Update Server option to point to the active software update point server in the site or location.
It's important to configure these tools so that they don't have overlapping coverage of the same servers in any datacenter deployment, including using different Windows Server Update Services servers.Patch compliance success rate is depends mainly on heath of your SCCM clients and some times things may go wrong even though sccm client is healthy (able to receive applications/packages and performing inventory except patches).Coming to the subject line, I have been seeing many questions on the configuration manager forums and social networking sites on software update patching issues .couple of questions on the subject line are like In this blog post (SCCM 2012 Troubleshoot software update client issues), I will explain you the basic troubleshooting steps (only on client side ) which will help you to resolve issues on your own by analyzing the logs and take it further afterwards.I normally use the configuration manager support center to troubleshoot the client issues to check if the policy for the deployed software update group received correctly or not based on the Policy IVersion.1.Stop the windows update service,rename or delete the Software Distribution folder (%windir%\software Distribution) and start windows update service.
Limited distribution release (LDR) updates, also called hotfixes, are not published through Microsoft Update or Windows Update, so they cannot be downloaded by the Windows Update Agent (WUA) plug-in that CAU uses by default.