Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Windows Server 2008 Network Policy Server (NPS) recognizes all computers as domain controllers in the NAP reporting data


View products that this article applies to.

Symptoms

Consider the following scenario:
  • The "Network Policy and Access Services" role is enabled on a Windows Server 2008-based computer.
  • The Network Access Protection (NAP) reporting data is configured to be logged in an SQL-compatible format.
In this scenario, Windows Server 2008 Network Policy Server (NPS) cannot differentiate between clients, servers, and domain controllers. Instead, all computers are recognized as domain controllers in the NAP reporting data.

For example, the following event ID 6278 identifies a Windows Vista-based client as "6.0.6001 1.0 x64 Domain Controller":

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Event ID:      6278
Task Category: Network Policy Server
Level:         Information
Keywords:      Audit Success
Description:
Network Policy Server granted full access to a user because the host met the defined health policy.

User:
	Security ID:			NULL SID
	Account Name:			-
	Account Domain:			-
	Fully Qualified Account Name:	-

Client Machine:
	Security ID:			<ID>
	Account Name:			<Name>
	Fully Qualified Account Name:	<Name>
	OS-Version:			6.0.6001 1.0 x64 Domain Controller   
	Called Station Identifier:		-
	Calling Station Identifier:		-

↑ Back to the top


Cause

This problem occurs because NAP reporting incorrectly recognizes all computers as domain controllers.

↑ Back to the top


Resolution

To resolve this problem, install hotfix KB956463 on all Windows Server 2008-based computers that have NAP enabled.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2008 installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008 note

The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are important for maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Crashdmp.sys6.0.6001.2233235,29617-Dec-200804:38x86
Ntkrnlpa.exe6.0.6001.223323,600,35217-Dec-200804:40Not Applicable
Ntoskrnl.exe6.0.6001.223323,548,64017-Dec-200804:40Not Applicable

For all supported x64-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Crashdmp.sys6.0.6001.2233239,39217-Dec-200805:50x64
Ntoskrnl.exe6.0.6001.223324,692,44817-Dec-200806:09x64

For all supported Itanium-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Crashdmp.sys6.0.6001.2233273,69617-Dec-200804:44IA-64
Ntoskrnl.exe6.0.6001.223329,492,96017-Dec-200804:45IA-64

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about NAP reporting, visit the following Microsoft Web site:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684� Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Vista and Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Package_for_kb956463_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36714-Aug-200818:15Not Applicable
Package_for_kb956463_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43014-Aug-200818:15Not Applicable
Package_for_kb956463_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42514-Aug-200818:15Not Applicable
Package_for_kb956463_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43114-Aug-200818:15Not Applicable
X86_microsoft-windows-n..ion_service_runtime_31bf3856ad364e35_6.0.6001.22243_none_f9623a835bc19bd2.manifestNot Applicable206,93014-Aug-200803:57Not Applicable
X86_microsoft-windows-n..tion_service_iassam_31bf3856ad364e35_6.0.6001.22243_none_7c10c3716cf59c40.manifestNot Applicable9,79014-Aug-200804:02Not Applicable
X86_microsoft-windows-n.._service_runtimeapi_31bf3856ad364e35_6.0.6001.22243_none_8bf65f1e7a170890.manifestNot Applicable14,33714-Aug-200803:57Not Applicable

Additional files for all supported x64-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-n..ion_service_runtime_31bf3856ad364e35_6.0.6001.22243_none_5580d607141f0d08.manifestNot Applicable206,96814-Aug-200805:17Not Applicable
Amd64_microsoft-windows-n..tion_service_iassam_31bf3856ad364e35_6.0.6001.22243_none_d82f5ef525530d76.manifestNot Applicable9,83614-Aug-200805:21Not Applicable
Amd64_microsoft-windows-n.._service_runtimeapi_31bf3856ad364e35_6.0.6001.22243_none_e814faa2327479c6.manifestNot Applicable14,36714-Aug-200805:17Not Applicable
Package_for_kb956463_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37514-Aug-200818:15Not Applicable
Package_for_kb956463_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43814-Aug-200818:15Not Applicable
Package_for_kb956463_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43314-Aug-200818:15Not Applicable
Package_for_kb956463_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43914-Aug-200818:15Not Applicable

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseadvanced, kbfix, kbsurveynew, kbqfe, kbhotfixserver, KB956463

↑ Back to the top

Article Info
Article ID : 956463
Revision : 1
Created on : 1/13/2009
Published on : 1/13/2009
Exists online : False
Views : 385