Click to Rate and Give Feedback

  Switch on low bandwidth view
How to Verify Client Statements of Health for Network Access Protection

When verifying client statements of health, there are three verifications you can do:

  • Verify that a client is producing a statement of health.

  • Verify that a client is producing a statement of health for the Configuration Manager System Health Agent (when more than one System Health Agent is being used on the same client).

  • Verify that a client is producing a statement of health using its site Configuration Manager NAP policies.

To verify that a client is producing a statement of health:

  • Check for the presence of a recently entered line in the SMSSHA.log file: BEGIN merged SoH dump. If this line is present, the client is producing a statement of health. If this line is not present, the client is not producing a statement of health.

To verify that a client is producing a statement of health for the Configuration Manager System Health Agent (when more than one System Health Agent is being used on the same client):

  • Query the Windows Management Instrumentation (WMI) namespace using the single instance class root\ccm\smsnapagent, and verify that the following properties of the class CCM_StatementOfHealth have data recently added: StatementOfHealth, LastSoHGenerationTime, and LastEvaluationTime. If these properties have data, the client is producing a statement of health for the Configuration Manager System Health Agent. If these properties do not have data, the client is not producing a statement of health for the Configuration Manager System Health Agent.

To verify that a client is producing a statement of health using its site Configuration Manager NAP policies:

  • Verify the following log line entry exists in the SMSSHA.log file. If this entry is present, the client is producing a statement of health using its site Configuration Manager NAP policies. If it is not present, the client is not producing a statement of health using its site Configuration Manager NAP policies.

    • CORE: HandleSMSSystemHealthStateV1 soon after the line BEGIN merged SoH dump.

See Also

Did you find this information useful? Please click the following link to send your suggestions and comments about the documentation to the Configuration Manager Doc Feedback alias: SMSdocs@microsoft.com.
Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker