Export (0) Print
Expand All

Best Practices Analyzer for Health Registration Authority

Published: December 15, 2009

Updated: March 29, 2012

Applies To: Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

In Windows management, best practices are guidelines that are considered the ideal way, under normal circumstances and as defined by experts, to configure a server. While best practice violations—even critical violations—do not necessarily lead to problems, they indicate server configurations that can result in poor performance, poor reliability, unexpected conflicts, increased security risks, or other potential issues.

Topics in this section can help you bring Health Registration Authority (HRA) running on Windows Server 2008 R2 into compliance with best practices. HRA is one of the roles services that are installed as part of the Network Policy and Access Service (NPAS) server role. Content in this section is most valuable to administrators who have completed a Best Practices Analyzer scan of NPAS and who want information about how to interpret and resolve scan results that identify areas of HRA that are not compliant with best practices.

For more information about Best Practices Analyzer and scans, see Best Practices Analyzer (http://go.microsoft.com/fwlink/?LinkId=122786).

HRA is a Network Access Protection (NAP) component that issues health certificates to clients that pass the health policy verification that Network Policy Server (NPS) performs using the client statement of health (SoH). HRA is used only with the NAP IPsec enforcement method. For more information, see Network Access Protection at http://go.microsoft.com/fwlink/?LinkID=169170.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft