WiredNetwork CSP

This commit is contained in:
Sam Yun 2025-05-13 23:57:03 -07:00
parent 0fbc401dd2
commit 22c483af5c

View File

@ -1,7 +1,7 @@
--- ---
title: WiredNetwork CSP title: WiredNetwork CSP
description: Learn more about the WiredNetwork CSP. description: Learn more about the WiredNetwork CSP.
ms.date: 03/12/2025 ms.date: 05/14/2025
ms.topic: generated-reference ms.topic: generated-reference
--- ---
@ -32,7 +32,7 @@ The following list shows the WiredNetwork configuration service provider nodes:
<!-- Device-EnableBlockPeriod-Applicability-Begin --> <!-- Device-EnableBlockPeriod-Applicability-Begin -->
| Scope | Editions | Applicable OS | | Scope | Editions | Applicable OS |
|:--|:--|:--| |:--|:--|:--|
| ✅ Device <br> ✅ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later | | ✅ Device <br> ✅ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later <br> ✅ Windows 11, version 21H2 [10.0.22000] and later |
<!-- Device-EnableBlockPeriod-Applicability-End --> <!-- Device-EnableBlockPeriod-Applicability-End -->
<!-- Device-EnableBlockPeriod-OmaUri-Begin --> <!-- Device-EnableBlockPeriod-OmaUri-Begin -->
@ -72,7 +72,7 @@ Enable block period (minutes), used to specify the duration for which automatic
<!-- Device-LanXML-Applicability-Begin --> <!-- Device-LanXML-Applicability-Begin -->
| Scope | Editions | Applicable OS | | Scope | Editions | Applicable OS |
|:--|:--|:--| |:--|:--|:--|
| ✅ Device <br> ✅ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later | | ✅ Device <br> ✅ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later <br> ✅ Windows 11, version 21H2 [10.0.22000] and later |
<!-- Device-LanXML-Applicability-End --> <!-- Device-LanXML-Applicability-End -->
<!-- Device-LanXML-OmaUri-Begin --> <!-- Device-LanXML-OmaUri-Begin -->
@ -88,6 +88,11 @@ XML describing the wired network configuration and follows the LAN_profile schem
<!-- Device-LanXML-Editable-Begin --> <!-- Device-LanXML-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. --> <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
The profile XML must be escaped, as shown in the following examples.
> [!NOTE]
> If you need to specify other advanced conditions, such as specifying criteria for certificates that can be used by the LAN profile, you can do so by specifying this through the [EapHostConfig](/windows/win32/eaphost/eaphostconfigschema-eaphostconfig-element) portion of the LanXML ([LANProfile](/windows/win32/nativewifi/lan-profileschema-schema) > [MSM](/windows/win32/nativewifi/lan-profileschema-msm-lanprofile-element) > [security](/windows/win32/nativewifi/lan-profileschema-security-msm-element) > [OneX](/windows/win32/nativewifi/onexschema-onex-element) > EAPConfig). For more information, see [EAP configuration](./eap-configuration.md) and [Extensible Authentication Protocol (EAP) for network access](/windows-server/networking/technologies/extensible-authentication-protocol/network-access).
<!-- Device-LanXML-Editable-End --> <!-- Device-LanXML-Editable-End -->
<!-- Device-LanXML-DFProperties-Begin --> <!-- Device-LanXML-DFProperties-Begin -->
@ -101,6 +106,7 @@ XML describing the wired network configuration and follows the LAN_profile schem
<!-- Device-LanXML-Examples-Begin --> <!-- Device-LanXML-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. --> <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
See [Examples](#examples).
<!-- Device-LanXML-Examples-End --> <!-- Device-LanXML-Examples-End -->
<!-- Device-LanXML-End --> <!-- Device-LanXML-End -->
@ -111,7 +117,7 @@ XML describing the wired network configuration and follows the LAN_profile schem
<!-- User-EnableBlockPeriod-Applicability-Begin --> <!-- User-EnableBlockPeriod-Applicability-Begin -->
| Scope | Editions | Applicable OS | | Scope | Editions | Applicable OS |
|:--|:--|:--| |:--|:--|:--|
| ✅ Device <br> ✅ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later | | ✅ Device <br> ✅ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later <br> ✅ Windows 11, version 21H2 [10.0.22000] and later |
<!-- User-EnableBlockPeriod-Applicability-End --> <!-- User-EnableBlockPeriod-Applicability-End -->
<!-- User-EnableBlockPeriod-OmaUri-Begin --> <!-- User-EnableBlockPeriod-OmaUri-Begin -->
@ -151,7 +157,7 @@ Enable block period (minutes), used to specify the duration for which automatic
<!-- User-LanXML-Applicability-Begin --> <!-- User-LanXML-Applicability-Begin -->
| Scope | Editions | Applicable OS | | Scope | Editions | Applicable OS |
|:--|:--|:--| |:--|:--|:--|
| ✅ Device <br> ✅ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later | | ✅ Device <br> ✅ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later <br> ✅ Windows 11, version 21H2 [10.0.22000] and later |
<!-- User-LanXML-Applicability-End --> <!-- User-LanXML-Applicability-End -->
<!-- User-LanXML-OmaUri-Begin --> <!-- User-LanXML-OmaUri-Begin -->
@ -167,6 +173,7 @@ XML describing the wired network configuration and follows the LAN_profile schem
<!-- User-LanXML-Editable-Begin --> <!-- User-LanXML-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. --> <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
For more information, see [Device/LanXML](#devicelanxml).
<!-- User-LanXML-Editable-End --> <!-- User-LanXML-Editable-End -->
<!-- User-LanXML-DFProperties-Begin --> <!-- User-LanXML-DFProperties-Begin -->
@ -188,7 +195,7 @@ XML describing the wired network configuration and follows the LAN_profile schem
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. --> <!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
## Examples ## Examples
The following example shows how to add a wired network profile: The following example shows how to add a wired network profile that authenticates with PEAP-MSCHAPv2:
```xml ```xml
<SyncML xmlns="SYNCML:SYNCML1.2"> <SyncML xmlns="SYNCML:SYNCML1.2">
@ -202,7 +209,7 @@ The following example shows how to add a wired network profile:
<Meta> <Meta>
<Format xmlns="syncml:metinf">chr</Format> <Format xmlns="syncml:metinf">chr</Format>
</Meta> </Meta>
<Data><?xml version="1.0"?><LANProfile xmlns="http://www.microsoft.com/networking/LAN/profile/v1"><MSM><security><OneXEnforced>false</OneXEnforced><OneXEnabled>true</OneXEnabled><OneX xmlns="http://www.microsoft.com/networking/OneX/v1"><EAPConfig><EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><EapMethod><Type xmlns="http://www.microsoft.com/provisioning/EapCommon">25</Type><VendorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorId><VendorType xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorType><AuthorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</AuthorId></EapMethod><Config xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>25</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV1"><ServerValidation><DisableUserPromptForServerValidation>false</DisableUserPromptForServerValidation><ServerNames></ServerNames></ServerValidation><FastReconnect>true</FastReconnect><InnerEapOptional>false</InnerEapOptional><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>26</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsChapV2ConnectionPropertiesV1"><UseWinLogonCredentials>false</UseWinLogonCredentials></EapType></Eap><EnableQuarantineChecks>false</EnableQuarantineChecks><RequireCryptoBinding>false</RequireCryptoBinding><PeapExtensions><PerformServerValidation xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">true</PerformServerValidation><AcceptServerName xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName><PeapExtensionsV2 xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2"><AllowPromptingWhenServerCANotFound xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV3">true</AllowPromptingWhenServerCANotFound></PeapExtensionsV2></PeapExtensions></EapType></Eap></Config></EapHostConfig></EAPConfig></OneX></security></MSM></LANProfile> </Data> <Data><![CDATA[<?xml version="1.0"?><LANProfile xmlns="http://www.microsoft.com/networking/LAN/profile/v1"><MSM><security><OneXEnforced>false</OneXEnforced><OneXEnabled>true</OneXEnabled><OneX xmlns="http://www.microsoft.com/networking/OneX/v1"><EAPConfig><EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><EapMethod><Type xmlns="http://www.microsoft.com/provisioning/EapCommon">25</Type><VendorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorId><VendorType xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorType><AuthorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</AuthorId></EapMethod><Config xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>25</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV1"><ServerValidation><DisableUserPromptForServerValidation>false</DisableUserPromptForServerValidation><ServerNames></ServerNames></ServerValidation><FastReconnect>true</FastReconnect><InnerEapOptional>false</InnerEapOptional><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>26</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsChapV2ConnectionPropertiesV1"><UseWinLogonCredentials>false</UseWinLogonCredentials></EapType></Eap><EnableQuarantineChecks>false</EnableQuarantineChecks><RequireCryptoBinding>false</RequireCryptoBinding><PeapExtensions><PerformServerValidation xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">true</PerformServerValidation><AcceptServerName xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName><PeapExtensionsV2 xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2"><AllowPromptingWhenServerCANotFound xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV3">true</AllowPromptingWhenServerCANotFound></PeapExtensionsV2></PeapExtensions></EapType></Eap></Config></EapHostConfig></EAPConfig></OneX></security></MSM></LANProfile>]]></Data>
</Item> </Item>
</Add> </Add>
</SyncBody> </SyncBody>
@ -214,4 +221,6 @@ The following example shows how to add a wired network profile:
## Related articles ## Related articles
[Configuration service provider reference](configuration-service-provider-reference.md) * [Configuration service provider reference](configuration-service-provider-reference.md)
* [Extensible Authentication Protocol (EAP) for network access](/windows-server/networking/technologies/extensible-authentication-protocol/network-access)
* [Configure EAP profiles and settings in Windows](/windows-server/networking/technologies/extensible-authentication-protocol/configure-eap-profiles)