deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-22 05:43:41 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

older windows version cleanup

Browse Source
This commit is contained in:
Vinay Pamnani
2023-04-11 11:36:23 -04:00
parent 92ff1941e9
commit 00af39a152
23 changed files with 285 additions and 776 deletions
Download Patch File Download Diff File Expand all files Collapse all files

70
windows/client-management/win32-and-centennial-app-policy-configuration.md
View File

@ -1,13 +1,13 @@
---
title: Win32 and Desktop Bridge app ADMX policy Ingestion
description: Starting in Windows 10, version 1703, you can ingest ADMX files and set those ADMX policies for Win32 and Desktop Bridge apps.
description: Ingest ADMX files and set ADMX policies for Win32 and Desktop Bridge apps.
ms.author: vinpa
ms.topic: article
ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.date: 03/23/2020
ms.reviewer:
ms.reviewer:
manager: aaroncz
appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
@ -16,21 +16,12 @@ appliesto:
# Win32 and Desktop Bridge app ADMX policy Ingestion
## In this section
## Overview
- [Overview](#overview)
- [Ingesting an app ADMX file](#ingesting-an-app-admx-file)
- [URI format for configuring an app policy](#uri-format-for-configuring-an-app-policy)
- [ADMX app policy examples](#admx-backed-app-policy-examples)
- [Enabling an app policy](#enabling-an-app-policy)
- [Disabling an app policy](#disabling-an-app-policy)
- [Setting an app policy to not configured](#setting-an-app-policy-to-not-configured)
You can ingest ADMX files (ADMX ingestion) and set those ADMX policies for Win32 and Desktop Bridge apps by using Windows Mobile Device Management (MDM) on desktop SKUs. The ADMX files that define policy information can be ingested to your device by using the Policy CSP URI, `./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall`. The ingested ADMX file is then processed into MDM policies.
## <a href="" id="overview"></a>Overview
NOTE: Starting from the following Windows versions Replace command is supported:
Starting in Windows 10, version 1703, you can ingest ADMX files (ADMX ingestion) and set those ADMX policies for Win32 and Desktop Bridge apps by using Windows 10 Mobile Device Management (MDM) on desktop SKUs. The ADMX files that define policy information can be ingested to your device by using the Policy CSP URI, `./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall`. The ingested ADMX file is then processed into MDM policies.
NOTE: Starting from the following Windows 10 version Replace command is supported
- Windows 10, version 1903 with KB4512941 and KB4517211 installed
- Windows 10, version 1809 with KB4512534 and KB installed
- Windows 10, version 1803 with KB4512509 and KB installed
@ -66,11 +57,12 @@ When the ADMX policies are ingested, the registry keys to which each policy is w
> [!NOTE]
> Settings that cannot be configured using custom policy ingestion have to be set by pushing the appropriate registry keys directly (for example, by using PowerShell script).
## <a href="" id="ingesting-an-app-admx-file"></a>Ingesting an app ADMX file
## Ingesting an app ADMX file
The following ADMX file example shows how to ingest a Win32 or Desktop Bridge app ADMX file and set policies from the file. The ADMX file defines eight policies.
**Payload**
**Payload**:
```XML
<policyDefinitions revision="1.0" schemaVersion="1.0">
<categories>
@ -204,7 +196,7 @@ The following ADMX file example shows how to ingest a Win32 or Desktop Bridge ap
</policyDefinitions>
```
**Request Syncml**
**Request Syncml**:
The ADMX file is escaped and sent in SyncML format through the Policy CSP URI, `./Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/{AppName}/{SettingType}/{FileUid or AdmxFileName}`.
When the ADMX file is imported, the policy states for each new policy are the same as those in a regular MDM policy: Enabled, Disabled, or Not Configured.
@ -363,12 +355,13 @@ The following example shows an ADMX file in SyncML format:
</SyncML>
```
**Response Syncml**
**Response Syncml**:
```XML
<Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>102</CmdRef><Cmd>Add</Cmd><Data>200</Data></Status>
```
### <a href="" id="uri-format-for-configuring-an-app-policy"></a>URI format for configuring an app policy
### URI format for configuring an app policy
The following example shows how to derive a Win32 or Desktop Bridge app policy name and policy area name:
@ -397,10 +390,9 @@ The following example shows how to derive a Win32 or Desktop Bridge app policy n
</policy>
```
As documented in [Policy CSP](mdm/policy-configuration-service-provider.md), the URI format to configure a policy via Policy CSP is:
'./{user or device}/Vendor/MSFT/Policy/Config/{AreaName}/{PolicyName}'.
As documented in [Policy CSP](mdm/policy-configuration-service-provider.md), the URI format to configure a policy via Policy CSP is: `./{user or device}/Vendor/MSFT/Policy/Config/{AreaName}/{PolicyName}`.
**User or device policy**
**User or device policy**:
In the policy class, the attribute is defined as "User" and the URI is prefixed with `./user`.
If the attribute value is "Machine", the URI is prefixed with `./device`.
@ -418,20 +410,22 @@ Therefore, from the example:
- Policy area name: ContosoCompanyApp~Policy~ParentCategoryArea~Category2~Category3
- URI: `./user/Vendor/MSFT/Policy/Config/ContosoCompanyApp~Policy~ParentCategoryArea~Category2~Category3/L_PolicyPreventRun_1`
## <a href="" id="admx-backed-app-policy-examples"></a>ADMX-backed app policy examples
## ADMX-backed app policy examples
The following examples describe how to set an ADMX-ingested app policy.
### <a href="" id="enabling-an-app-policy"></a>Enabling an app policy
### Enabling an app policy
**Payload**:
**Payload**
```XML
<enabled/>
<data id="L_ServerAddressInternal_VALUE" value="TextValue1"/>
<data id="L_ServerAddressExternal_VALUE" value="TextValue2"/>
```
**Request Syncml**
**Request Syncml**:
```XML
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
@ -453,19 +447,22 @@ The following examples describe how to set an ADMX-ingested app policy.
</SyncML>
```
**Response SyncML**
**Response SyncML**:
```XML
<Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>103</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status>
```
### <a href="" id="disabling-an-app-policy"></a>Disabling an app policy
### Disabling an app policy
**Payload**:
**Payload**
```XML
<disabled/>
```
**Request SyncML**
**Request SyncML**:
```XML
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
@ -487,18 +484,20 @@ The following examples describe how to set an ADMX-ingested app policy.
</SyncML>
```
**Response SyncML**
**Response SyncML**:
```XML
<Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>104</CmdRef><Cmd>Replace</Cmd><Data>200</Data></Status>
```
### <a href="" id="setting-an-app-policy-to-not-configured"></a>Setting an app policy to not configured
### Setting an app policy to not configured
**Payload**
**Payload**:
(None)
**Request SyncML**
**Request SyncML**:
```XML
<SyncML xmlns="SYNCML:SYNCML1.1">
<SyncBody>
@ -515,7 +514,8 @@ The following examples describe how to set an ADMX-ingested app policy.
</SyncML>
```
**Response SyncML**
**Response SyncML**:
```XML
<Status><CmdID>2</CmdID><MsgRef>1</MsgRef><CmdRef>105</CmdRef><Cmd>Delete</Cmd><Data>200</Data></Status>
```