mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-20 17:27:23 +00:00
Merge remote-tracking branch 'refs/remotes/origin/jd3cbb' into rs3
This commit is contained in:
jdeckerMS
commit
ea6afa369a
@ -37,7 +37,7 @@ You can also configure Surface Hub to receive updates from both Windows Update f
|
||||
|
||||
## Surface Hub servicing model
|
||||
|
||||
Surface Hub uses the Windows 10 servicing model, referred to as Windows as a Service (WaaS). Traditionally, new features are added only in new versions of Windows that are released every few years. Each new version required lengthy and expensive processes to deploy in an organization. As a result, end users and organizations don't frequently enjoy the benefits of new innovation. The goal of Windows as a Service is to continually provide new capabilities while maintaining a high level of quality.
|
||||
Surface Hub uses the Windows 10 servicing model, referred to as [Windows as a Service (WaaS)](https://docs.microsoft.com/windows/deployment/update/waas-overview). Traditionally, new features are added only in new versions of Windows that are released every few years. Each new version required lengthy and expensive processes to deploy in an organization. As a result, end users and organizations don't frequently enjoy the benefits of new innovation. The goal of Windows as a Service is to continually provide new capabilities while maintaining a high level of quality.
|
||||
|
||||
Microsoft publishes two types of Surface Hub releases broadly on an ongoing basis:
|
||||
- **Feature updates** - Updates that install the latest new features, experiences, and capabilities. Microsoft expects to publish an average of two to three new feature upgrades per year.
|
||||
@ -45,7 +45,7 @@ Microsoft publishes two types of Surface Hub releases broadly on an ongoing basi
|
||||
|
||||
In order to improve release quality and simplify deployments, all new releases that Microsoft publishes for Windows 10, including Surface Hub, will be cumulative. This means new feature updates and quality updates will contain the payloads of all previous releases (in an optimized form to reduce storage and networking requirements), and installing the release on a device will bring it completely up to date. Also, unlike earlier versions of Windows, you cannot install a subset of the contents of a Windows 10 quality update. For example, if a quality update contains fixes for three security vulnerabilities and one reliability issue, deploying the update will result in the installation of all four fixes.
|
||||
|
||||
The Surface Hub operating system is available on **Current Branch (CB)** and **Current Branch for Business (CBB)**. Like other editions of Windows 10, the servicing lifetime of CB or CBB is finite. You must install new feature updates on machines running these branches in order to continue receiving quality updates.
|
||||
The Surface Hub operating system receives updates on the [Semi-Annual Channel](https://docs.microsoft.com/windows/deployment/update/waas-overview#naming-changes). Like other editions of Windows 10, the servicing lifetime ois finite. You must install new feature updates on machines running these branches in order to continue receiving quality updates.
|
||||
|
||||
For more information on Windows as a Service, see [Overview of Windows as a service](https://technet.microsoft.com/itpro/windows/manage/waas-overview).
|
||||
|
||||
@ -55,11 +55,9 @@ Surface Hubs, like all Windows 10 devices, include **Windows Update for Business
|
||||
|
||||
**To set up Windows Update for Business:**
|
||||
1. [Group Surface Hub into deployment rings](#group-surface-hub-into-deployment-rings)
|
||||
2. [Configure Surface Hub to use Current Branch or Current Branch for Business](#configure-surface-hub-to-use-current-branch-or-current-branch-for-business).
|
||||
2. [Configure when Surface Hub receives updates](#configure-when-surface-hub-receives-updates).
|
||||
|
||||
> [!NOTE]
|
||||
|
||||
> You can use Microsoft Intune, System Center Configuration Manager, or a supported third-party MDM provider to set up WUfB. [Walkthrough: use Microsoft Intune to configure Windows Update for Business.](https://technet.microsoft.com/itpro/windows/manage/waas-wufb-intune)
|
||||
|
||||
|
||||
@ -70,29 +68,22 @@ This table gives examples of deployment rings.
|
||||
|
||||
| Deployment ring | Ring size | Servicing branch | Deferral for feature updates | Deferral for quality updates (security fixes, drivers, and other updates) | Validation step |
|
||||
| --------- | --------- | --------- | --------- | --------- | --------- |
|
||||
| Preview (e.g. non-critical or test devices) | Small | Current Branch (CB) | None. Devices receive feature updates immediately after CB is released. | None. Devices receive quality updates immediately after CB is released. | Manually test and evaluate new functionality. Pause updates if there are issues. |
|
||||
| Release (e.g. devices used by select teams) | Medium | Current Branch for Business (CBB) | None. Devices receive feature updates immediately once CBB is released. | None. Devices receive quality updates immediately after CBB is released. | Monitor device usage and user feedback. Pause updates if there are issues. |
|
||||
| Broad deployment (e.g. most of the devices in your organization) | Large | Current Branch for Business (CBB) | 120 days after CBB is released. | 7-14 days after CBB is released. | Monitor device usage and user feedback. Pause updates if there are issues. |
|
||||
| Mission critical (e.g. devices in executive boardrooms) | Small | Current Branch for Business (CBB) | 180 days after CBB is released (maximum deferral for feature updates). | 30 days after CBB is released (maximum deferral for quality updates). | Monitor device usage and user feedback. |
|
||||
| Preview (e.g. non-critical or test devices) | Small | Semi-annual channel (Targeted) | None. | None. | Manually test and evaluate new functionality. Pause updates if there are issues. |
|
||||
| Release (e.g. devices used by select teams) | Medium | Semi-annual channel | None. | None. | Monitor device usage and user feedback. Pause updates if there are issues. |
|
||||
| Broad deployment (e.g. most of the devices in your organization) | Large | Semi-annual channel | 120 days after release. | 7-14 days after release. | Monitor device usage and user feedback. Pause updates if there are issues. |
|
||||
| Mission critical (e.g. devices in executive boardrooms) | Small | Semi-annual channel | 180 days after release (maximum deferral for feature updates). | 30 days after release (maximum deferral for quality updates). | Monitor device usage and user feedback. |
|
||||
|
||||
|
||||
### Configure Surface Hub to use Current Branch or Current Branch for Business
|
||||
By default, Surface Hubs are configured to receive updates from Current Branch (CB). CB receives feature updates as soon as they are released by Microsoft. Current Branch for Business (CBB), on the other hand, receives feature updates at least four months after they have been initially offered to CB devices, and includes all of the quality updates that have been released in the interim. For more information on the differences between CB and CBB, see [Servicing branches](https://technet.microsoft.com/itpro/windows/manage/waas-overview#servicing-branches).
|
||||
|
||||
**To manually configure Surface Hub to use CB or CBB:**
|
||||
1. Open **Settings** > **Update & Security** > **Windows Update**, and then select **Advanced Options**.
|
||||
2. Select **Defer feature updates**.
|
||||
|
||||
To configure Surface Hub to use CB or CBB remotely using MDM, set an appropriate [Update/BranchReadinessLevel](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_BranchReadinessLevel) policy.
|
||||
|
||||
|
||||
### Configure when Surface Hub receives updates
|
||||
Once you've determined deployment rings for your Surface Hubs, configure update deferral policies for each ring:
|
||||
- To defer feature updates, set an appropriate [Update/DeferFeatureUpdatesPeriodInDays](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_DeferFeatureUpdatesPeriodInDays) policy for each ring.
|
||||
- To defer quality updates, set an appropriate [Update/DeferQualityUpdatesPeriodInDays](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_DeferQualityUpdatesPeriodInDays) policy for each ring.
|
||||
- To defer feature updates, set an appropriate [Update/DeferFeatureUpdatesPeriodInDays](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-deferfeatureupdatesperiodindays) policy for each ring.
|
||||
- To defer quality updates, set an appropriate [Update/DeferQualityUpdatesPeriodInDays](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-deferqualityupdatesperiodindays) policy for each ring.
|
||||
|
||||
> [!NOTE]
|
||||
> If you encounter issues during the update rollout, you can pause updates using [Update/PauseFeatureUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseFeatureUpdates) and [Update/PauseQualityUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseQualityUpdates).
|
||||
> If you encounter issues during the update rollout, you can pause updates using [Update/PauseFeatureUpdates](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-pausefeatureupdates) and [Update/PauseQualityUpdates](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-pausequalityupdates).
|
||||
|
||||
|
||||
## Use Windows Server Update Services
|
||||
|
||||
@ -6,6 +6,7 @@
|
||||
### [Certificate authentication device enrollment](certificate-authentication-device-enrollment.md)
|
||||
### [On-premise authentication device enrollment](on-premise-authentication-device-enrollment.md)
|
||||
## [Understanding ADMX-backed policies](understanding-admx-backed-policies.md)
|
||||
## [Enable ADMX-backed policies in MDM](enable-admx-backed-policies-in-mdm.md)
|
||||
## [Win32 and Desktop Bridge app policy configuration](win32-and-centennial-app-policy-configuration.md)
|
||||
## [Implement server-side support for mobile application management on Windows](implement-server-side-mobile-application-management.md)
|
||||
## [Diagnose MDM failures in Windows 10](diagnose-mdm-failures-in-windows-10.md)
|
||||
|
||||
@ -7,12 +7,15 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: nickbrower
|
||||
ms.date: 06/19/2017
|
||||
ms.date: 08/10/2017
|
||||
---
|
||||
|
||||
# DeviceManageability CSP
|
||||
|
||||
|
||||
> [!WARNING]
|
||||
> Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
The DeviceManageability configuration service provider (CSP) is used retrieve the general information about MDM configuration capabilities on the device. This CSP was added in Windows 10, version 1607.
|
||||
|
||||
For performance reasons DeviceManageability CSP directly reads the CSP version from the registry. Specifically, the value csp\_version is used to determine each of the CSP versions. The csp\_version is a value under each of the CSP registration keys. To have consistency on the CSP version, the CSP GetProperty implementation for CFGMGR\_PROPERTY\_SEMANTICTYPE has to be updated to read from the registry as well, so that the both paths return the same information.
|
||||
@ -39,6 +42,8 @@ Added in Windows 10, version 1709. Provider ID of the configuration source.
|
||||
<a href="" id="capabilities-cspversions"></a>**Provider/_ProviderID_/ConfigInfo**
|
||||
Added in Windows 10, version 1709. Configuration information string value set by the configuration source. Recommended to be used during sync session.
|
||||
|
||||
The MDM server can query ConfigInfo to determine the settings of the traditional PC management system. The MDM can also configure ConfigInfo with its own device management information.
|
||||
|
||||
Data type is string. Supported operations are Add, Get, Delete, and Replace.
|
||||
|
||||
<a href="" id="capabilities-cspversions"></a>**Provider/_ProviderID_/EnrollmentInfo**
|
||||
|
||||
@ -0,0 +1,300 @@
|
||||
---
|
||||
title: Enable ADMX-backed policies in MDM
|
||||
description: Guide to configuring ADMX-backed policies in MDM
|
||||
ms.author: maricia
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: nickbrower
|
||||
ms.date: 08/11/2017
|
||||
---
|
||||
|
||||
# Enable ADMX-backed policies in MDM
|
||||
|
||||
> [!WARNING]
|
||||
> Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
This is a step-by-step guide to configuring ADMX-backed policies in MDM.
|
||||
|
||||
Starting in Windows 10 version 1703, Mobile Device Management (MDM) policy configuration support expanded to allow access of select Group Policy administrative templates (ADMX-backed policies) for Windows PCs via the [Policy configuration service provider (CSP)](policy-configuration-service-provider.md). Configuring ADMX-backed policies in Policy CSP is different from the typical way you configure a traditional MDM policy.
|
||||
|
||||
Summary of steps to enable a policy:
|
||||
- Find the policy from the list ADMX-backed policies.
|
||||
- Find the Group Policy related information from the MDM policy description.
|
||||
- Use the Group Policy Editor to determine whether there are parameters necessary to enable the policy.
|
||||
- Create the data payload for the SyncML.
|
||||
|
||||
## Enable a policy
|
||||
|
||||
1. Find the policy from the list [ADMX-backed policies](policy-configuration-service-provider.md#admx-backed-policies). You need the following information listed in the policy description.
|
||||
- GP English name
|
||||
- GP name
|
||||
- GP ADMX file name
|
||||
- GP path
|
||||
|
||||
2. Use the Group Policy Editor to determine whether you need additional information to enable the policy. Run GPEdit.msc
|
||||
|
||||
1. Click **Start**, then in the text box type **gpedit**.
|
||||
|
||||
2. Under **Best match**, click **Edit group policy** to launch it.
|
||||
|
||||
|
||||
|
||||
3. In **Local Computer Policy** navigate to the policy you want to configure.
|
||||
|
||||
In this example, navigate to **Administrative Templates > System > App-V**.
|
||||
|
||||
|
||||
|
||||
4. Double-click **Enable App-V Client**.
|
||||
|
||||
The **Options** section is empty, which means there are no parameters necessary to enable the policy. If the **Options** section is not empty, follow the procedure in [Enable a policy that requires parameters](#enable-a-policy-that-requires-parameters)
|
||||
|
||||
|
||||
|
||||
3. Create the SyncML to enable the policy that does not require any parameter.
|
||||
|
||||
In this example you configure **Enable App-V Client** to **Enabled**.
|
||||
|
||||
> [!Note]
|
||||
> The \<Data> payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
|
||||
|
||||
``` syntax
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
<Meta>
|
||||
<Format>chr</Format>
|
||||
<Type>text/plain</Type>
|
||||
</Meta>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/AllowAppVClient </LocURI>
|
||||
</Target>
|
||||
<Data><Enabled/></Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
<Final/>
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
|
||||
## Enable a policy that requires parameters
|
||||
|
||||
|
||||
1. Create the SyncML to enable the policy that requires parameters.
|
||||
|
||||
In this example, the policy is in **Administrative Templates > System > App-V > Publishing**.
|
||||
|
||||
1. Double-click **Publishing Server 2 Settings** to see the parameters you need to configure when you enable this policy.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
2. Find the variable names of the parameters in the ADMX file.
|
||||
|
||||
You can find the ADMX file name in the policy description in Policy CSP. In this example, the filename appv.admx is listed in [AppVirtualization/PublishingAllowServer2](policy-configuration-service-provider.md#appvirtualization-publishingallowserver2).
|
||||
|
||||
|
||||
|
||||
3. Navigate to **C:\Windows\PolicyDefinitions** (default location of the admx files) and open appv.admx.
|
||||
|
||||
4. Search for GP name **Publishing_Server2_policy**.
|
||||
|
||||
|
||||
5. Under **policy name="Publishing_Server2_Policy"** you can see the \<elements> listed. The text id and enum id represents the data id you need to include in the SyncML data payload. They correspond to the fields you see in GP Editor.
|
||||
|
||||
Here is the snippet from appv.admx:
|
||||
|
||||
``` syntax
|
||||
<!-- Publishing Server 2 -->
|
||||
<policy name="Publishing_Server2_Policy" class="Machine" displayName="$(string.PublishingServer2)"
|
||||
explainText="$(string.Publishing_Server_Help)" presentation="$(presentation.Publishing_Server2)"
|
||||
key="SOFTWARE\Policies\Microsoft\AppV\Client\Publishing\Servers\2">
|
||||
<parentCategory ref="CAT_Publishing" />
|
||||
<supportedOn ref="windows:SUPPORTED_Windows7" />
|
||||
<elements>
|
||||
<text id="Publishing_Server2_Name_Prompt" valueName="Name" required="true"/>
|
||||
<text id="Publishing_Server_URL_Prompt" valueName="URL" required="true"/>
|
||||
<enum id="Global_Publishing_Refresh_Options" valueName="GlobalEnabled">
|
||||
<item displayName="$(string.False)">
|
||||
<value>
|
||||
<decimal value="0"/>
|
||||
</value>
|
||||
</item>
|
||||
<item displayName="$(string.True)">
|
||||
<value>
|
||||
<decimal value="1"/>
|
||||
</value>
|
||||
</item>
|
||||
</enum>
|
||||
<enum id="Global_Refresh_OnLogon_Options" valueName="GlobalLogonRefresh">
|
||||
<item displayName="$(string.False)">
|
||||
<value>
|
||||
<decimal value="0"/>
|
||||
</value>
|
||||
</item>
|
||||
<item displayName="$(string.True)">
|
||||
<value>
|
||||
<decimal value="1"/>
|
||||
</value>
|
||||
</item>
|
||||
</enum>
|
||||
<decimal id="Global_Refresh_Interval_Prompt" valueName="GlobalPeriodicRefreshInterval" minValue="0" maxValue="31"/>
|
||||
<enum id="Global_Refresh_Unit_Options" valueName="GlobalPeriodicRefreshIntervalUnit">
|
||||
<item displayName="$(string.Hour)">
|
||||
<value>
|
||||
<decimal value="0"/>
|
||||
</value>
|
||||
</item>
|
||||
<item displayName="$(string.Day)">
|
||||
<value>
|
||||
<decimal value="1"/>
|
||||
</value>
|
||||
</item>
|
||||
</enum>
|
||||
<enum id="User_Publishing_Refresh_Options" valueName="UserEnabled">
|
||||
<item displayName="$(string.False)">
|
||||
<value>
|
||||
<decimal value="0"/>
|
||||
</value>
|
||||
</item>
|
||||
<item displayName="$(string.True)">
|
||||
<value>
|
||||
<decimal value="1"/>
|
||||
</value>
|
||||
</item>
|
||||
</enum>
|
||||
<enum id="User_Refresh_OnLogon_Options" valueName="UserLogonRefresh">
|
||||
<item displayName="$(string.False)">
|
||||
<value>
|
||||
<decimal value="0"/>
|
||||
</value>
|
||||
</item>
|
||||
<item displayName="$(string.True)">
|
||||
<value>
|
||||
<decimal value="1"/>
|
||||
</value>
|
||||
</item>
|
||||
</enum>
|
||||
<decimal id="User_Refresh_Interval_Prompt" valueName="UserPeriodicRefreshInterval" minValue="0" maxValue="31"/>
|
||||
<enum id="User_Refresh_Unit_Options" valueName="UserPeriodicRefreshIntervalUnit">
|
||||
<item displayName="$(string.Hour)">
|
||||
<value>
|
||||
<decimal value="0"/>
|
||||
</value>
|
||||
</item>
|
||||
<item displayName="$(string.Day)">
|
||||
<value>
|
||||
<decimal value="1"/>
|
||||
</value>
|
||||
</item>
|
||||
</enum>
|
||||
</elements>
|
||||
</policy>
|
||||
```
|
||||
|
||||
6. From the \<elements> tag, copy all the text id and enum id and create an XML with data id and value fields. The value field contains the configuration settings you would enter in the GP Editor.
|
||||
|
||||
Here is the example XML for Publishing_Server2_Policy :
|
||||
|
||||
``` syntax
|
||||
<data id="Publishing_Server2_Name_Prompt" value="Name"/>
|
||||
<data id="Publishing_Server_URL_Prompt" value="http://someuri"/>
|
||||
<data id="Global_Publishing_Refresh_Options" value="1"/>
|
||||
<data id="Global_Refresh_OnLogon_Options" value="0"/>
|
||||
<data id="Global_Refresh_Interval_Prompt" value="15"/>
|
||||
<data id="Global_Refresh_Unit_Options" value="0"/>
|
||||
<data id="User_Publishing_Refresh_Options" value="0"/>
|
||||
<data id="User_Refresh_OnLogon_Options" value="0"/>
|
||||
<data id="User_Refresh_Interval_Prompt" value="15"/>
|
||||
<data id="User_Refresh_Unit_Options" value="1"/>
|
||||
```
|
||||
|
||||
7. Create the SyncML to enable the policy. Payload contains \<enabled/> and name/value pairs.
|
||||
|
||||
Here is the example for **AppVirtualization/PublishingAllowServer2**:
|
||||
|
||||
> [!Note]
|
||||
> The \<Data> payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
<Meta>
|
||||
<Format>chr</Format>
|
||||
<Type>text/plain</Type>
|
||||
</Meta>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/PublishingAllowServer2</LocURI>
|
||||
</Target>
|
||||
<![CDATA[<enabled/><data id="Publishing_Server2_Name_Prompt" value="name prompt"/><data
|
||||
id="Publishing_Server_URL_Prompt" value="URL prompt"/><data
|
||||
id="Global_Publishing_Refresh_Options" value="1"/><data
|
||||
id="Global_Refresh_OnLogon_Options" value="0"/><data
|
||||
id="Global_Refresh_Interval_Prompt" value="15"/><data
|
||||
id="Global_Refresh_Unit_Options" value="0"/><data
|
||||
id="User_Publishing_Refresh_Options" value="0"/><data
|
||||
id="User_Refresh_OnLogon_Options" value="0"/><data
|
||||
id="User_Refresh_Interval_Prompt" value="15"/><data
|
||||
id="User_Refresh_Unit_Options" value="1"/>]]>
|
||||
</Item>
|
||||
</Replace>
|
||||
<Final/>
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
|
||||
## Disable a policy
|
||||
|
||||
The \<Data> payload is \<disabled/>. Here is an example to disable AppVirtualization/PublishingAllowServer2.
|
||||
|
||||
``` syntax
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
<Meta>
|
||||
<Format>chr</Format>
|
||||
<Type>text/plain</Type>
|
||||
</Meta>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/PublishingAllowServer2</LocURI>
|
||||
</Target>
|
||||
<Data><disabled/></Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
<Final/>
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
## Setting a policy to not configured
|
||||
|
||||
The \<Data> payload is empty. Here an example to set AppVirtualization/PublishingAllowServer2 to "Not Configured."
|
||||
|
||||
``` syntax
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/Policy/Config/AppVirtualization/PublishingAllowServer2</LocURI>
|
||||
</Target>
|
||||
</Item>
|
||||
</Delete>
|
||||
<Final/>
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 85 KiB |
BIN
windows/client-management/mdm/images/admx-appv-publishing.png
Normal file
BIN
windows/client-management/mdm/images/admx-appv-publishing.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 54 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 62 KiB |
BIN
windows/client-management/mdm/images/admx-appv.png
Normal file
BIN
windows/client-management/mdm/images/admx-appv.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
BIN
windows/client-management/mdm/images/admx-gpedit-search.png
Normal file
BIN
windows/client-management/mdm/images/admx-gpedit-search.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
@ -702,7 +702,7 @@ User Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, D
|
||||
|
||||
<!--StartADMX-->
|
||||
ADMX Info:
|
||||
- GP english name: *Publishing Server 2 Settings*
|
||||
- GP English name: *Publishing Server 2 Settings*
|
||||
- GP name: *Publishing_Server2_Policy*
|
||||
- GP path: *Administrative Templates/System/App-V/Publishing*
|
||||
- GP ADMX file name: *appv.admx*
|
||||
|
||||
@ -97,7 +97,7 @@ Appv.admx file:
|
||||
|
||||
## <a href="" id="admx-backed-policy-examples"></a>ADMX-backed policy examples
|
||||
|
||||
The following SyncML examples describe how to set a MDM policy that is defined by an ADMX template, specifically the Publishing_Server2_Policy Group Policy description in the application virtualization ADMX file, appv.admx. Note that the functionality that this Group Policy manages is not important; it is used to illustrate only how an MDM ISV can set an ADMX-backed policy. These SyncML examples illustrate common options and the corresponding SyncML code that can be used for testing your policies. Note that the payload of the SyncML must be XML-encoded; for this XML encoding, you can use the [Coder’s Toolbox](http://coderstoolbox.net/string/#!encoding=xml&action=encode&charset=us_ascii) online tool. To avoid encoding the payload, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||
The following SyncML examples describe how to set a MDM policy that is defined by an ADMX template, specifically the Publishing_Server2_Policy Group Policy description in the application virtualization ADMX file, appv.admx. Note that the functionality that this Group Policy manages is not important; it is used to illustrate only how an MDM ISV can set an ADMX-backed policy. These SyncML examples illustrate common options and the corresponding SyncML code that can be used for testing your policies. Note that the payload of the SyncML must be XML-encoded; for this XML encoding, you can use favorite online tool. To avoid encoding the payload, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
|
||||
|
||||
|
||||
### <a href="" id="enabling-a-policy"></a>Enabling a policy
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user