deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

games handwriting humanpresence

Browse Source
This commit is contained in:
Liz Long 2023-01-02 13:17:49 -05:00
parent 192c548ef5
commit 3f303ce6b0
3 changed files with 349 additions and 300 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

109
windows/client-management/mdm/policy-csp-games.md
View File

@ -1,77 +1,80 @@
--- ---
title: Policy CSP - Games title: Games Policy CSP
description: Learn to use the Policy CSP - Games setting so that you can specify whether advanced gaming services can be used. description: Learn more about the Games Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.topic: article ms.date: 01/02/2023
ms.localizationpriority: medium
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.localizationpriority: medium
ms.date: 09/27/2019
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- Games-Begin -->
# Policy CSP - Games # Policy CSP - Games
<hr/> <!-- Games-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Games-Editable-End -->
<!--Policies--> <!-- AllowAdvancedGamingServices-Begin -->
## Games policies ## AllowAdvancedGamingServices
<dl> <!-- AllowAdvancedGamingServices-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#games-allowadvancedgamingservices">Games/AllowAdvancedGamingServices</a> |:--|:--|:--|
</dd> | :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1703 [10.0.15063] and later |
</dl> <!-- AllowAdvancedGamingServices-Applicability-End -->
<hr/> <!-- AllowAdvancedGamingServices-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/Games/AllowAdvancedGamingServices
```
<!-- AllowAdvancedGamingServices-OmaUri-End -->
<!--Policy--> <!-- AllowAdvancedGamingServices-Description-Begin -->
<a href="" id="games-allowadvancedgamingservices"></a>**Games/AllowAdvancedGamingServices** <!-- Description-Source-DDF -->
Specifies whether advanced gaming services can be used. These services may send data to Microsoft or publishers of games that use these services.
<!-- AllowAdvancedGamingServices-Description-End -->
<!--SupportedSKUs--> <!-- AllowAdvancedGamingServices-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- AllowAdvancedGamingServices-Editable-End -->
|Edition|Windows 10|Windows 11| <!-- AllowAdvancedGamingServices-DFProperties-Begin -->
|--- |--- |--- | **Description framework properties**:
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> | Property name | Property value |
<hr/> |:--|:--|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 1 |
<!-- AllowAdvancedGamingServices-DFProperties-End -->
<!--Scope--> <!-- AllowAdvancedGamingServices-AllowedValues-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): **Allowed values**:
> [!div class = "checklist"] | Value | Description |
> * Device |:--|:--|
| 0 | Not allowed. |
| 1 (Default) | Allowed. |
<!-- AllowAdvancedGamingServices-AllowedValues-End -->
<hr/> <!-- AllowAdvancedGamingServices-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- AllowAdvancedGamingServices-Examples-End -->
<!--/Scope--> <!-- AllowAdvancedGamingServices-End -->
<!--Description-->
Added in Windows 10, version 1709. Specifies whether advanced gaming services can be used. These services may send data to Microsoft or publishers of games that use these services.
Supported value type is integer. <!-- Games-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- Games-CspMoreInfo-End -->
<!--/Description--> <!-- Games-End -->
<!--SupportedValues-->
The following list shows the supported values:
- 0 - Not Allowed ## Related articles
- 1 (default) - Allowed
<!--/SupportedValues-->
<!--/Policy-->
<hr/>
<!--/Policies-->
## Related topics
[Policy configuration service provider](policy-configuration-service-provider.md) [Policy configuration service provider](policy-configuration-service-provider.md)

131
windows/client-management/mdm/policy-csp-handwriting.md
View File

@ -1,89 +1,94 @@
--- ---
title: Policy CSP - Handwriting title: Handwriting Policy CSP
description: Use the Policy CSP - Handwriting setting to allow an enterprise to configure the default mode for the handwriting panel. description: Learn more about the Handwriting Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.topic: article ms.date: 01/02/2023
ms.localizationpriority: medium
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.localizationpriority: medium
ms.date: 09/27/2019
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- Handwriting-Begin -->
# Policy CSP - Handwriting # Policy CSP - Handwriting
<hr/> <!-- Handwriting-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Handwriting-Editable-End -->
<!--Policies--> <!-- PanelDefaultModeDocked-Begin -->
## Handwriting policies ## PanelDefaultModeDocked
<dl> <!-- PanelDefaultModeDocked-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#handwriting-paneldefaultmodedocked">Handwriting/PanelDefaultModeDocked</a> |:--|:--|:--|
</dd> | :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 1709 [10.0.16299] and later |
</dl> <!-- PanelDefaultModeDocked-Applicability-End -->
<hr/> <!-- PanelDefaultModeDocked-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/Handwriting/PanelDefaultModeDocked
```
<!-- PanelDefaultModeDocked-OmaUri-End -->
<!--Policy--> <!-- PanelDefaultModeDocked-Description-Begin -->
<a href="" id="handwriting-paneldefaultmodedocked"></a>**Handwriting/PanelDefaultModeDocked** <!-- Description-Source-ADMX -->
The handwriting panel has 2 modes - floats near the text box, or, attached to the bottom of the screen. Default is floating near text box. If you want the panel to be fixed, use this policy to fix it to the bottom.
<!-- PanelDefaultModeDocked-Description-End -->
<!--SupportedSKUs--> <!-- PanelDefaultModeDocked-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- PanelDefaultModeDocked-Editable-End -->
|Edition|Windows 10|Windows 11| <!-- PanelDefaultModeDocked-DFProperties-Begin -->
|--- |--- |--- | **Description framework properties**:
|Home|No|No|
|Pro|No|No|
|Windows SE|No|No|
|Business|No|No|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> | Property name | Property value |
<hr/> |:--|:--|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- PanelDefaultModeDocked-DFProperties-End -->
<!--Scope--> <!-- PanelDefaultModeDocked-AllowedValues-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): **Allowed values**:
> [!div class = "checklist"] | Value | Description |
> * Device |:--|:--|
| 0 (Default) | Disabled. |
| 1 | Enabled. |
<!-- PanelDefaultModeDocked-AllowedValues-End -->
<hr/> <!-- PanelDefaultModeDocked-GpMapping-Begin -->
**Group policy mapping**:
<!--/Scope--> | Name | Value |
<!--Description--> |:--|:--|
This policy allows an enterprise to configure the default mode for the handwriting panel. | Name | PanelDefaultModeDocked |
| Friendly Name | Handwriting Panel Default Mode Docked |
| Location | Computer Configuration |
| Path | Windows Components > Handwriting |
| Registry Key Name | Software\Policies\Microsoft\Handwriting |
| Registry Value Name | PanelDefaultModeDocked |
| ADMX File Name | Handwriting.admx |
<!-- PanelDefaultModeDocked-GpMapping-End -->
The handwriting panel has two modes - floats near the text box, or docked to the bottom of the screen. The default configuration is the one floating near text box. If you want the panel to be fixed or docked, use this policy to fix it to the bottom of the screen. <!-- PanelDefaultModeDocked-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- PanelDefaultModeDocked-Examples-End -->
In floating mode, the content is hidden behind a flying-in panel and results in end-user dissatisfaction. The end-user will need to drag the flying-in panel, to see the rest of the content. In the fixed mode, the flying-in panel is fixed to the bottom of the screen and doesn't require any user interaction. <!-- PanelDefaultModeDocked-End -->
The docked mode is especially useful in Kiosk mode, where you don't expect the end-user to drag the flying-in panel out of the way. <!-- Handwriting-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- Handwriting-CspMoreInfo-End -->
<!--/Description--> <!-- Handwriting-End -->
<!--ADMXMapped-->
ADMX Info:
- GP Friendly name: *Handwriting Panel Default Mode Docked*
- GP name: *PanelDefaultModeDocked*
- GP path: *Windows Components/Handwriting*
- GP ADMX file name: *Handwriting.admx*
<!--/ADMXMapped--> ## Related articles
<!--SupportedValues-->
The following list shows the supported values:
- 0 (default) - Disabled.
- 1 - Enabled.
<!--/SupportedValues-->
<!--/Policy-->
<hr/>
<!--/Policies-->
## Related topics
[Policy configuration service provider](policy-configuration-service-provider.md) [Policy configuration service provider](policy-configuration-service-provider.md)

403
windows/client-management/mdm/policy-csp-humanpresence.md
View File

@ -1,246 +1,287 @@
--- ---
title: Policy CSP - HumanPresence potitle: HumanPresence Policy CSP
description: Use the Policy CSP - HumanPresence setting allows wake on approach and lock on leave that can be managed from MDM. description: Learn more about the HumanPresence Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.topic: article ms.date: 01/02/2023
ms.localizationpriority: medium
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.localizationpriority: medium
ms.date: 09/27/2019
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- HumanPresence-Begin -->
# Policy CSP - HumanPresence # Policy CSP - HumanPresence
<hr/> <!-- HumanPresence-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- HumanPresence-Editable-End -->
<!--Policies--> <!-- ForceInstantDim-Begin -->
## HumanPresence policies ## ForceInstantDim
<dl> <!-- ForceInstantDim-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#humanpresence-forceinstantdim">HumanPresence/ForceInstantDim</a> |:--|:--|:--|
</dd> | :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :x: Windows SE | :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<dd> <!-- ForceInstantDim-Applicability-End -->
<a href="#humanpresence-forceinstantlock">HumanPresence/ForceInstantLock</a>
</dd>
<dd>
<a href="#humanpresence-forceinstantwake">HumanPresence/ForceInstantWake</a>
</dd>
<dd>
<a href="#humanpresence-forcelocktimeout">HumanPresence/ForceLockTimeout</a>
</dd>
</dl>
<hr/> <!-- ForceInstantDim-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/HumanPresence/ForceInstantDim
```
<!-- ForceInstantDim-OmaUri-End -->
<!--Policy--> <!-- ForceInstantDim-Description-Begin -->
<a href="" id="humanpresence-forceinstantdim"></a>**HumanPresence/ForceInstantDim** <!-- Description-Source-ADMX -->
Determines whether Attention Based Display Dimming is forced on/off by the MDM policy. The user will not be able to change this setting and the toggle in the UI will be greyed out.
<!-- ForceInstantDim-Description-End -->
<!--SupportedSKUs--> <!-- ForceInstantDim-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
This is a power saving feature that prolongs battery charge.
<!-- ForceInstantDim-Editable-End -->
|Edition|Windows 10|Windows 11| <!-- ForceInstantDim-DFProperties-Begin -->
|--- |--- |--- | **Description framework properties**:
|Home|No|No|
|Pro|No|Yes|
|Business|No|No|
|Enterprise|No|Yes|
|Education|No|Yes|
<!--/SupportedSKUs--> | Property name | Property value |
<hr/> |:--|:--|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- ForceInstantDim-DFProperties-End -->
<!--Scope--> <!-- ForceInstantDim-AllowedValues-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): **Allowed values**:
> [!div class = "checklist"] | Value | Description |
> * Device |:--|:--|
| 2 | ForcedOff. |
| 1 | ForcedOn. |
| 0 (Default) | DefaultToUserChoice. |
<!-- ForceInstantDim-AllowedValues-End -->
<hr/> <!-- ForceInstantDim-GpMapping-Begin -->
**Group policy mapping**:
<!--/Scope--> | Name | Value |
<!--Description--> |:--|:--|
This feature dims the screen based on user attention. This is a power saving feature that prolongs battery charge. | Name | ForceInstantDim |
| Friendly Name | Force Instant Dim |
| Location | Computer Configuration |
| Path | Windows Components > Human Presence |
| Registry Key Name | Software\Policies\Microsoft\HumanPresence |
| ADMX File Name | Sensors.admx |
<!-- ForceInstantDim-GpMapping-End -->
<!--/Description--> <!-- ForceInstantDim-Examples-Begin -->
<!--ADMXMapped--> <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
ADMX Info: <!-- ForceInstantDim-Examples-End -->
- GP Friendly name: *Force Instant Dim*
- GP name: *ForceInstantDim*
- GP path: *Windows Components/Human Presence*
- GP ADMX file name: *Sensors.admx*
<!--/ADMXMapped--> <!-- ForceInstantDim-End -->
<!--SupportedValues-->
The following list shows the supported values:
- 2 = ForcedOff <!-- ForceInstantLock-Begin -->
- 1 = ForcedOn ## ForceInstantLock
- 0 = DefaultToUserChoice
- Defaults to 0.
<!--/SupportedValues--> <!-- ForceInstantLock-Applicability-Begin -->
<!--/Policy--> | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :x: Windows SE | :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- ForceInstantLock-Applicability-End -->
<hr/> <!-- ForceInstantLock-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/HumanPresence/ForceInstantLock
```
<!-- ForceInstantLock-OmaUri-End -->
<!--Policy--> <!-- ForceInstantLock-Description-Begin -->
<a href="" id="humanpresence-forceinstantlock"></a>**HumanPresence/ForceInstantLock** <!-- Description-Source-ADMX -->
Determines whether Lock on Leave is forced on/off by the MDM policy. The user will not be able to change this setting and the toggle in the UI will be greyed out.
<!-- ForceInstantLock-Description-End -->
<!--SupportedSKUs--> <!-- ForceInstantLock-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ForceInstantLock-Editable-End -->
|Edition|Windows 10|Windows 11| <!-- ForceInstantLock-DFProperties-Begin -->
|--- |--- |--- | **Description framework properties**:
|Home|No|No|
|Pro|No|No|
|Windows SE|No|No|
|Business|No|No|
|Enterprise|No|Yes|
|Education|No|Yes|
<!--/SupportedSKUs--> | Property name | Property value |
<hr/> |:--|:--|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- ForceInstantLock-DFProperties-End -->
<!--Scope--> <!-- ForceInstantLock-AllowedValues-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): **Allowed values**:
> [!div class = "checklist"] | Value | Description |
> * Device |:--|:--|
| 2 | ForcedOff. |
| 1 | ForcedOn. |
| 0 (Default) | DefaultToUserChoice. |
<!-- ForceInstantLock-AllowedValues-End -->
<hr/> <!-- ForceInstantLock-GpMapping-Begin -->
**Group policy mapping**:
<!--/Scope--> | Name | Value |
<!--Description--> |:--|:--|
This policy specifies, whether the device can lock when a human presence sensor detects a human. | Name | ForceInstantLock |
| Friendly Name | Force Instant Lock |
| Location | Computer Configuration |
| Path | Windows Components > Human Presence |
| Registry Key Name | Software\Policies\Microsoft\HumanPresence |
| Registry Value Name | ForceInstantLock |
| ADMX File Name | Sensors.admx |
<!-- ForceInstantLock-GpMapping-End -->
<!--/Description--> <!-- ForceInstantLock-Examples-Begin -->
<!--ADMXMapped--> <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
ADMX Info: <!-- ForceInstantLock-Examples-End -->
- GP Friendly name: *Implements wake on approach and lock on leave that can be managed from MDM*
- GP name: *ForceInstantLock*
- GP path: *Windows Components/HumanPresence*
- GP ADMX file name: *HumanPresence.admx*
<!--/ADMXMapped--> <!-- ForceInstantLock-End -->
<!--SupportedValues-->
The following list shows the supported values:
- 2 = ForcedOff <!-- ForceInstantWake-Begin -->
- 1 = ForcedOn ## ForceInstantWake
- 0 = DefaultToUserChoice
- Defaults to 0
<!--/SupportedValues--> <!-- ForceInstantWake-Applicability-Begin -->
<!--/Policy--> | Scope | Editions | Applicable OS |
<hr/> |:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :x: Windows SE | :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- ForceInstantWake-Applicability-End -->
<!--Policy--> <!-- ForceInstantWake-OmaUri-Begin -->
<a href="" id="humanpresence-forceinstantwake"></a>**HumanPresence/ForceInstantWake** ```Device
./Device/Vendor/MSFT/Policy/Config/HumanPresence/ForceInstantWake
```
<!-- ForceInstantWake-OmaUri-End -->
<!--SupportedSKUs--> <!-- ForceInstantWake-Description-Begin -->
<!-- Description-Source-ADMX -->
Determines whether Wake On Arrival is forced on/off by the MDM policy. The user will not be able to change this setting and the toggle in the UI will be greyed out.
<!-- ForceInstantWake-Description-End -->
|Edition|Windows 10|Windows 11| <!-- ForceInstantWake-Editable-Begin -->
|--- |--- |--- | <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
|Home|No|No| <!-- ForceInstantWake-Editable-End -->
|Pro|No|No|
|Windows SE|No|No|
|Business|No|No|
|Enterprise|No|Yes|
|Education|No|Yes|
<!--/SupportedSKUs--> <!-- ForceInstantWake-DFProperties-Begin -->
<hr/> **Description framework properties**:
<!--Scope--> | Property name | Property value |
[Scope](./policy-configuration-service-provider.md#policy-scope): |:--|:--|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- ForceInstantWake-DFProperties-End -->
> [!div class = "checklist"] <!-- ForceInstantWake-AllowedValues-Begin -->
> * Device **Allowed values**:
<hr/> | Value | Description |
|:--|:--|
| 2 | ForcedOff. |
| 1 | ForcedOn. |
| 0 (Default) | DefaultToUserChoice. |
<!-- ForceInstantWake-AllowedValues-End -->
<!--/Scope--> <!-- ForceInstantWake-GpMapping-Begin -->
<!--Description--> **Group policy mapping**:
This policy specifies, whether the device can lock when a human presence sensor detects a human.
<!--/Description--> | Name | Value |
<!--ADMXMapped--> |:--|:--|
ADMX Info: | Name | ForceInstantWake |
- GP Friendly name: *Implements wake on approach and lock on leave that can be managed from MDM* | Friendly Name | Force Instant Wake |
- GP name: *ForceInstantWake* | Location | Computer Configuration |
- GP path: *Windows Components/HumanPresence* | Path | Windows Components > Human Presence |
- GP ADMX file name: *HumanPresence.admx* | Registry Key Name | Software\Policies\Microsoft\HumanPresence |
| Registry Value Name | ForceInstantWake |
| ADMX File Name | Sensors.admx |
<!-- ForceInstantWake-GpMapping-End -->
<!--/ADMXMapped--> <!-- ForceInstantWake-Examples-Begin -->
<!--SupportedValues--> <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
The following list shows the supported values: <!-- ForceInstantWake-Examples-End -->
- 2 = ForcedOff <!-- ForceInstantWake-End -->
- 1 = ForcedOn
- 0 = DefaultToUserChoice
- Defaults to 0
<!--/SupportedValues--> <!-- ForceLockTimeout-Begin -->
<!--/Policy--> ## ForceLockTimeout
<hr/>
<!--Policy--> <!-- ForceLockTimeout-Applicability-Begin -->
<a href="" id="humanpresence-forcelocktimeout"></a>**HumanPresence/ForceLockTimeout** | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :x: Windows SE | :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- ForceLockTimeout-Applicability-End -->
<!--SupportedSKUs--> <!-- ForceLockTimeout-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/HumanPresence/ForceLockTimeout
```
<!-- ForceLockTimeout-OmaUri-End -->
|Edition|Windows 10|Windows 11| <!-- ForceLockTimeout-Description-Begin -->
|--- |--- |--- | <!-- Description-Source-ADMX -->
|Home|No|No| Determines the timeout for Lock on Leave forced by the MDM policy. The user will be unable to change this setting and the toggle in the UI will be greyed out.
|Pro|No|No| <!-- ForceLockTimeout-Description-End -->
|Windows SE|No|No|
|Business|No|No|
|Enterprise|No|Yes|
|Education|No|Yes|
<!--/SupportedSKUs--> <!-- ForceLockTimeout-Editable-Begin -->
<hr/> <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ForceLockTimeout-Editable-End -->
<!--Scope--> <!-- ForceLockTimeout-DFProperties-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): **Description framework properties**:
> [!div class = "checklist"] | Property name | Property value |
> * Device |:--|:--|
| Format | int |
| Access Type | Add, Delete, Get, Replace |
| Default Value | 0 |
<!-- ForceLockTimeout-DFProperties-End -->
<hr/> <!-- ForceLockTimeout-AllowedValues-Begin -->
**Allowed values**:
<!--/Scope--> | Value | Description |
<!--Description--> |:--|:--|
This policy specifies, at what distance the sensor wakes up when it sees a human in seconds. | 120 | TwoMinutes |
| 30 | ThirtySeconds. |
| 10 | TenSeconds. |
| 0 (Default) | DefaultToUserChoice. |
<!-- ForceLockTimeout-AllowedValues-End -->
<!--/Description--> <!-- ForceLockTimeout-GpMapping-Begin -->
<!--ADMXMapped--> **Group policy mapping**:
ADMX Info:
- GP Friendly name: *Implements wake on approach and lock on leave that can be managed from MDM*
- GP name: *ForceLockTimeout*
- GP path: *Windows Components/HumanPresence*
- GP ADMX file name: *HumanPresence.admx*
<!--/ADMXMapped--> | Name | Value |
<!--SupportedValues--> |:--|:--|
Integer value that specifies, whether the device can lock when a human presence sensor detects a human. | Name | ForceLockTimeout |
| Friendly Name | Lock Timeout |
| Location | Computer Configuration |
| Path | Windows Components > Human Presence |
| Registry Key Name | Software\Policies\Microsoft\HumanPresence |
| ADMX File Name | Sensors.admx |
<!-- ForceLockTimeout-GpMapping-End -->
The following list shows the supported values: <!-- ForceLockTimeout-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- ForceLockTimeout-Examples-End -->
- 120 = 120 seconds <!-- ForceLockTimeout-End -->
- 30 = 30 seconds
- 10 = 10 seconds
- 0 = DefaultToUserChoice
- Defaults to 0
<!--/SupportedValues--> <!-- HumanPresence-CspMoreInfo-Begin -->
<!--/Policy--> <!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<hr/> <!-- HumanPresence-CspMoreInfo-End -->
<!--/Policies--> <!-- HumanPresence-End -->
## Related topics ## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md) [Policy configuration service provider](policy-configuration-service-provider.md)