locked
DCM Compliance Report is showing wrong RRS feed

  • Question

  • Hi All,

    Through SCCM DCM we'are maintaing system drive space..everything is working fine.

    however while checking "Summary compliance for a configuration item by computer" report in SCCM, one machine system drive space is Non Compliance and warning..

    we've set DCM compliance level is if  system drive sapce is below 5% ,it should be non compliance. however even though we've enough space is in server it is showing non-compliance.

    logged into server, went to control panel->open configuration manager-went to confiugation tab-all are compliant..however i evaluate everything once again and if i click view report..evething if compliant and green..intiated the machine policy,hardware policy, datadiscovery policy..but still report showing that particular machine is non-compliance.

    give me suggestion on this issue...

    Monday, August 13, 2012 1:23 PM

Answers

  • Then... I give up.  I would open up a call with MS at this point, if it were me.

    About the only other thing I could think of to try would be to "retire" that baseline/Configitem.  Make up a completely brand new one; so that to ALL clients it is brand new; and deploy that one.  At least then you are starting fresh, and you know it.


    Standardize. Simplify. Automate.

    • Proposed as answer by Garth JonesMVP Friday, December 26, 2014 10:31 PM
    • Marked as answer by Garth JonesMVP Saturday, January 3, 2015 5:21 PM
    Thursday, August 16, 2012 4:52 PM

All replies

  • Read through this:  http://blogs.msdn.com/b/steverac/archive/2011/01/07/sccm-state-messaging-in-depth.aspx

    My guess, and it is ONLY a guess, is that at some point in time, for that specific machine, the state message that indicates compliant was lost or malformed or something--basically the machine's information was lost between it and the server.  Since subsequent local re-evaluations are "still" compliant, the machine will not re-send a delta when nothing has changed.  So... in that blog above is a small script you can run locally on that box to tell it to resend all state messages, just this once, just for this specific computer.

    RefreshServerComplianceState

    PS: another way to 'force' it would be to change the configuration item just enough so that it is a "new policy version".  The easiest is just to add something to the description of the CI.  i.e., you aren't changing the CI itself; just metadata/comments.  But that's enough to change the policy version.  After the clients pick up the new policy, ALL your clients will have to evaluate and report on this "new" changed CI.  But since you are talking about just 1 computer, the quick script in the blog above is usually easier on a case by case basis.


    Standardize. Simplify. Automate.


    Monday, August 13, 2012 1:31 PM
  • Hi,

    Thanks for the update..Yes..that would be also one of the reason..may be state messages lost regarding this compliance..let me tryout this..

    thank again.

    Monday, August 13, 2012 1:35 PM
  • No luck..

    above link it is done for software update compliance update..

    i'm not getting idea how i need to modify the script for my DCM compliance table update in central. please suggest

    Monday, August 13, 2012 2:27 PM
  • DCM uses the EXACT SAME stuff as Software Update Compliance.  Just run the script, please, on the computer that is misreporting. 

    A state message is a state message is a state message. 


    Standardize. Simplify. Automate.

    Monday, August 13, 2012 3:11 PM
  • thank you !!!!

    let me try the same..i will update once i completed.

    Monday, August 13, 2012 3:14 PM
  • I used the below script from http://blogs.msdn.com/b/steverac/archive/2011/01/07/sccm-state-messaging-in-depth.aspx and ran in secondary server which is showing wrong in DCM report.

    RefreshServerComplianceState()

    Sub RefreshServerComplianceState()
        dim newCCMUpdatesStore
        set newCCMUpdatesStore = CreateObject ("Microsoft.CCM.UpdatesStore")
        newCCMUpdatesStore.RefreshServerComplianceState
        wscript.echo "Ran RefreshServerComplianceState."
    End Sub

    no luck..

    still that particular server is showing drive space is non-compliant->warning. even through we've enough free space on server..

    any other ideas ..please...

    Thursday, August 16, 2012 11:28 AM
  • check inboxmon.log: are your state messages backlogged?

    Standardize. Simplify. Automate.

    Thursday, August 16, 2012 11:55 AM
  • i've checked backlogs. there is no backlogs and checked inboxmon.log no warnings,no errors..

    Thursday, August 16, 2012 2:00 PM
  • Then... I give up.  I would open up a call with MS at this point, if it were me.

    About the only other thing I could think of to try would be to "retire" that baseline/Configitem.  Make up a completely brand new one; so that to ALL clients it is brand new; and deploy that one.  At least then you are starting fresh, and you know it.


    Standardize. Simplify. Automate.

    • Proposed as answer by Garth JonesMVP Friday, December 26, 2014 10:31 PM
    • Marked as answer by Garth JonesMVP Saturday, January 3, 2015 5:21 PM
    Thursday, August 16, 2012 4:52 PM