For case one, make sure you are running the report against the same SUG that the deployment uses. This report will show different results if the SUGs are different. The downfall of enforcement state reports is that it will tell you a server is compliant, but only against what you've advertised to it, not against what it needs. so either include everything from MS in a deployment or be cognizant of which updates you're "compliant" against.
For case two, in SCCM 2012 clients will report "Downloaded Updates" instead of "waiting for maintenance window" like in 2007. Check to make sure it's not actually waiting for a maintenance window. There may be nothing wrong with it. I also find that sometimes repairing the client doesn't do what's needed to clear up status reporting. I usually completely uninstall first, then reinstall, and sometimes I stop BITS and the Windows Update services rename c:\windows\softaredistribution to .old and restart the services. C:\windows\windowsupdate.log will let you know what's going on too to some degree. Todd From: [email protected] [mailto:[email protected]] On Behalf Of Corkill, Daniel Sent: Sunday, January 4, 2015 10:46 PM To: [email protected] Subject: [mssms] Inconsistent software updates reports Why not start my first day back from the break with some patching fun. Firstly, I have a server that when viewed using the 'states 1 - enforcement states for a deployment' report shows as compliant, but when I view the 'compliance 3 - update group (per update)' report it's listed as required for an update (the latest Flash Player update which we SCUP). I have confirmed the update is installed on the server and there's no updates available in software center. I've performed a software updates deployment eval scan and confirmed in the statemessage.log that the messages are successfully being forwarded to the MP. This morning I performed a repair of the client and the reports are still inconsistent. Secondly, another server is reporting a 'downloaded updates' last state in the 'states 1 - enforcement states for a deployment' report despite all applicable updates being installed. I performed a repair of the client on this server too but it's not being reported as complaint. Does anyone have any thoughts or suggestions? Always appreciative. Daniel. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law.
