none
SQL query collection to fetch corrupt WMI in client machines in SCCM

    Question

  • I need to find out how many machines have WMI in client machines corrupted. Is there any collection - is there any SQL query to find out. If yes, whats it. How do we rectify the corrupt WMI in those machine then? 
    Monday, August 29, 2011 3:39 PM

Answers

  • I think, it's better to use some client health tools to check whether the client is fully functional or not.

    http://configmgrclienthtc.codeplex.com/

     


    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.

    • Proposed as answer by Sabrina Shen Wednesday, August 31, 2011 8:58 AM
    • Marked as answer by Sabrina Shen Friday, September 02, 2011 8:46 AM
    Monday, August 29, 2011 3:49 PM
  • Chicken and the egg here. The ConfigMgr client agent heavily relies on WMI so if WMI is broken or corrupt, the ConfigMgr agent isn't healthy either and can't report anything back to the site.

    You'll need to use something else to ensure client helaht like one of the startup scripts available, ConfigMgr Client Status Reporting tool (available in R2 nd R3) or Client Health from Adaptiva.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    • Proposed as answer by Sabrina Shen Wednesday, August 31, 2011 8:58 AM
    • Marked as answer by Sabrina Shen Friday, September 02, 2011 8:46 AM
    Monday, August 29, 2011 5:03 PM

All replies

  • I think, it's better to use some client health tools to check whether the client is fully functional or not.

    http://configmgrclienthtc.codeplex.com/

     


    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.

    • Proposed as answer by Sabrina Shen Wednesday, August 31, 2011 8:58 AM
    • Marked as answer by Sabrina Shen Friday, September 02, 2011 8:46 AM
    Monday, August 29, 2011 3:49 PM
  • Chicken and the egg here. The ConfigMgr client agent heavily relies on WMI so if WMI is broken or corrupt, the ConfigMgr agent isn't healthy either and can't report anything back to the site.

    You'll need to use something else to ensure client helaht like one of the startup scripts available, ConfigMgr Client Status Reporting tool (available in R2 nd R3) or Client Health from Adaptiva.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    • Proposed as answer by Sabrina Shen Wednesday, August 31, 2011 8:58 AM
    • Marked as answer by Sabrina Shen Friday, September 02, 2011 8:46 AM
    Monday, August 29, 2011 5:03 PM