Thursday, May 15, 2014

SCCM Client Health

This looked very helpful.

I am currently working on trying to come up with a process and methodology for SCCM Client Health. It seems to start with a good Asset Management strategy which is not what SCCM 2007, at least, offers. CM12 should improve some Asset Management but Asset Management seems to be a big data solution for a problem of tracking information from multiple sources. First you need to include Financial data from the purchase of equipment, then you need to track heartbeats from the objects from multiple sources. We are trying to use LDAP/ Active Directory lastLogonTimestamp, McAfee Last Communication, and SCCM Heartbeats.

I'm just now starting to play with WMIDiag from Microsoft. I'm wondering if it would make sense to implement WMIDiag.vbs into a DCM to give a success, error, or warning.

    0 = SUCCESS

    1 = ERROR

    2 = WARNING

    3 = Command Line Parameter errors

    4 = User Declined (Clicked the Cancel button when getting a consent prompt)


Tracking resource usage of WMI

By default the core WMI service lives in the shared Network Services instance of scvhost.exe. This can make debugging or identifying resource issues a little challenging. As a general rule of thumb I run (and recommend to customers) that they keep WMI separated into its own instance of svchost.

On XP/Server 2003 this can be accomplished automatically via the following case sensitive command:

    RUNDLL32.EXE %Systemroot%\SYSTEM32\WBEM\WMISVC.DLL,MoveToAlone

For Vista and up this is done with

         winmgmt /standalonehost

WMI Troubleshooting Tips - System Center Configuration Manager Team Blog - Site Home - TechNet Blogs:

No comments:

Post a Comment