Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into recall-ga-9608247

This commit is contained in:
Meghan Stewart 2025-04-23 09:24:54 -07:00
commit 32af4d23ed
11 changed files with 2025 additions and 7 deletions

View File

@ -2,12 +2,17 @@ name: (Scheduled) Stale branch removal
permissions: permissions:
contents: write contents: write
# This workflow is designed to be run in the days up to, and including, a "deletion day", specified by 'DeleteOnDayOfMonth' in env: in https://github.com/MicrosoftDocs/microsoft-365-docs/blob/workflows-prod/.github/workflows/Shared-StaleBranch.yml.
# On the days leading up to "deletion day", the workflow will report the branches to be deleted. This lets users see which branches will be deleted. On "deletion day", those branches are deleted.
# The workflow should not be configured to run after "deletion day" so that users can review the branches were deleted.
# Recommendation: configure cron to run on days 1,15-31 where 1 is what's configured in 'DeleteOnDayOfMonth'. If 'DeleteOnDayOfMonth' is set to something else, update cron to run the two weeks leading up to it.
on: on:
schedule: schedule:
- cron: "0 9 1 * *" - cron: "0 9 1,15-31 * *"
# workflow_dispatch: workflow_dispatch:
jobs: jobs:

View File

@ -1,7 +1,7 @@
--- ---
title: Configuration service provider preview policies title: Configuration service provider preview policies
description: Learn more about configuration service provider (CSP) policies that are available for Windows Insider Preview. description: Learn more about configuration service provider (CSP) policies that are available for Windows Insider Preview.
ms.date: 04/04/2025 ms.date: 04/21/2025
ms.topic: generated-reference ms.topic: generated-reference
--- ---
@ -111,6 +111,17 @@ This article lists the policies that are applicable for Windows Insider Preview
- [StartInstallation](language-pack-management-csp.md#installlanguage-idstartinstallation) - [StartInstallation](language-pack-management-csp.md#installlanguage-idstartinstallation)
- [SystemPreferredUILanguages](language-pack-management-csp.md#languagesettingssystempreferreduilanguages) - [SystemPreferredUILanguages](language-pack-management-csp.md#languagesettingssystempreferreduilanguages)
## LanmanServer
- [AuditClientDoesNotSupportEncryption](policy-csp-lanmanserver.md#auditclientdoesnotsupportencryption)
- [AuditClientDoesNotSupportSigning](policy-csp-lanmanserver.md#auditclientdoesnotsupportsigning)
- [AuditInsecureGuestLogon](policy-csp-lanmanserver.md#auditinsecureguestlogon)
- [AuthRateLimiterDelayInMs](policy-csp-lanmanserver.md#authratelimiterdelayinms)
- [EnableAuthRateLimiter](policy-csp-lanmanserver.md#enableauthratelimiter)
- [EnableMailslots](policy-csp-lanmanserver.md#enablemailslots)
- [MaxSmb2Dialect](policy-csp-lanmanserver.md#maxsmb2dialect)
- [MinSmb2Dialect](policy-csp-lanmanserver.md#minsmb2dialect)
## LanmanWorkstation ## LanmanWorkstation
- [AuditInsecureGuestLogon](policy-csp-lanmanworkstation.md#auditinsecureguestlogon) - [AuditInsecureGuestLogon](policy-csp-lanmanworkstation.md#auditinsecureguestlogon)
@ -218,6 +229,22 @@ This article lists the policies that are applicable for Windows Insider Preview
- [DisableSubscription](windowslicensing-csp.md#subscriptionsdisablesubscription) - [DisableSubscription](windowslicensing-csp.md#subscriptionsdisablesubscription)
- [RemoveSubscription](windowslicensing-csp.md#subscriptionsremovesubscription) - [RemoveSubscription](windowslicensing-csp.md#subscriptionsremovesubscription)
## WirelessNetworkPreference CSP
- [IsEnabled](wirelessnetworkpreference-csp.md#isenabled)
- [PreferCellularOverWiFi](wirelessnetworkpreference-csp.md#prefercellularoverwifi)
- [eSIMprofilesCount](wirelessnetworkpreference-csp.md#statusesimprofilescount)
- [eSIMprofilesMatched](wirelessnetworkpreference-csp.md#statusesimprofilesmatched)
- [eSIMpolicyStatus](wirelessnetworkpreference-csp.md#statusesimpolicystatus)
- [NetworkDiscoveryOption](wirelessnetworkpreference-csp.md#parameterscellularparametersnetworkdiscoveryoption)
- [MaxRescanIntervalInSeconds](wirelessnetworkpreference-csp.md#parameterscellularparametersmaxrescanintervalinseconds)
- [PreferredProfileWakeConnectionTimerInSeconds](wirelessnetworkpreference-csp.md#parameterscellularparameterspreferredprofilewakeconnectiontimerinseconds)
- [ProfileRegistrationTimerInSeconds](wirelessnetworkpreference-csp.md#parameterscellularparametersprofileregistrationtimerinseconds)
- [ScreenOffDurationToTriggerNetworkDiscoveryInMinutes](wirelessnetworkpreference-csp.md#parameterscellularparametersscreenoffdurationtotriggernetworkdiscoveryinminutes)
- [Priority](wirelessnetworkpreference-csp.md#connectionprofilesconnectionprofileidpriority)
- [WirelessType](wirelessnetworkpreference-csp.md#connectionprofilesconnectionprofileidwirelesstype)
- [PLMNID](wirelessnetworkpreference-csp.md#connectionprofilesconnectionprofileidcellularplmnid)
## Related articles ## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md) [Policy configuration service provider](policy-configuration-service-provider.md)

View File

@ -1,7 +1,7 @@
--- ---
title: Policy CSP title: Policy CSP
description: Learn more about the Policy CSP. description: Learn more about the Policy CSP.
ms.date: 03/12/2025 ms.date: 04/21/2025
ms.topic: generated-reference ms.topic: generated-reference
--- ---
@ -1120,6 +1120,7 @@ Specifies the name/value pair used in the policy. See the individual Area DDFs f
- [InternetExplorer](policy-csp-internetexplorer.md) - [InternetExplorer](policy-csp-internetexplorer.md)
- [Kerberos](policy-csp-kerberos.md) - [Kerberos](policy-csp-kerberos.md)
- [KioskBrowser](policy-csp-kioskbrowser.md) - [KioskBrowser](policy-csp-kioskbrowser.md)
- [LanmanServer](policy-csp-lanmanserver.md)
- [LanmanWorkstation](policy-csp-lanmanworkstation.md) - [LanmanWorkstation](policy-csp-lanmanworkstation.md)
- [Licensing](policy-csp-licensing.md) - [Licensing](policy-csp-licensing.md)
- [LocalPoliciesSecurityOptions](policy-csp-localpoliciessecurityoptions.md) - [LocalPoliciesSecurityOptions](policy-csp-localpoliciessecurityoptions.md)

View File

@ -0,0 +1,557 @@
---
title: LanmanServer Policy CSP
description: Learn more about the LanmanServer Area in Policy CSP.
ms.date: 04/21/2025
ms.topic: generated-reference
---
<!-- Auto-Generated CSP Document -->
<!-- LanmanServer-Begin -->
# Policy CSP - LanmanServer
[!INCLUDE [Windows Insider tip](includes/mdm-insider-csp-note.md)]
<!-- LanmanServer-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- LanmanServer-Editable-End -->
<!-- AuditClientDoesNotSupportEncryption-Begin -->
## AuditClientDoesNotSupportEncryption
<!-- AuditClientDoesNotSupportEncryption-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 11, version 24H2 [10.0.26100.3613] and later <br> ✅ Windows Insider Preview |
<!-- AuditClientDoesNotSupportEncryption-Applicability-End -->
<!-- AuditClientDoesNotSupportEncryption-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/LanmanServer/AuditClientDoesNotSupportEncryption
```
<!-- AuditClientDoesNotSupportEncryption-OmaUri-End -->
<!-- AuditClientDoesNotSupportEncryption-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy controls whether the SMB server will log the event when the SMB client doesn't support encryption.
- If you enable this policy setting, the SMB server will log the event when the SMB client doesn't support encryption.
- If you disable or don't configure this policy setting, the SMB server won't log the event.
<!-- AuditClientDoesNotSupportEncryption-Description-End -->
<!-- AuditClientDoesNotSupportEncryption-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- AuditClientDoesNotSupportEncryption-Editable-End -->
<!-- AuditClientDoesNotSupportEncryption-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- AuditClientDoesNotSupportEncryption-DFProperties-End -->
<!-- AuditClientDoesNotSupportEncryption-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 0 (Default) | Disabled. |
| 1 | Enabled. |
<!-- AuditClientDoesNotSupportEncryption-AllowedValues-End -->
<!-- AuditClientDoesNotSupportEncryption-GpMapping-Begin -->
**Group policy mapping**:
| Name | Value |
|:--|:--|
| Name | Pol_AuditClientDoesNotSupportEncryption |
| Friendly Name | Audit client does not support encryption |
| Location | Computer Configuration |
| Path | Network > Lanman Server |
| Registry Key Name | Software\Policies\Microsoft\Windows\LanmanServer |
| Registry Value Name | AuditClientDoesNotSupportEncryption |
| ADMX File Name | LanmanServer.admx |
<!-- AuditClientDoesNotSupportEncryption-GpMapping-End -->
<!-- AuditClientDoesNotSupportEncryption-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- AuditClientDoesNotSupportEncryption-Examples-End -->
<!-- AuditClientDoesNotSupportEncryption-End -->
<!-- AuditClientDoesNotSupportSigning-Begin -->
## AuditClientDoesNotSupportSigning
<!-- AuditClientDoesNotSupportSigning-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 11, version 24H2 [10.0.26100.3613] and later <br> ✅ Windows Insider Preview |
<!-- AuditClientDoesNotSupportSigning-Applicability-End -->
<!-- AuditClientDoesNotSupportSigning-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/LanmanServer/AuditClientDoesNotSupportSigning
```
<!-- AuditClientDoesNotSupportSigning-OmaUri-End -->
<!-- AuditClientDoesNotSupportSigning-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy controls whether the SMB server will log the event when the SMB client doesn't support signing.
If you enable this policy setting, the SMB server will log the event when the SMB client doesn't support signing.
<!-- AuditClientDoesNotSupportSigning-Description-End -->
<!-- AuditClientDoesNotSupportSigning-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- AuditClientDoesNotSupportSigning-Editable-End -->
<!-- AuditClientDoesNotSupportSigning-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- AuditClientDoesNotSupportSigning-DFProperties-End -->
<!-- AuditClientDoesNotSupportSigning-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 0 (Default) | Disabled. |
| 1 | Enabled. |
<!-- AuditClientDoesNotSupportSigning-AllowedValues-End -->
<!-- AuditClientDoesNotSupportSigning-GpMapping-Begin -->
**Group policy mapping**:
| Name | Value |
|:--|:--|
| Name | Pol_AuditClientDoesNotSupportSigning |
| Friendly Name | Audit client does not support signing |
| Location | Computer Configuration |
| Path | Network > Lanman Server |
| Registry Key Name | Software\Policies\Microsoft\Windows\LanmanServer |
| Registry Value Name | AuditClientDoesNotSupportSigning |
| ADMX File Name | LanmanServer.admx |
<!-- AuditClientDoesNotSupportSigning-GpMapping-End -->
<!-- AuditClientDoesNotSupportSigning-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- AuditClientDoesNotSupportSigning-Examples-End -->
<!-- AuditClientDoesNotSupportSigning-End -->
<!-- AuditInsecureGuestLogon-Begin -->
## AuditInsecureGuestLogon
<!-- AuditInsecureGuestLogon-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 11, version 24H2 [10.0.26100.3613] and later <br> ✅ Windows Insider Preview |
<!-- AuditInsecureGuestLogon-Applicability-End -->
<!-- AuditInsecureGuestLogon-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/LanmanServer/AuditInsecureGuestLogon
```
<!-- AuditInsecureGuestLogon-OmaUri-End -->
<!-- AuditInsecureGuestLogon-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy controls whether the SMB server will enable the audit event when the client is logged-on as guest account.
- If you enable this policy setting, the SMB server will log the event when the client is logged-on as guest account.
- If you disable or don't configure this policy setting, the SMB server won't log the event.
<!-- AuditInsecureGuestLogon-Description-End -->
<!-- AuditInsecureGuestLogon-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- AuditInsecureGuestLogon-Editable-End -->
<!-- AuditInsecureGuestLogon-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- AuditInsecureGuestLogon-DFProperties-End -->
<!-- AuditInsecureGuestLogon-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 0 (Default) | Disabled. |
| 1 | Enabled. |
<!-- AuditInsecureGuestLogon-AllowedValues-End -->
<!-- AuditInsecureGuestLogon-GpMapping-Begin -->
**Group policy mapping**:
| Name | Value |
|:--|:--|
| Name | Pol_AuditInsecureGuestLogon |
| Friendly Name | Audit insecure guest logon |
| Location | Computer Configuration |
| Path | Network > Lanman Server |
| Registry Key Name | Software\Policies\Microsoft\Windows\LanmanServer |
| Registry Value Name | AuditInsecureGuestLogon |
| ADMX File Name | LanmanServer.admx |
<!-- AuditInsecureGuestLogon-GpMapping-End -->
<!-- AuditInsecureGuestLogon-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- AuditInsecureGuestLogon-Examples-End -->
<!-- AuditInsecureGuestLogon-End -->
<!-- AuthRateLimiterDelayInMs-Begin -->
## AuthRateLimiterDelayInMs
<!-- AuthRateLimiterDelayInMs-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 11, version 24H2 [10.0.26100.3613] and later <br> ✅ Windows Insider Preview |
<!-- AuthRateLimiterDelayInMs-Applicability-End -->
<!-- AuthRateLimiterDelayInMs-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/LanmanServer/AuthRateLimiterDelayInMs
```
<!-- AuthRateLimiterDelayInMs-OmaUri-End -->
<!-- AuthRateLimiterDelayInMs-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy controls whether the SMB server will use a default value in milliseconds for the invalid authentication delay.
- If you configure this policy setting, the authentication rate limiter will use the specified value for delaying invalid authentication attempts.
- If you don't configure this policy setting, the authentication rate limiter will use the default value or the value from local registry under HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters.
<!-- AuthRateLimiterDelayInMs-Description-End -->
<!-- AuthRateLimiterDelayInMs-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- AuthRateLimiterDelayInMs-Editable-End -->
<!-- AuthRateLimiterDelayInMs-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Allowed Values | Range: `[0-10000]` |
| Default Value | 2000 |
<!-- AuthRateLimiterDelayInMs-DFProperties-End -->
<!-- AuthRateLimiterDelayInMs-GpMapping-Begin -->
**Group policy mapping**:
| Name | Value |
|:--|:--|
| Name | Pol_AuthRateLimiterDelayInMs |
| Friendly Name | Set authentication rate limiter delay (milliseconds) |
| Location | Computer Configuration |
| Path | Network > Lanman Server |
| Registry Key Name | Software\Policies\Microsoft\Windows\LanmanServer |
| ADMX File Name | LanmanServer.admx |
<!-- AuthRateLimiterDelayInMs-GpMapping-End -->
<!-- AuthRateLimiterDelayInMs-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- AuthRateLimiterDelayInMs-Examples-End -->
<!-- AuthRateLimiterDelayInMs-End -->
<!-- EnableAuthRateLimiter-Begin -->
## EnableAuthRateLimiter
<!-- EnableAuthRateLimiter-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 11, version 24H2 [10.0.26100.3613] and later <br> ✅ Windows Insider Preview |
<!-- EnableAuthRateLimiter-Applicability-End -->
<!-- EnableAuthRateLimiter-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/LanmanServer/EnableAuthRateLimiter
```
<!-- EnableAuthRateLimiter-OmaUri-End -->
<!-- EnableAuthRateLimiter-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy controls whether the SMB server will enable or disable the authentication rate limiter.
- If you disable this policy setting, the authentication rate limiter won't be enabled.
- If you don't configure this policy setting, the authentication rate limiter may still be working depending on the delay settings (the recommended delay value is 2000ms).
<!-- EnableAuthRateLimiter-Description-End -->
<!-- EnableAuthRateLimiter-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- EnableAuthRateLimiter-Editable-End -->
<!-- EnableAuthRateLimiter-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 1 |
<!-- EnableAuthRateLimiter-DFProperties-End -->
<!-- EnableAuthRateLimiter-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 0 | Disabled. |
| 1 (Default) | Enabled. |
<!-- EnableAuthRateLimiter-AllowedValues-End -->
<!-- EnableAuthRateLimiter-GpMapping-Begin -->
**Group policy mapping**:
| Name | Value |
|:--|:--|
| Name | Pol_EnableAuthRateLimiter |
| Friendly Name | Enable authentication rate limiter |
| Location | Computer Configuration |
| Path | Network > Lanman Server |
| Registry Key Name | Software\Policies\Microsoft\Windows\LanmanServer |
| Registry Value Name | EnableAuthRateLimiter |
| ADMX File Name | LanmanServer.admx |
<!-- EnableAuthRateLimiter-GpMapping-End -->
<!-- EnableAuthRateLimiter-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- EnableAuthRateLimiter-Examples-End -->
<!-- EnableAuthRateLimiter-End -->
<!-- EnableMailslots-Begin -->
## EnableMailslots
<!-- EnableMailslots-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 11, version 24H2 [10.0.26100.3613] and later <br> ✅ Windows Insider Preview |
<!-- EnableMailslots-Applicability-End -->
<!-- EnableMailslots-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/LanmanServer/EnableMailslots
```
<!-- EnableMailslots-OmaUri-End -->
<!-- EnableMailslots-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy controls whether the SMB server will enable or disable remote mailslots over the computer browser service.
- If you disable this policy setting, the computer browser service will no longer run as expected.
- If you don't configure this policy setting, the computer browser may still be working with remote mailslots enabled.
> [!NOTE]
> This policy requires a Windows reboot to take effect.
<!-- EnableMailslots-Description-End -->
<!-- EnableMailslots-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- EnableMailslots-Editable-End -->
<!-- EnableMailslots-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- EnableMailslots-DFProperties-End -->
<!-- EnableMailslots-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 0 (Default) | Disabled. |
| 1 | Enabled. |
<!-- EnableMailslots-AllowedValues-End -->
<!-- EnableMailslots-GpMapping-Begin -->
**Group policy mapping**:
| Name | Value |
|:--|:--|
| Name | Pol_EnableMailslots |
| Friendly Name | Enable remote mailslots |
| Location | Computer Configuration |
| Path | Network > Lanman Server |
| Registry Key Name | Software\Policies\Microsoft\Windows\Bowser |
| Registry Value Name | EnableMailslots |
| ADMX File Name | LanmanServer.admx |
<!-- EnableMailslots-GpMapping-End -->
<!-- EnableMailslots-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- EnableMailslots-Examples-End -->
<!-- EnableMailslots-End -->
<!-- MaxSmb2Dialect-Begin -->
## MaxSmb2Dialect
<!-- MaxSmb2Dialect-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 11, version 24H2 [10.0.26100.3613] and later <br> ✅ Windows Insider Preview |
<!-- MaxSmb2Dialect-Applicability-End -->
<!-- MaxSmb2Dialect-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/LanmanServer/MaxSmb2Dialect
```
<!-- MaxSmb2Dialect-OmaUri-End -->
<!-- MaxSmb2Dialect-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy controls the maximum version of SMB protocol.
> [!NOTE]
> This group policy doesn't prevent use of SMB 1 if that component is still installed and enabled.
<!-- MaxSmb2Dialect-Description-End -->
<!-- MaxSmb2Dialect-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- MaxSmb2Dialect-Editable-End -->
<!-- MaxSmb2Dialect-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 785 |
<!-- MaxSmb2Dialect-DFProperties-End -->
<!-- MaxSmb2Dialect-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 514 | SMB 2.0.2. |
| 528 | SMB 2.1.0. |
| 768 | SMB 3.0.0. |
| 770 | SMB 3.0.2. |
| 785 (Default) | SMB 3.1.1. |
<!-- MaxSmb2Dialect-AllowedValues-End -->
<!-- MaxSmb2Dialect-GpMapping-Begin -->
**Group policy mapping**:
| Name | Value |
|:--|:--|
| Name | Pol_MaxSmb2Dialect |
| Friendly Name | Mandate the maximum version of SMB |
| Location | Computer Configuration |
| Path | Network > Lanman Server |
| Registry Key Name | Software\Policies\Microsoft\Windows\LanmanServer |
| ADMX File Name | LanmanServer.admx |
<!-- MaxSmb2Dialect-GpMapping-End -->
<!-- MaxSmb2Dialect-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- MaxSmb2Dialect-Examples-End -->
<!-- MaxSmb2Dialect-End -->
<!-- MinSmb2Dialect-Begin -->
## MinSmb2Dialect
<!-- MinSmb2Dialect-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 11, version 24H2 [10.0.26100.3613] and later <br> ✅ Windows Insider Preview |
<!-- MinSmb2Dialect-Applicability-End -->
<!-- MinSmb2Dialect-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/LanmanServer/MinSmb2Dialect
```
<!-- MinSmb2Dialect-OmaUri-End -->
<!-- MinSmb2Dialect-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy controls the minimum version of SMB protocol.
> [!NOTE]
> This group policy doesn't prevent use of SMB 1 if that component is still installed and enabled.
<!-- MinSmb2Dialect-Description-End -->
<!-- MinSmb2Dialect-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- MinSmb2Dialect-Editable-End -->
<!-- MinSmb2Dialect-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 514 |
<!-- MinSmb2Dialect-DFProperties-End -->
<!-- MinSmb2Dialect-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 514 (Default) | SMB 2.0.2. |
| 528 | SMB 2.1.0. |
| 768 | SMB 3.0.0. |
| 770 | SMB 3.0.2. |
| 785 | SMB 3.1.1. |
<!-- MinSmb2Dialect-AllowedValues-End -->
<!-- MinSmb2Dialect-GpMapping-Begin -->
**Group policy mapping**:
| Name | Value |
|:--|:--|
| Name | Pol_MinSmb2Dialect |
| Friendly Name | Mandate the minimum version of SMB |
| Location | Computer Configuration |
| Path | Network > Lanman Server |
| Registry Key Name | Software\Policies\Microsoft\Windows\LanmanServer |
| ADMX File Name | LanmanServer.admx |
<!-- MinSmb2Dialect-GpMapping-End -->
<!-- MinSmb2Dialect-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- MinSmb2Dialect-Examples-End -->
<!-- MinSmb2Dialect-End -->
<!-- LanmanServer-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- LanmanServer-CspMoreInfo-End -->
<!-- LanmanServer-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)

View File

@ -471,6 +471,8 @@ items:
href: policy-csp-kerberos.md href: policy-csp-kerberos.md
- name: KioskBrowser - name: KioskBrowser
href: policy-csp-kioskbrowser.md href: policy-csp-kioskbrowser.md
- name: LanmanServer
href: policy-csp-lanmanserver.md
- name: LanmanWorkstation - name: LanmanWorkstation
href: policy-csp-lanmanworkstation.md href: policy-csp-lanmanworkstation.md
- name: Licensing - name: Licensing
@ -999,3 +1001,8 @@ items:
items: items:
- name: WiredNetwork DDF file - name: WiredNetwork DDF file
href: wirednetwork-ddf-file.md href: wirednetwork-ddf-file.md
- name: WirelessNetworkPreference
href: wirelessnetworkpreference-csp.md
items:
- name: WirelessNetworkPreference DDF file
href: wirelessnetworkpreference-ddf-file.md

View File

@ -0,0 +1,844 @@
---
title: WirelessNetworkPreference CSP
description: Learn more about the WirelessNetworkPreference CSP.
ms.date: 04/21/2025
ms.topic: generated-reference
---
<!-- Auto-Generated CSP Document -->
<!-- WirelessNetworkPreference-Begin -->
# WirelessNetworkPreference CSP
[!INCLUDE [Windows Insider tip](includes/mdm-insider-csp-note.md)]
<!-- WirelessNetworkPreference-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- WirelessNetworkPreference-Editable-End -->
<!-- WirelessNetworkPreference-Tree-Begin -->
The following list shows the WirelessNetworkPreference configuration service provider nodes:
- ./Device/Vendor/MSFT/WirelessNetworkPreference
- [ConnectionProfiles](#connectionprofiles)
- [{ConnectionProfileID}](#connectionprofilesconnectionprofileid)
- [Cellular](#connectionprofilesconnectionprofileidcellular)
- [PLMNID](#connectionprofilesconnectionprofileidcellularplmnid)
- [Priority](#connectionprofilesconnectionprofileidpriority)
- [WirelessType](#connectionprofilesconnectionprofileidwirelesstype)
- [IsEnabled](#isenabled)
- [Parameters](#parameters)
- [CellularParameters](#parameterscellularparameters)
- [MaxRescanIntervalInSeconds](#parameterscellularparametersmaxrescanintervalinseconds)
- [NetworkDiscoveryOption](#parameterscellularparametersnetworkdiscoveryoption)
- [PreferredProfileWakeConnectionTimerInSeconds](#parameterscellularparameterspreferredprofilewakeconnectiontimerinseconds)
- [ProfileRegistrationTimerInSeconds](#parameterscellularparametersprofileregistrationtimerinseconds)
- [ScreenOffDurationToTriggerNetworkDiscoveryInMinutes](#parameterscellularparametersscreenoffdurationtotriggernetworkdiscoveryinminutes)
- [PreferCellularOverWiFi](#prefercellularoverwifi)
- [Status](#status)
- [eSIMpolicyStatus](#statusesimpolicystatus)
- [eSIMprofilesCount](#statusesimprofilescount)
- [eSIMprofilesMatched](#statusesimprofilesmatched)
<!-- WirelessNetworkPreference-Tree-End -->
<!-- Device-ConnectionProfiles-Begin -->
## ConnectionProfiles
<!-- Device-ConnectionProfiles-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-ConnectionProfiles-Applicability-End -->
<!-- Device-ConnectionProfiles-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/ConnectionProfiles
```
<!-- Device-ConnectionProfiles-OmaUri-End -->
<!-- Device-ConnectionProfiles-Description-Begin -->
<!-- Description-Source-DDF -->
Profiles to connect to wireless networks in a specified priority order.
<!-- Device-ConnectionProfiles-Description-End -->
<!-- Device-ConnectionProfiles-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-Editable-End -->
<!-- Device-ConnectionProfiles-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `node` |
| Access Type | Get |
<!-- Device-ConnectionProfiles-DFProperties-End -->
<!-- Device-ConnectionProfiles-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-Examples-End -->
<!-- Device-ConnectionProfiles-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Begin -->
### ConnectionProfiles/{ConnectionProfileID}
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Applicability-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/ConnectionProfiles/{ConnectionProfileID}
```
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-OmaUri-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Description-Begin -->
<!-- Description-Source-DDF -->
Unique identifier of a network preference policy. Unique ID is auto-generated.
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Description-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Editable-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `node` |
| Access Type | Add, Delete, Get |
| Dynamic Node Naming | ServerGeneratedUniqueIdentifier |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-DFProperties-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Examples-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Begin -->
#### ConnectionProfiles/{ConnectionProfileID}/Cellular
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Applicability-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/ConnectionProfiles/{ConnectionProfileID}/Cellular
```
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-OmaUri-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Description-Begin -->
<!-- Description-Source-DDF -->
Identifiers for cellular networks.
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Description-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Editable-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `node` |
| Access Type | Add, Delete, Get |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-DFProperties-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-Examples-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Begin -->
##### ConnectionProfiles/{ConnectionProfileID}/Cellular/PLMNID
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Applicability-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/ConnectionProfiles/{ConnectionProfileID}/Cellular/PLMNID
```
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-OmaUri-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Description-Begin -->
<!-- Description-Source-DDF -->
5- or 6-digit string identifying a cellular network. It consists of the combination of Mobile Country Code (MCC) and Mobile Network Code (MNC).
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Description-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Editable-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `chr` (string) |
| Access Type | Add, Delete, Get, Replace |
| Allowed Values | Regular Expression: `^[0-9]{5,6}$` |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-DFProperties-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-Examples-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Cellular-PLMNID-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Begin -->
#### ConnectionProfiles/{ConnectionProfileID}/Priority
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Applicability-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/ConnectionProfiles/{ConnectionProfileID}/Priority
```
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-OmaUri-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Description-Begin -->
<!-- Description-Source-DDF -->
Priority of a policy compared to the others where 1 represents the highest priority. Thus, the smaller this value is, the higher preference this specific network will receive in establishing a data connection.
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Description-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Editable-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Add, Delete, Get, Replace |
| Allowed Values | Range: `[1-2147483647]` |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-DFProperties-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-Examples-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-Priority-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Begin -->
#### ConnectionProfiles/{ConnectionProfileID}/WirelessType
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Applicability-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/ConnectionProfiles/{ConnectionProfileID}/WirelessType
```
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-OmaUri-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Description-Begin -->
<!-- Description-Source-DDF -->
Type of wireless network (either Cellular or Wi-Fi). 0 represents Cellular, and 1 represents Wi-Fi. Currently only cellular is supported.
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Description-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Editable-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `bin` |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-DFProperties-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 0 (Default) | Cellular. |
| 1 | Wi-Fi. |
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-AllowedValues-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-Examples-End -->
<!-- Device-ConnectionProfiles-{ConnectionProfileID}-WirelessType-End -->
<!-- Device-IsEnabled-Begin -->
## IsEnabled
<!-- Device-IsEnabled-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-IsEnabled-Applicability-End -->
<!-- Device-IsEnabled-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/IsEnabled
```
<!-- Device-IsEnabled-OmaUri-End -->
<!-- Device-IsEnabled-Description-Begin -->
<!-- Description-Source-DDF -->
It determines whether the wireless connectivity management policy is enabled or not.
<!-- Device-IsEnabled-Description-End -->
<!-- Device-IsEnabled-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-IsEnabled-Editable-End -->
<!-- Device-IsEnabled-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `bool` |
| Access Type | Get, Replace |
| Default Value | False |
<!-- Device-IsEnabled-DFProperties-End -->
<!-- Device-IsEnabled-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| False (Default) | Disable the wireless management policy. |
| True | Enable the wireless management policy. |
<!-- Device-IsEnabled-AllowedValues-End -->
<!-- Device-IsEnabled-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-IsEnabled-Examples-End -->
<!-- Device-IsEnabled-End -->
<!-- Device-Parameters-Begin -->
## Parameters
<!-- Device-Parameters-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Parameters-Applicability-End -->
<!-- Device-Parameters-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Parameters
```
<!-- Device-Parameters-OmaUri-End -->
<!-- Device-Parameters-Description-Begin -->
<!-- Description-Source-DDF -->
Parameters to configure the behavior of the wireless connectivity management service.
<!-- Device-Parameters-Description-End -->
<!-- Device-Parameters-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Parameters-Editable-End -->
<!-- Device-Parameters-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `node` |
| Access Type | Get |
<!-- Device-Parameters-DFProperties-End -->
<!-- Device-Parameters-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Parameters-Examples-End -->
<!-- Device-Parameters-End -->
<!-- Device-Parameters-CellularParameters-Begin -->
### Parameters/CellularParameters
<!-- Device-Parameters-CellularParameters-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Parameters-CellularParameters-Applicability-End -->
<!-- Device-Parameters-CellularParameters-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Parameters/CellularParameters
```
<!-- Device-Parameters-CellularParameters-OmaUri-End -->
<!-- Device-Parameters-CellularParameters-Description-Begin -->
<!-- Description-Source-DDF -->
Parameters to configure the cellular-specific behavior of the wireless connectivity management service.
<!-- Device-Parameters-CellularParameters-Description-End -->
<!-- Device-Parameters-CellularParameters-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-Editable-End -->
<!-- Device-Parameters-CellularParameters-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `node` |
| Access Type | Get |
<!-- Device-Parameters-CellularParameters-DFProperties-End -->
<!-- Device-Parameters-CellularParameters-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-Examples-End -->
<!-- Device-Parameters-CellularParameters-End -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Begin -->
#### Parameters/CellularParameters/MaxRescanIntervalInSeconds
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Applicability-End -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Parameters/CellularParameters/MaxRescanIntervalInSeconds
```
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-OmaUri-End -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Description-Begin -->
<!-- Description-Source-DDF -->
Maximum time (in seconds) from the point that no connection could be established using the permissible eSIM profiles on the device to the start of the next round of network discovery attempts. A smaller interval increases network discovery frequency and can decrease battery life significantly. A value of 0 means that the device is to pick a reasonable interval per its own discretion.
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Description-End -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Editable-End -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Get, Replace |
| Allowed Values | Range: `[0-360]` |
| Default Value | 0 |
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-DFProperties-End -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-Examples-End -->
<!-- Device-Parameters-CellularParameters-MaxRescanIntervalInSeconds-End -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Begin -->
#### Parameters/CellularParameters/NetworkDiscoveryOption
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Applicability-End -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Parameters/CellularParameters/NetworkDiscoveryOption
```
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-OmaUri-End -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Description-Begin -->
<!-- Description-Source-DDF -->
Configures which approach should be used in the network discovery process. There are two possible values: (0) no network scan will be performed - rather, registration and connection will be attempted with each eSIM profile in descending order of preference; or (1) Network scan will be performed using the current active eSIM profile. This option works for modems that when performing a network scan show the complete list of available networks independently of which eSIM profile is active.
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Description-End -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Editable-End -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Get, Replace |
| Default Value | 0 |
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-DFProperties-End -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| 0 (Default) | No network scan will be performed -- rather, registration and connection will be attempted with each eSIM profile in descending order of preference. |
| 1 | Network scan will be performed using the current active eSIM profile. |
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-AllowedValues-End -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-Examples-End -->
<!-- Device-Parameters-CellularParameters-NetworkDiscoveryOption-End -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Begin -->
#### Parameters/CellularParameters/PreferredProfileWakeConnectionTimerInSeconds
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Applicability-End -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Parameters/CellularParameters/PreferredProfileWakeConnectionTimerInSeconds
```
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-OmaUri-End -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Description-Begin -->
<!-- Description-Source-DDF -->
When the device is woken from sleep with the most-preferred profile already enabled, this value configures the amount of time (in seconds) before the agent will give up on waiting for connection re-establishment with the most-preferred profile and start network discovery.
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Description-End -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Editable-End -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Get, Replace |
| Allowed Values | Range: `[30-360]` |
| Default Value | 200 |
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-DFProperties-End -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-Examples-End -->
<!-- Device-Parameters-CellularParameters-PreferredProfileWakeConnectionTimerInSeconds-End -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Begin -->
#### Parameters/CellularParameters/ProfileRegistrationTimerInSeconds
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Applicability-End -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Parameters/CellularParameters/ProfileRegistrationTimerInSeconds
```
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-OmaUri-End -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Description-Begin -->
<!-- Description-Source-DDF -->
When evaluating eSIM profiles for connectivity, this value configures the amount of time (in seconds) that the agent will wait for network registration before considering this profile unsatisfactory and moving on to the next one.
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Description-End -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Editable-End -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Get, Replace |
| Allowed Values | Range: `[30-360]` |
| Default Value | 60 |
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-DFProperties-End -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-Examples-End -->
<!-- Device-Parameters-CellularParameters-ProfileRegistrationTimerInSeconds-End -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Begin -->
#### Parameters/CellularParameters/ScreenOffDurationToTriggerNetworkDiscoveryInMinutes
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Applicability-End -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Parameters/CellularParameters/ScreenOffDurationToTriggerNetworkDiscoveryInMinutes
```
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-OmaUri-End -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Description-Begin -->
<!-- Description-Source-DDF -->
When the device experiences screen off and back on, this value configures the minimum duration (in minutes) of the screen off period that will trigger network discovery.
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Description-End -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Editable-End -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Get, Replace |
| Allowed Values | Range: `[0-30]` |
| Default Value | 10 |
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-DFProperties-End -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-Examples-End -->
<!-- Device-Parameters-CellularParameters-ScreenOffDurationToTriggerNetworkDiscoveryInMinutes-End -->
<!-- Device-PreferCellularOverWiFi-Begin -->
## PreferCellularOverWiFi
<!-- Device-PreferCellularOverWiFi-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-PreferCellularOverWiFi-Applicability-End -->
<!-- Device-PreferCellularOverWiFi-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/PreferCellularOverWiFi
```
<!-- Device-PreferCellularOverWiFi-OmaUri-End -->
<!-- Device-PreferCellularOverWiFi-Description-Begin -->
<!-- Description-Source-DDF -->
It determines the order of preference between Wi-Fi and cellular networks. When the value is set to "False", Wi-Fi is preferred over cellular. When the value is set to "True", cellular is preferred over Wi-Fi.
<!-- Device-PreferCellularOverWiFi-Description-End -->
<!-- Device-PreferCellularOverWiFi-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-PreferCellularOverWiFi-Editable-End -->
<!-- Device-PreferCellularOverWiFi-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `bool` |
| Access Type | Get, Replace |
| Default Value | False |
<!-- Device-PreferCellularOverWiFi-DFProperties-End -->
<!-- Device-PreferCellularOverWiFi-AllowedValues-Begin -->
**Allowed values**:
| Value | Description |
|:--|:--|
| False (Default) | Prefer Wi-Fi over Cellular. |
| True | Prefer Cellular over Wi-Fi. |
<!-- Device-PreferCellularOverWiFi-AllowedValues-End -->
<!-- Device-PreferCellularOverWiFi-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-PreferCellularOverWiFi-Examples-End -->
<!-- Device-PreferCellularOverWiFi-End -->
<!-- Device-Status-Begin -->
## Status
<!-- Device-Status-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Status-Applicability-End -->
<!-- Device-Status-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Status
```
<!-- Device-Status-OmaUri-End -->
<!-- Device-Status-Description-Begin -->
<!-- Description-Source-DDF -->
Nodes that indicate the status of the wireless connectivity management service.
<!-- Device-Status-Description-End -->
<!-- Device-Status-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Status-Editable-End -->
<!-- Device-Status-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `node` |
| Access Type | Get |
<!-- Device-Status-DFProperties-End -->
<!-- Device-Status-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Status-Examples-End -->
<!-- Device-Status-End -->
<!-- Device-Status-eSIMpolicyStatus-Begin -->
### Status/eSIMpolicyStatus
<!-- Device-Status-eSIMpolicyStatus-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Status-eSIMpolicyStatus-Applicability-End -->
<!-- Device-Status-eSIMpolicyStatus-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Status/eSIMpolicyStatus
```
<!-- Device-Status-eSIMpolicyStatus-OmaUri-End -->
<!-- Device-Status-eSIMpolicyStatus-Description-Begin -->
<!-- Description-Source-DDF -->
An integer indicating the current status of the wireless connectivity management service. If the value is zero, there are no errors. \n\n 0 = No errors. \n 1 = No policies are configured. \n 2 = More than one policy has the same priority. \n 3 = More than one policy references the same PLMNID. \n 4 = Invalid PLMNID for one or more of the configured profiles. \n 5 = More than one eSIM profile stored in the eUICC with the same PLMN ID. \n 6 = Invalid configuration value for one or more of the cellular parameters. Please review CSP documentation. \n\n Warning: Any of these errors will result in a complete halt of the wireless connectivity management service.
<!-- Device-Status-eSIMpolicyStatus-Description-End -->
<!-- Device-Status-eSIMpolicyStatus-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Status-eSIMpolicyStatus-Editable-End -->
<!-- Device-Status-eSIMpolicyStatus-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Get |
<!-- Device-Status-eSIMpolicyStatus-DFProperties-End -->
<!-- Device-Status-eSIMpolicyStatus-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Status-eSIMpolicyStatus-Examples-End -->
<!-- Device-Status-eSIMpolicyStatus-End -->
<!-- Device-Status-eSIMprofilesCount-Begin -->
### Status/eSIMprofilesCount
<!-- Device-Status-eSIMprofilesCount-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Status-eSIMprofilesCount-Applicability-End -->
<!-- Device-Status-eSIMprofilesCount-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Status/eSIMprofilesCount
```
<!-- Device-Status-eSIMprofilesCount-OmaUri-End -->
<!-- Device-Status-eSIMprofilesCount-Description-Begin -->
<!-- Description-Source-DDF -->
Count of operational eSIM profiles stored in the eUICC.
<!-- Device-Status-eSIMprofilesCount-Description-End -->
<!-- Device-Status-eSIMprofilesCount-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Status-eSIMprofilesCount-Editable-End -->
<!-- Device-Status-eSIMprofilesCount-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Get |
<!-- Device-Status-eSIMprofilesCount-DFProperties-End -->
<!-- Device-Status-eSIMprofilesCount-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Status-eSIMprofilesCount-Examples-End -->
<!-- Device-Status-eSIMprofilesCount-End -->
<!-- Device-Status-eSIMprofilesMatched-Begin -->
### Status/eSIMprofilesMatched
<!-- Device-Status-eSIMprofilesMatched-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows Insider Preview |
<!-- Device-Status-eSIMprofilesMatched-Applicability-End -->
<!-- Device-Status-eSIMprofilesMatched-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/WirelessNetworkPreference/Status/eSIMprofilesMatched
```
<!-- Device-Status-eSIMprofilesMatched-OmaUri-End -->
<!-- Device-Status-eSIMprofilesMatched-Description-Begin -->
<!-- Description-Source-DDF -->
Count of operational eSIM profiles stored on the eUICC whose PLMN matches one of the ConnectionProfileIDs setup under the ConnectionProfiles node. Only matched profiles with no errors will be counted. If more than one eSIM profile with the same PLMN ID is configured on the policy and/or more than one eSIM profile with the same PLMN ID is stored in the eUICC, then they won't be counted even if there is a match.
<!-- Device-Status-eSIMprofilesMatched-Description-End -->
<!-- Device-Status-eSIMprofilesMatched-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Device-Status-eSIMprofilesMatched-Editable-End -->
<!-- Device-Status-eSIMprofilesMatched-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | `int` |
| Access Type | Get |
<!-- Device-Status-eSIMprofilesMatched-DFProperties-End -->
<!-- Device-Status-eSIMprofilesMatched-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Device-Status-eSIMprofilesMatched-Examples-End -->
<!-- Device-Status-eSIMprofilesMatched-End -->
<!-- WirelessNetworkPreference-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- WirelessNetworkPreference-CspMoreInfo-End -->
<!-- WirelessNetworkPreference-End -->
## Related articles
[Configuration service provider reference](configuration-service-provider-reference.md)

View File

@ -0,0 +1,543 @@
---
title: WirelessNetworkPreference DDF file
description: View the XML file containing the device description framework (DDF) for the WirelessNetworkPreference configuration service provider.
ms.date: 04/21/2025
ms.topic: generated-reference
---
<!-- Auto-Generated CSP Document -->
# WirelessNetworkPreference DDF file
The following XML file contains the device description framework (DDF) for the WirelessNetworkPreference configuration service provider.
```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE MgmtTree PUBLIC " -//OMA//DTD-DM-DDF 1.2//EN" "http://www.openmobilealliance.org/tech/DTD/DM_DDF-V1_2.dtd"[<?oma-dm-ddf-ver supported-versions="1.2"?>]>
<MgmtTree xmlns:MSFT="http://schemas.microsoft.com/MobileDevice/DM">
<VerDTD>1.2</VerDTD>
<MSFT:Diagnostics>
</MSFT:Diagnostics>
<Node>
<NodeName>WirelessNetworkPreference</NodeName>
<Path>./Device/Vendor/MSFT</Path>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Represents information associated with wireless networks prioritization including detailed connectivity priorities for specific cellular networks with a unique PLMN_ID.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
<MSFT:Applicability>
<MSFT:OsBuildVersion>99.9.99999</MSFT:OsBuildVersion>
<MSFT:CspVersion>1.0</MSFT:CspVersion>
<MSFT:EditionAllowList>0x4;0x1B;0x30;0x31;0x48;0x54;0x62;0x63;0x64;0x65;0x79;0x7A;0x7D;0x7E;0x81;0x82;0x88;0x8A;0x8B;0xA1;0xA2;0xA4;0xA5;0xAB;0xAC;0xAF;0xBC;0xBF;0xCA;0xCB;0xCD;0xCF;0xD2;</MSFT:EditionAllowList>
</MSFT:Applicability>
</DFProperties>
<Node>
<NodeName>IsEnabled</NodeName>
<DFProperties>
<AccessType>
<Get />
<Replace />
</AccessType>
<DefaultValue>False</DefaultValue>
<Description>It determines whether the wireless connectivity management policy is enabled or not.</Description>
<DFFormat>
<bool />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="ENUM">
<MSFT:Enum>
<MSFT:Value>False</MSFT:Value>
<MSFT:ValueDescription>Disable the wireless management policy.</MSFT:ValueDescription>
</MSFT:Enum>
<MSFT:Enum>
<MSFT:Value>True</MSFT:Value>
<MSFT:ValueDescription>Enable the wireless management policy.</MSFT:ValueDescription>
</MSFT:Enum>
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>PreferCellularOverWiFi</NodeName>
<DFProperties>
<AccessType>
<Get />
<Replace />
</AccessType>
<DefaultValue>False</DefaultValue>
<Description>It determines the order of preference between Wi-Fi and cellular networks. When the value is set to “False”, Wi-Fi is preferred over cellular. When the value is set to “True”, cellular is preferred over Wi-Fi. </Description>
<DFFormat>
<bool />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="ENUM">
<MSFT:Enum>
<MSFT:Value>False</MSFT:Value>
<MSFT:ValueDescription>Prefer Wi-Fi over Cellular.</MSFT:ValueDescription>
</MSFT:Enum>
<MSFT:Enum>
<MSFT:Value>True</MSFT:Value>
<MSFT:ValueDescription>Prefer Cellular over Wi-Fi.</MSFT:ValueDescription>
</MSFT:Enum>
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>Status</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Nodes that indicate the status of the wireless connectivity management service.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
</DFProperties>
<Node>
<NodeName>eSIMprofilesCount</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Count of operational eSIM profiles stored in the eUICC.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>eSIMprofilesMatched</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Count of operational eSIM profiles stored on the eUICC whose PLMN matches one of the ConnectionProfileIDs setup under the ConnectionProfiles node. Only matched profiles with no errors will be counted. If more than one eSIM profile with the same PLMN ID is configured on the policy and/or more than one eSIM profile with the same PLMN ID is stored in the eUICC, then they will not be counted even if there is a match.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
</DFProperties>
</Node>
<Node>
<NodeName>eSIMpolicyStatus</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>An integer indicating the current status of the wireless connectivity management service. If the value is zero, there are no errors. \n\n 0 = No errors. \n 1 = No policies are configured. \n 2 = More than one policy has the same priority. \n 3 = More than one policy references the same PLMNID. \n 4 = Invalid PLMNID for one or more of the configured profiles. \n 5 = More than one eSIM profile stored in the eUICC with the same PLMN ID. \n 6 = Invalid configuration value for one or more of the cellular parameters. Please review CSP documentation. \n\n Warning: Any of these errors will result in a complete halt of the wireless connectivity management service.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
</DFProperties>
</Node>
</Node>
<Node>
<NodeName>Parameters</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Parameters to configure the behavior of the wireless connectivity management service.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
</DFProperties>
<Node>
<NodeName>CellularParameters</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Parameters to configure the cellular-specific behavior of the wireless connectivity management service.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
</DFProperties>
<Node>
<NodeName>NetworkDiscoveryOption</NodeName>
<DFProperties>
<AccessType>
<Get />
<Replace />
</AccessType>
<DefaultValue>0</DefaultValue>
<Description>Configures which approach should be used in the network discovery process. There are two possible values: (0) no network scan will be performed rather, registration and connection will be attempted with each eSIM profile in descending order of preference; or (1) Network scan will be performed using the current active eSIM profile. This option works for modems that when performing a network scan show the complete list of available networks independently of which eSIM profile is active.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="ENUM">
<MSFT:Enum>
<MSFT:Value>0</MSFT:Value>
<MSFT:ValueDescription>No network scan will be performed -- rather, registration and connection will be attempted with each eSIM profile in descending order of preference.</MSFT:ValueDescription>
</MSFT:Enum>
<MSFT:Enum>
<MSFT:Value>1</MSFT:Value>
<MSFT:ValueDescription>Network scan will be performed using the current active eSIM profile.</MSFT:ValueDescription>
</MSFT:Enum>
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>MaxRescanIntervalInSeconds</NodeName>
<DFProperties>
<AccessType>
<Get />
<Replace />
</AccessType>
<DefaultValue>0</DefaultValue>
<Description>Maximum time (in seconds) from the point that no connection could be established using the permissible eSIM profiles on the device to the start of the next round of network discovery attempts. A smaller interval increases network discovery frequency and can decrease battery life significantly. A value of 0 means that the device is to pick a reasonable interval per its own discretion.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="Range">
<MSFT:Value>[0-360]</MSFT:Value>
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>PreferredProfileWakeConnectionTimerInSeconds</NodeName>
<DFProperties>
<AccessType>
<Get />
<Replace />
</AccessType>
<DefaultValue>200</DefaultValue>
<Description>When the device is woken from sleep with the most-preferred profile already enabled, this value configures the amount of time (in seconds) before the agent will give up on waiting for connection re-establishment with the most-preferred profile and start network discovery.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="Range">
<MSFT:Value>[30-360]</MSFT:Value>
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>ProfileRegistrationTimerInSeconds</NodeName>
<DFProperties>
<AccessType>
<Get />
<Replace />
</AccessType>
<DefaultValue>60</DefaultValue>
<Description>When evaluating eSIM profiles for connectivity, this value configures the amount of time (in seconds) that the agent will wait for network registration before considering this profile unsatisfactory and moving on to the next one.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="Range">
<MSFT:Value>[30-360]</MSFT:Value>
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>ScreenOffDurationToTriggerNetworkDiscoveryInMinutes</NodeName>
<DFProperties>
<AccessType>
<Get />
<Replace />
</AccessType>
<DefaultValue>10</DefaultValue>
<Description>When the device experiences screen off and back on, this value configures the minimum duration (in minutes) of the screen off period that will trigger network discovery.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="Range">
<MSFT:Value>[0-30]</MSFT:Value>
</MSFT:AllowedValues>
</DFProperties>
</Node>
</Node>
</Node>
<Node>
<NodeName>ConnectionProfiles</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Profiles to connect to wireless networks in a specified priority order.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
</DFProperties>
<Node>
<NodeName>
</NodeName>
<DFProperties>
<AccessType>
<Add />
<Delete />
<Get />
</AccessType>
<Description>Unique identifier of a network preference policy. Unique ID is auto-generated.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<ZeroOrMore />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFTitle>ConnectionProfileID</DFTitle>
<DFType>
<DDFName />
</DFType>
<MSFT:DynamicNodeNaming>
<MSFT:ServerGeneratedUniqueIdentifier />
</MSFT:DynamicNodeNaming>
</DFProperties>
<Node>
<NodeName>Priority</NodeName>
<DFProperties>
<AccessType>
<Add />
<Delete />
<Get />
<Replace />
</AccessType>
<Description>Priority of a policy compared to the others where 1 represents the highest priority. Thus, the smaller this value is, the higher preference this specific network will receive in establishing a data connection. </Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="Range">
<MSFT:Value>[1-2147483647]</MSFT:Value>
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>WirelessType</NodeName>
<DFProperties>
<AccessType>
<Add />
<Delete />
<Get />
<Replace />
</AccessType>
<DefaultValue>0</DefaultValue>
<Description>Type of wireless network (either Cellular or Wi-Fi). 0 represents Cellular, and 1 represents Wi-Fi. Currently only cellular is supported.</Description>
<DFFormat>
<bin />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="ENUM">
<MSFT:Enum>
<MSFT:Value>0</MSFT:Value>
<MSFT:ValueDescription>Cellular</MSFT:ValueDescription>
</MSFT:Enum>
<MSFT:Enum>
<MSFT:Value>1</MSFT:Value>
<MSFT:ValueDescription>Wi-Fi</MSFT:ValueDescription>
</MSFT:Enum>
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>Cellular</NodeName>
<DFProperties>
<AccessType>
<Add />
<Delete />
<Get />
</AccessType>
<Description>Identifiers for cellular networks.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<ZeroOrOne />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<DDFName />
</DFType>
</DFProperties>
<Node>
<NodeName>PLMNID</NodeName>
<DFProperties>
<AccessType>
<Add />
<Delete />
<Get />
<Replace />
</AccessType>
<Description>5- or 6-digit string identifying a cellular network. It consists of the combination of Mobile Country Code (MCC) and Mobile Network Code (MNC). </Description>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:AllowedValues ValueType="RegEx">
<MSFT:Value>^[0-9]{5,6}$</MSFT:Value>
</MSFT:AllowedValues>
</DFProperties>
</Node>
</Node>
</Node>
</Node>
</Node>
</MgmtTree>
```
## Related articles
[WirelessNetworkPreference configuration service provider reference](wirelessnetworkpreference-csp.md)

View File

@ -4,7 +4,7 @@ metadata:
description: Answers to frequently asked questions about Windows Autopatch. description: Answers to frequently asked questions about Windows Autopatch.
ms.service: windows-client ms.service: windows-client
ms.topic: faq ms.topic: faq
ms.date: 04/11/2025 ms.date: 04/21/2025
audience: itpro audience: itpro
ms.localizationpriority: medium ms.localizationpriority: medium
manager: aaroncz manager: aaroncz
@ -97,6 +97,18 @@ sections:
- question: Can I configure when to move to the next ring or is it controlled by Windows Autopatch? - question: Can I configure when to move to the next ring or is it controlled by Windows Autopatch?
answer: | answer: |
You're in full control over when updates are deployed to their devices. Autopatch groups will recommend a set of intelligent defaults but those are fully customizable so that you can achieve your desired rollout. You're in full control over when updates are deployed to their devices. Autopatch groups will recommend a set of intelligent defaults but those are fully customizable so that you can achieve your desired rollout.
- question: What is the expected behavior for turning on the Feature Update option for Autopatch groups?
answer: |
Starting in April 2025, default policies aren't created for new Autopatch customers. Existing customers will continue to receive support until Windows 10 reaches its End-of-Service (EOS). However, these policies won't transition to Windows 11.
If you created an Autopatch group before April 2025:
- The Feature Update option is unselected by default.
- Selecting the Feature Update option creates a feature update policy for the newly created Autopatch group. This doesn't affect the Global DSS policy.
- The Feature Update option doesn't affect existing releases created before April 2025; these releases remain unchanged
If you created an Autopatch group after April 2025:
- Selecting the Feature Update option creates a feature update policy and assigns it to all its deployment rings.
- Global DSS policy isn't affected.
- name: Hotpatch updates - name: Hotpatch updates
questions: questions:
- question: What are the licensing requirements for hotpatch updates? - question: What are the licensing requirements for hotpatch updates?

View File

@ -1,5 +1,5 @@
--- ---
ms.date: 02/25/2025 ms.date: 04/22/2025
title: Considerations and known issues when using Credential Guard title: Considerations and known issues when using Credential Guard
description: Considerations, recommendations, and known issues when using Credential Guard. description: Considerations, recommendations, and known issues when using Credential Guard.
ms.topic: troubleshooting ms.topic: troubleshooting
@ -112,6 +112,12 @@ When data protected with user DPAPI is unusable, then the user loses access to a
**Workaround:** Users can resolve the problem by connecting their device to the domain and rebooting or using their Encrypting File System Data Recovery Agent certificate. For more information about Encrypting File System Data Recovery Agent certificate, see [Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate](/previous-versions/windows/it-pro/windows-10/security/information-protection/windows-information-protection/create-and-verify-an-efs-dra-certificate). **Workaround:** Users can resolve the problem by connecting their device to the domain and rebooting or using their Encrypting File System Data Recovery Agent certificate. For more information about Encrypting File System Data Recovery Agent certificate, see [Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate](/previous-versions/windows/it-pro/windows-10/security/information-protection/windows-information-protection/create-and-verify-an-efs-dra-certificate).
### Azure Virtual Machines lose access to the data protected by Credential Guard after deallocation
When an Azure Virtual Machine is deallocated, the underlying hardware is released, causing the keys protected by the TPM to become inaccessible. Consequently, any data protected by those keys also becomes inaccessible.
For more information, see [States and billing status of Azure Virtual Machines](/azure/virtual-machines/states-billing#power-states-and-billing).
## Known issues ## Known issues
Credential Guard blocks certain authentication capabilities. Applications that require such capabilities won't function when Credential Guard is enabled. Credential Guard blocks certain authentication capabilities. Applications that require such capabilities won't function when Credential Guard is enabled.

View File

@ -15,3 +15,12 @@ The default value is 0.
|--|--| |--|--|
| **CSP** | `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[devicetenantidpoliciespincomplexityexpiration](/windows/client-management/mdm/passportforwork-csp#devicetenantidpoliciespincomplexityexpiration)<br><br>`./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[usertenantidpoliciespincomplexityexpiration](/windows/client-management/mdm/passportforwork-csp#usertenantidpoliciespincomplexityexpiration) | | **CSP** | `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[devicetenantidpoliciespincomplexityexpiration](/windows/client-management/mdm/passportforwork-csp#devicetenantidpoliciespincomplexityexpiration)<br><br>`./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[usertenantidpoliciespincomplexityexpiration](/windows/client-management/mdm/passportforwork-csp#usertenantidpoliciespincomplexityexpiration) |
| **GPO** | **Computer Configuration** > **Administrative Templates** > **System** > **PIN Complexity**| | **GPO** | **Computer Configuration** > **Administrative Templates** > **System** > **PIN Complexity**|
> [!NOTE]
> Starting with Windows 11, version 23H2, Windows Hello uses Virtualization-based security (VBS) to isolate credentials on devices that support [Enhanced Security Settings (ESS)](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security).
>
> Starting with Windows 11, version 24H2, Windows Hello uses VBS to isolate credentials on all devices that have VBS enabled.
>
> On such devices, PIN expiration is not supported.

View File

@ -18,3 +18,10 @@ The default value is 0.
|--|--| |--|--|
| **CSP** | `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[devicetenantidpoliciespincomplexityhistory](/windows/client-management/mdm/passportforwork-csp#devicetenantidpoliciespincomplexityhistory)<br><br>`./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[usertenantidpoliciespincomplexityhistory](/windows/client-management/mdm/passportforwork-csp#usertenantidpoliciespincomplexityhistory) | | **CSP** | `./Device/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[devicetenantidpoliciespincomplexityhistory](/windows/client-management/mdm/passportforwork-csp#devicetenantidpoliciespincomplexityhistory)<br><br>`./User/Vendor/MSFT/PassportForWork/{TenantId}/Policies/PINComplexity/`[usertenantidpoliciespincomplexityhistory](/windows/client-management/mdm/passportforwork-csp#usertenantidpoliciespincomplexityhistory) |
| **GPO** | **Computer Configuration** > **Administrative Templates** > **System** > **PIN Complexity** | | **GPO** | **Computer Configuration** > **Administrative Templates** > **System** > **PIN Complexity** |
> [!NOTE]
> Starting with Windows 11, version 23H2, Windows Hello uses Virtualization-based security (VBS) to isolate credentials on devices that support [Enhanced Security Settings (ESS)](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security).
>
> Starting with Windows 11, version 24H2, Windows Hello uses VBS to isolate credentials on all devices that have VBS enabled.
>
> On such devices, PIN history is not supported.