mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Update dates in documentation files
This commit is contained in:
parent
8690f4a539
commit
24c440ff8d
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Take tests and assessments in Windows
|
title: Take tests and assessments in Windows
|
||||||
description: Learn about the built-in Take a Test app for Windows and how to use it.
|
description: Learn about the built-in Take a Test app for Windows and how to use it.
|
||||||
ms.date: 03/31/2023
|
ms.date: 02/29/2024
|
||||||
ms.topic: how-to
|
ms.topic: how-to
|
||||||
---
|
---
|
||||||
|
|
||||||
|
@ -11,7 +11,7 @@ ms.date: 02/29/2024
|
|||||||
|
|
||||||
<!-- AssignedAccess-Editable-Begin -->
|
<!-- AssignedAccess-Editable-Begin -->
|
||||||
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
|
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
|
||||||
The AssignedAccess configuration service provider (CSP) is used to configure a kiosk or restricted user experience. Once the CSP is executed, the next user login that is associated with the kiosk profile puts the device into the kiosk mode specified in the CSP configuration.
|
The AssignedAccess configuration service provider (CSP) is used to configure a kiosk or restricted user experience. Once the CSP is executed, the next user login that is associated with the Assigned Access profile puts the device into the kiosk mode specified in the CSP configuration.
|
||||||
|
|
||||||
To learn more about how to configure Assigned Access, see [Configure kiosks and restricted user experiences](/windows/configuration/assigned-access).
|
To learn more about how to configure Assigned Access, see [Configure kiosks and restricted user experiences](/windows/configuration/assigned-access).
|
||||||
<!-- AssignedAccess-Editable-End -->
|
<!-- AssignedAccess-Editable-End -->
|
||||||
@ -829,7 +829,7 @@ This example configures the following apps: Skype, Learning, Feedback Hub, and C
|
|||||||
|
|
||||||
XML encoding (escaped) and CDATA of the XML in the Data node will both ensure that DM client can properly interpret the SyncML and send the configuration xml as string (in original format, unescaped) to AssignedAccess CSP to handle.
|
XML encoding (escaped) and CDATA of the XML in the Data node will both ensure that DM client can properly interpret the SyncML and send the configuration xml as string (in original format, unescaped) to AssignedAccess CSP to handle.
|
||||||
|
|
||||||
Similarly, the StartLayout xml inside the configuration xml is using the same format, xml inside xml as string. In the sample Configuration xml provided above, CDATA is used to embed the StartLayout xml. If you use CDATA to embed configuration xml in SyncML as well, you'll have nested CDATA, so pay attention to how CDATA is used in the provided CDATA sample. With that being said, when the Configuration xml is being constructed, MDM server can either escape start layout xml or put startlayout xml inside CDATA, when MDM server puts configuration xml inside SyncML, MDM server can also either escape it or wrap with CDATA.
|
Similarly, the StartLayout xml inside the configuration xml is using the same format, xml inside xml as string. In the sample Configuration xml provided above, CDATA is used to embed the StartLayout xml. If you use CDATA to embed configuration xml in SyncML as well, you have nested CDATA, so pay attention to how CDATA is used in the provided CDATA sample. With that being said, when the Configuration xml is being constructed, MDM server can either escape start layout xml or put startlayout xml inside CDATA, when MDM server puts configuration xml inside SyncML, MDM server can also either escape it or wrap with CDATA.
|
||||||
|
|
||||||
Escape and CDATA are mechanisms used when handling xml in xml. Consider that it's a transportation channel to send the configuration xml as payload from server to client. It's transparent to both, the end user who configures the CSP and to our CSP. Both the customer on the server side and our CSP must only see the original configuration XML.
|
Escape and CDATA are mechanisms used when handling xml in xml. Consider that it's a transportation channel to send the configuration xml as payload from server to client. It's transparent to both, the end user who configures the CSP and to our CSP. Both the customer on the server side and our CSP must only see the original configuration XML.
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Dynamic lock
|
title: Dynamic lock
|
||||||
description: Learn how to configure dynamic lock on Windows devices via group policies. This feature locks a device when a Bluetooth signal falls below a set value.
|
description: Learn how to configure dynamic lock on Windows devices via group policies. This feature locks a device when a Bluetooth signal falls below a set value.
|
||||||
ms.date: 03/10/2023
|
ms.date: 02/29/2024
|
||||||
ms.topic: how-to
|
ms.topic: how-to
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -16,7 +16,7 @@ You can configure Windows devices to use the **dynamic lock** using a Group Poli
|
|||||||
|
|
||||||
1. Using the Group Policy Management Console (GPMC), scope a domain-based Group Policy to computer accounts in Active Directory.
|
1. Using the Group Policy Management Console (GPMC), scope a domain-based Group Policy to computer accounts in Active Directory.
|
||||||
1. Edit the Group Policy object from Step 1.
|
1. Edit the Group Policy object from Step 1.
|
||||||
1. Enable the **Configure dynamic lock factors** policy setting located under **Computer Configuration > Administrative Templates > Windows Components > Windows Hello for Business**.
|
1. Enable the **Configure dynamic lock factors** policy setting located under **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Windows Hello for Business**.
|
||||||
1. Close the Group Policy Management Editor to save the Group Policy object.
|
1. Close the Group Policy Management Editor to save the Group Policy object.
|
||||||
|
|
||||||
The Group Policy Editor, when the policy is enabled, creates a default signal rule policy with the following value:
|
The Group Policy Editor, when the policy is enabled, creates a default signal rule policy with the following value:
|
||||||
@ -30,7 +30,7 @@ The Group Policy Editor, when the policy is enabled, creates a default signal ru
|
|||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
>Microsoft recommends using the default values for this policy settings. Measurements are relative based on the varying conditions of each environment. Therefore, the same values may produce different results. Test policy settings in each environment prior to broadly deploying the setting.
|
>Microsoft recommends using the default values for this policy settings. Measurements are relative based on the varying conditions of each environment. Therefore, the same values may produce different results. Test policy settings in each environment prior to broadly deploying the setting.
|
||||||
|
|
||||||
For this policy setting, the **type** and **scenario** attribute values are static and can't change. The **classofDevice** is configurable but Phone is the only currently supported configuration. The attribute defaults to Phone and uses the values from the following table:
|
For this policy setting, the `type` and `scenario` attribute values are static and can't change. The `classofDevice` is configurable but Phone is the only currently supported configuration. The attribute defaults to Phone and uses the values from the following table:
|
||||||
|
|
||||||
|Description|Value|
|
|Description|Value|
|
||||||
|:-------------|:-------:|
|
|:-------------|:-------:|
|
||||||
@ -46,6 +46,6 @@ For this policy setting, the **type** and **scenario** attribute values are stat
|
|||||||
|Health|2304|
|
|Health|2304|
|
||||||
|Uncategorized|7936|
|
|Uncategorized|7936|
|
||||||
|
|
||||||
The **rssiMin** attribute value signal indicates the strength needed for the device to be considered *in-range*. The default value of **-10** enables a user to move about an average size office or cubicle without triggering Windows to lock the device. The **rssiMaxDelta** has a default value of **-10**, which instruct Windows to lock the device once the signal strength weakens by more than measurement of 10.
|
The `rssiMin` attribute value signal indicates the strength needed for the device to be considered *in-range*. The default value of `-10` enables a user to move about an average size office or cubicle without triggering Windows to lock the device. The `rssiMaxDelta` has a default value of `-10`, which instruct Windows to lock the device once the signal strength weakens by more than measurement of 10.
|
||||||
|
|
||||||
RSSI measurements are relative and lower as the bluetooth signals between the two paired devices reduces. Therefore a measurement of 0 is stronger than -10, which is stronger than -60, which is an indicator the devices are moving further apart from each other.
|
RSSI measurements are relative and lower as the bluetooth signals between the two paired devices reduces. Therefore a measurement of 0 is stronger than -10, which is stronger than -60, which is an indicator the devices are moving further apart from each other.
|
||||||
|
@ -8,7 +8,7 @@ manager: aaroncz
|
|||||||
ms.collection:
|
ms.collection:
|
||||||
- tier2
|
- tier2
|
||||||
ms.topic: overview
|
ms.topic: overview
|
||||||
ms.date: 05/04/2023
|
ms.date: 02/29/2024
|
||||||
appliesto:
|
appliesto:
|
||||||
- ✅ <a href=/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
- ✅ <a href=/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||||
ms.service: windows-client
|
ms.service: windows-client
|
||||||
|
Loading…
x
Reference in New Issue
Block a user