Wednesday, October 21, 2015

SCCM Client Health State

Every SCCM Admin would have been asked this question, "Can you tell me which Client is not communicating back to the primary site server?"
All of us admin would know that a SCCM client is of no use if it does not communicate correctly back to the primary site server.
If it does not communicate, it will be be able to retrieve any machine policy.
If it does not communicate, it will be be able to send back the inventory information back to the Primary Site Server.
And of course the list goes on....

Using the query below, you will be able to do just that.
With the information that is made available, you will then be able to troubleshoot the client that are not working as expected.

SELECT [SMSID]
      ,[FQDN]
      ,[NetBiosName]
      ,[AssignedSiteCode]
      ,[HealthType]
      ,[HealthState]
      ,[HealthStateName]
      ,[ErrorCode]
      ,[ExtendedErrorCode]
      ,[LastHealthReportDate]
      ,substring(OU.System_OU_Name0,15,3) [Site]

  FROM [CM_C00].[dbo].[v_ClientHealthState] CHS
  left join v_R_System VRS on  VRS.Name0 = CHS.NetBiosName
  left join v_RA_System_SystemOUName OU on ou.ResourceID = VRS.ResourceID

order by HealthState desc


No comments:

Post a Comment