Fixing NAP Client Settings Problems
Updated: March 29, 2012
Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
This section describes and provides solutions for problems that you might experience when deploying Network Access Protection (NAP) client settings to computers on your network.
NAP client settings can be deployed by using the local NAP Client Configuration console, the Netsh command-line tool, or Group Policy. These include enforcement client settings, user interface settings, trusted server group settings, and cryptographic policy settings.
The following additional settings cannot be configured using the NAP Client Configuration console or the Netsh command-line tool:
- Status of the NAP Agent service.
- Status of SHA-dependent services, such as Windows Security Center and Windows Update.
- Status of services used for network authentication, such as Wired Autoconfig, Wireless Zero Configuration, and WLAN Autoconfig.
- Local and remote network connections.
The following is a list of known problems and solutions associated with client settings in a NAP deployment. Problems and solutions that might be inter-related are noted and linked if needed. Problems that have more than one possible root cause are noted and have more than one proposed solution. Choose the problem that best describes your situation, and then complete the procedures for the suggested fix. This list will be continuously updated as new problems and solutions are found.
Enforcement Client Is Not Enabled
Enforcement Client Is Not Initialized
Trusted Server Groups Are Not Found
Wireless EAP Enforcement Client Is Not Enabled