7 Appendix B: Product Behavior
The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.
The terms "earlier" and "later", when used with a product version, refer to either all preceding versions or all subsequent versions, respectively. The term "through" refers to the inclusive range of versions. Applicable Microsoft products are listed chronologically in this section.
The following table shows the relationships between Microsoft product versions or supplemental software and the roles they perform.
|
Windows Client Releases |
Server Role |
Client Role |
|---|---|---|
|
Windows XP operating system Service Pack 1 (SP1) |
No |
Yes |
|
Windows Vista operating system |
No |
Yes |
|
Windows 7 operating system |
No |
Yes |
|
Windows 8.1 operating system |
No |
Yes |
|
Windows 10 operating system |
No |
Yes |
|
Windows 11 operating system |
No |
Yes |
|
Windows Server Releases |
Server Role |
Client Role |
|---|---|---|
|
Windows Server 2003 operating system |
Yes |
Yes |
|
Windows Server 2008 operating system |
Yes |
Yes |
|
Windows Server 2008 R2 operating system |
Yes |
Yes |
|
Windows 8 operating system |
Yes |
Yes |
|
Windows Server 2012 operating system |
Yes |
Yes |
|
Windows Server 2012 R2 operating system |
No |
Yes |
|
Windows Server 2016 operating system |
Yes |
Yes |
|
Windows Server 2019 operating system |
Yes |
Yes |
|
Windows Server 2022 operating system |
Yes |
Yes |
|
Windows Server 2025 operating system |
Yes |
Yes |
Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.
<1> Section 1.6: For more information on networking in Windows Vista and Windows Server 2008, see [MSFT-NFLHWV].
<2> Section 2.2.1.1.1: If MajorVersion is 1, sub-BLOB is interpretable by the client-side plug-in.
If MajorVersion is 2, sub-BLOB is not interpretable by the client-side plug-in only on Windows XP SP1.
If MajorVersion is 3, sub-BLOB is not interpretable by the client-side plug-in on Windows XP SP1 and Windows XP operating system Service Pack 2 (SP2).
<3> Section 2.2.1.1.2: The client-side plug-in checks for changes at this interval in addition to the polling mechanism used by the Group Policy framework only on Windows XP SP1, Windows XP SP2, Windows XP operating system Service Pack 3 (SP3), and Windows Server 2003. Otherwise, the client side plug-in ignores this setting.
<4> Section 2.2.1.1.2: Except in Windows XP operating system (prior to Windows XP SP1) and Windows Server 2003, the client-side plug-in ignores this field.
<5> Section 2.2.1.2: The enbleSoftAP flag is not available in Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.
<6> Section 2.2.1.2: The enableExplicitCreds flag is not available in Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.
<7> Section 2.2.1.2: The blockPeriod flag is not available in Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. In the absence of this setting, the operating system can have a default block timeout period.
Most authentication failures (such as failures due to identity issues, UI display issues, or explicit EAP failures) are treated as long-term, and the block timeout period is 20 minutes. If authentication fails due to a lack of response from the IEEE 802.1X authenticator, the block timeout period is 1 minute. Some authentication failures (such as a timeout during an ongoing IEEE 802.1X exchange) result in no blocking period.
<8> Section 2.2.1.2: The enableWFD flag is not available in Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating system. In the absence of this setting, these applicable operating systems allow Wi-Fi Peer-to-Peer connections.
<9> Section 2.2.1.2.1: The administrative-side plug-in does not support creation/deletion/modification of XML-based wireless Group Policy on the following operating systems: Windows Server 2003, Windows Server 2003 operating system with Service Pack 1 (SP1), and Windows Server 2003 operating system with Service Pack 2 (SP2).
The client-side plug-in does not support XML-based Wireless Group Policy on the following operating systems: Windows XP SP1, Windows XP SP2, Windows XP SP3, Windows Server 2003, Windows Server 2003 with SP1, and Windows Server 2003 SP2.
<10> Section 2.2.1.2.1: MacRandomization is available in Windows 10 v1507 operating system and later.
<11> Section 2.2.1.2.1: TransitionMode is available in Windows Server 2022 and later.
<12> Section 2.2.1.2.1: QoSDSCPToUPMappingAllowed is available in Windows 11, version 24H2 operating system and later, and in Windows Server 2025 and later.
<13> Section 2.2.2: The blockPeriod flag is not available in Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. In the absence of this setting, these operating systems can have a default block timeout period.
Most authentication failures (such as failures due to identity issues, UI display issues, or explicit EAP failures) are treated as long-term, and the block timeout period is 20 minutes. If authentication fails due to a lack of response from the IEEE 802.1X authenticator, the block timeout period is 1 minute. Some authentication failures (such as a timeout during an ongoing IEEE 802.1X exchange) result in no blocking period.
<14> Section 2.2.2: The enableExplicitCreds flag is not available in Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.
<15> Section 2.2.2.1: The administrative-side plug-in supports creation/deletion/modification of XML-based wired Group Policy on the following operating systems: Windows Server 2008 and Windows Server 2008 R2.
The client-side plug-in does not support XML-based wired Group Policy on Windows XP and Windows Server 2003.
<16> Section 2.2.3.1.1: The applicable operating systems for the EapTlsDisablePromptValidation flag are Windows Vista, Windows Vista operating system with Service Pack 1 (SP1), and Windows Server 2008.
<17> Section 2.2.3.1.1: The client-side plug-in does not support regular expressions in serverName on Windows XP SP1.
<18> Section 2.2.3.1.2: The client-side plug-in supports a NumberOfEapTypes value of 0 in following operating systems: Windows XP SP2 and Windows Server 2003 SP2.
The client-side plug-in supports a NumberOfEapTypes value of 1 in the following operating systems: Windows XP SP3, Windows Vista, Windows Vista SP1, and Windows Server 2008.
<19> Section 2.2.3.1.2: The client-side plug-in only supports PeapInnerEAPOptional in the following operating systems: Windows XP SP2 and Windows Server 2003 SP2.
<20> Section 2.2.3.1.2: The client-side plug-in supports PeapEnforceCryptoBinding on the following operating systems: Windows Vista, Windows Vista SP1 and Windows Server 2008.
<21> Section 2.2.3.1.2: The client-side plug-in supports PeapEnableQuarantine on the following operating systems: Windows Vista, Windows Vista SP1, and Windows Server 2008.
<22> Section 2.2.3.1.2: The client-side plug-in does not support PeapEnableIdentityPrivacy on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.
<23> Section 2.2.3.1.2: The client-side plug-in does not support IdentityPrivacyString on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.
<24> Section 2.2.3.1.2.1: The client-side plug-in supports PeapTlsPhase1DisablePromptValidation on Windows XP SP1, Windows XP SP2, Windows XP SP3, Windows Server 2003 with SP1, Windows Vista and Windows Server 2008. Otherwise, it is ignored.
<25> Section 2.2.3.1.2.1: The client-side plug-in does not support regular expressions in Windows XP SP1.
<26> Section 2.2.3.2.1: The Config element is not applicable in Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.
<27> Section 2.2.3.2.1: The ConfigBlob element is not applicable in Windows XP and Windows Server 2003.
<28> Section 2.2.3.2.1: EAP-TTLS, EAP-SIM, EAP-AKA, and EAP-AKA' are not supported on Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. EAP-TEAP is supported on Windows 10 v2004 operating system and later.
<29> Section 2.2.3.2.5: The client-side plug-in does not support EapTlsConnectionPropertiesV2 on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.
<30> Section 2.2.3.2.5: The client-side plug-in does not support EapTlsConnectionPropertiesV3 on Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.
<31> Section 2.2.3.2.6: The client-side plug-in does not support IdentityPrivacy as an element of MsPeapConnectionProperties on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.
<32> Section 2.2.3.2.6: The client-side plug-in does not support MsPeapConnectionPropertiesV2 on Windows XP SP1, Windows Server 2003, Windows Vista, and Windows Server 2008.
<33> Section 2.2.3.2.6: The client-side plug-in does not support MsPeapConnectionPropertiesV3 on Windows XP SP1, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.
<34> Section 2.2.3.2.8: The client-side plug-in does not support PerformServerValidation on Windows XP SP1, Windows Server 2003, Windows Vista, and Windows Server 2008.
<35> Section 2.2.3.2.8: The client-side plug-in does not support AcceptServerName on Windows XP SP1, Windows Server 2003, Windows Vista, and Windows Server 2008.
<36> Section 3.1.3: The administrative-side plug-in does not support creation, deletion, or modification of XML-based wireless Group Policy on Windows Server 2003.
<37> Section 3.1.5.1: Time-out period is set to 2 minutes in Windows.
<38> Section 3.2.3: The client-side plug-in does not support processing of XML-based wireless Group Policy on the following operating systems: Windows XP SP1, Windows XP SP2, Windows XP SP3, and Windows Server 2003.