Enforcement Client Is Not Initialized
Updated: March 29, 2012
Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
This problem can occur when the NAP client computer is running Windows Vista® with no service packs installed. Although an enforcement client is initialized, it might not be displayed as initialized when you run the netsh nap client show state command. This is a known issue with computers running Windows Vista that do not have Service Pack 1 (SP1) installed.
If an enforcement client is not initialized, a NAP client computer will not report its health status to NAP server components. NAP client events 28 and 29 will also not occur. If you observe these events, then the enforcement client has been initialized successfully.
- NAP client event ID 28: A Statement of Health with correlation ID %1 was sent to the enforcement client %2.
- NAP client event ID 29: A Statement of Health Response with correlation ID %1 was received from the enforcement client %2. The current client state is %3. The following SHAs report this client non-compliant: %4 The following error categories were encountered: %5 The probation expiration time is: %6 The help URL is: %7 The duration of health check was %8 ms.
This problem is resolved when you install SP1 on a computer running Windows Vista.