OK, here's the main difference: In addition to OS patches, Microsoft Update takes care of your MS Applications like Office, SQL Server and Exchange. WSUS has a good monitoring and reporting feature that allows me to see at a glance which machines are struggling with the stuff Microsoft is trying to send to it.
So I do a Remote Desktop session to the machine in question and run the process manually. I used to spend hours looking up ways to get around these errors. This process of switching from the newer method to the older one and then back again seems to fix a host of registry errors and other wastes of time.
That's the command to use, but it won't force a download, it just makes the client check in with WSUS and ensure it's interfacing with it.
The downloads happen based on the clients' Windows Update settings.
If this is the case, then all is working, and you just need to hit "Check for Updates" on the client.
One of most important and critically used feature in configuration manager 2012 is Software updates .
It is always challenging and import task for any sccm administrator to achieve good patch compliance success rate within the given SLA(Service level agreement).
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.
As always before performing anything; check, double check, test and always ensure you have a backup.