locked
SCCM 2007 Software Updates - A. Compliance Report not working RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've noticed an interesting problem when we started doing server patches this month.

    While trying to report status to the group I noticed that the “Software Updates - A. Compliance” - “Compliance 1 - Overall Compliance” report wasn’t updating.  I can look at the deployment state and see that the servers are running the deployments and then eventually stating compliant.  However, when trying to provide compliance rollup using the Compliance reports they aren’t showing compliant for the update list.  I’ve considered that it may need some time to sync the report but I’ve given it 4 days.

    Any thoughts?… Anyone?

    Tuesday, August 30, 2011 3:20 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have seen the same issue several times, for some reason some of the clients are not sending the correct state messages back to the server. I ususally create a pacakge with the below script, and run it daily on clients and servers. It forces the state messages to be send to the MP.

    Option Explicit
    On Error Resume Next

    Call RefreshServerComplianceState

    ' WScript.Echo "Finished"

    Sub RefreshServerComplianceState()

        ' Initialize the UpdatesStore variable.
        dim newCCMUpdatesStore
       
        ' Create the COM object.
        set newCCMUpdatesStore = CreateObject ("Microsoft.CCM.UpdatesStore")

        ' Refresh the server compliance state by running the RefreshServerComplianceState method.
        newCCMUpdatesStore.RefreshServerComplianceState
       
        ' Output success message.
    '    wscript.echo "Ran RefreshServerComplianceState."

    End Sub

    Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
    • Proposed as answer by Anoop C NairMVP Tuesday, August 30, 2011 5:37 AM
    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 4:54 AM
    Tuesday, August 30, 2011 5:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Also, you can check the client side process of software update from  below blog.

    Make sure you have monitoring the statemessage.log for more details ...

    http://blogs.technet.com/b/sus/archive/2010/11/04/information-on-the-configmgr-2007-client-side-process-for-software-updates.aspx

    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 4:54 AM
    Tuesday, August 30, 2011 5:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Please also see Software Updates Compliance Status Summary not matching Reporting

     

    Regards,

     

    Sabrina

    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 4:54 AM
    Wednesday, August 31, 2011 9:55 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have seen the same issue several times, for some reason some of the clients are not sending the correct state messages back to the server. I ususally create a pacakge with the below script, and run it daily on clients and servers. It forces the state messages to be send to the MP.

    Option Explicit
    On Error Resume Next

    Call RefreshServerComplianceState

    ' WScript.Echo "Finished"

    Sub RefreshServerComplianceState()

        ' Initialize the UpdatesStore variable.
        dim newCCMUpdatesStore
       
        ' Create the COM object.
        set newCCMUpdatesStore = CreateObject ("Microsoft.CCM.UpdatesStore")

        ' Refresh the server compliance state by running the RefreshServerComplianceState method.
        newCCMUpdatesStore.RefreshServerComplianceState
       
        ' Output success message.
    '    wscript.echo "Ran RefreshServerComplianceState."

    End Sub

    Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
    • Proposed as answer by Anoop C NairMVP Tuesday, August 30, 2011 5:37 AM
    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 4:54 AM
    Tuesday, August 30, 2011 5:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Also, you can check the client side process of software update from  below blog.

    Make sure you have monitoring the statemessage.log for more details ...

    http://blogs.technet.com/b/sus/archive/2010/11/04/information-on-the-configmgr-2007-client-side-process-for-software-updates.aspx

    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 4:54 AM
    Tuesday, August 30, 2011 5:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Please also see Software Updates Compliance Status Summary not matching Reporting

     

    Regards,

     

    Sabrina

    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 4:54 AM
    Wednesday, August 31, 2011 9:55 AM