mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge branch 'MicrosoftDocs:master' into patch-5
This commit is contained in:
Alice-at-Microsoft
GitHub
commit
bf2121e8a1
@ -12,12 +12,12 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
ms.date: 06/26/2017
|
||||
ms.date: 11/02/2021
|
||||
---
|
||||
|
||||
# Enterprise settings, policies, and app management
|
||||
|
||||
The actual management interaction between the device and server is done via the DM client. The DM client communicates with the enterprise management server via DM v1.2 SyncML syntax. The full description of the OMA DM protocol v1.2 can be found at the [OMA website](https://go.microsoft.com/fwlink/p/?LinkId=267526).
|
||||
The actual management interaction between the device and server is done via the DM client. The DM client communicates with the enterprise management server via DM v1.2 SyncML syntax. The full description of the OMA DM protocol v1.2 can be found at the [OMA website](https://www.openmobilealliance.org/release/DM/V1_2-20070209-A/OMA-TS-DM_Protocol-V1_2-20070209-A.pdf).
|
||||
|
||||
Windows currently supports one MDM server. The DM client that is configured via the enrollment process is granted access to enterprise related settings. Enterprise MDM settings are exposed via various configuration service providers to the DM client. For the list of available configuration service providers, see [Configuration service provider reference](configuration-service-provider-reference.md).
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: dansimp
|
||||
ms.date: 10/11/2021
|
||||
ms.date: 11/02/2021
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
@ -266,7 +266,7 @@ ADMX Info:
|
||||
<!--/ADMXMapped-->
|
||||
|
||||
<a href="" id="status"></a>**Status**
|
||||
Returns bitmask that indicates status of Application Guard installation and pre-requisites on the device.
|
||||
Returns bitmask that indicates status of Application Guard installation for Microsoft Edge and prerequisites on the device.
|
||||
|
||||
Value type is integer. Supported operation is Get.
|
||||
|
||||
@ -275,11 +275,13 @@ Value type is integer. Supported operation is Get.
|
||||
- Bit 2 - Set to 1 when the client machine has a valid OS license and SKU.
|
||||
- Bit 3 - Set to 1 when Application Guard installed on the client machine.
|
||||
- Bit 4 - Set to 1 when required Network Isolation Policies are configured.
|
||||
> [!IMPORTANT]
|
||||
> If you are deploying Application Guard via Intune, Network Isolation Policy must be configured to enable Application Guard for Microsoft Edge.
|
||||
- Bit 5 - Set to 1 when the client machine meets minimum hardware requirements.
|
||||
- Bit 6 - Set to 1 when system reboot is required.
|
||||
- Bit 6 - Set to 1 when system reboot is required.
|
||||
|
||||
<a href="" id="platformstatus"></a>**PlatformStatus**
|
||||
Added in Windows 10, version 2004. Returns bitmask that indicates status of Application Guard platform installation and prerequisites on the device.
|
||||
Added in Windows 10, version 2004. Applies to Microsoft Office/Generic platform. Returns bitmask that indicates status of Application Guard platform installation and prerequisites on the device.
|
||||
|
||||
Value type is integer. Supported operation is Get.
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/23/2021
|
||||
ms.date: 11/02/2021
|
||||
ms.reviewer:
|
||||
---
|
||||
|
||||
@ -389,7 +389,7 @@ The registry keys for the smart card KSP are in **HKEY\_LOCAL\_MACHINE\\SYSTEM\\
|
||||
| **AllowPrivateSignatureKeyImport** | A non-zero value allows RSA signature private keys to be imported for use in key archival scenarios.<br>Default value: 00000000 |
|
||||
| **DefaultPrivateKeyLenBits** | Defines the default length for private keys, if desired.<br>Default value: 00000400<br>Default key generation parameter: 1024-bit keys |
|
||||
| **RequireOnCardPrivateKeyGen** | This key sets the flag that requires on-card private key generation (default). If this value is set, a key generated on a host can be imported into the smart card. This is used for smart cards that don't support on-card key generation or where key escrow is required.<br>Default value: 00000000 |
|
||||
| **TransactionTimeoutMilliseconds** | Default timeout values allow you to specify whether transactions that take an excessive amount of time will fail.<br>Default value: 000005dc1500<br>The default timeout for holding transactions to the smart card is 1.5 seconds. |
|
||||
| **TransactionTimeoutMilliseconds** | Default timeout values allow you to specify whether transactions that take an excessive amount of time will fail.<br>Default value: 000005dc<br>The default timeout for holding transactions to the smart card is 1.5 seconds. |
|
||||
|
||||
**Additional registry keys for the smart card KSP**
|
||||
|
||||
|
||||
@ -42,7 +42,7 @@ Because Windows Sandbox runs the same operating system image as the host, it has
|
||||
|
||||
## Integrated kernel scheduler
|
||||
|
||||
With ordinary virtual machines, the Microsoft hypervisor controls the scheduling of the virtual processors running in the VMs. Windows Sandbox uses new technology called "integrated scheduling," which allows the host scheduler to decide when the sandbox gets CPU cycles.
|
||||
With ordinary virtual machines, the Microsoft hypervisor controls the scheduling of the virtual processors running in the VMs. Windows Sandbox uses a new technology called "integrated scheduling," which allows the host scheduler to decide when the sandbox gets CPU cycles.
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user