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

EnterpriseDesktopAppManagement CSP

Browse Source
This commit is contained in:
Vinay Pamnani 2023-02-27 15:41:45 -05:00
parent 3040f52f8f
commit bf9cf317e7
4 changed files with 2071 additions and 647 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.openpublishing.redirection.json
View File

@ -20530,6 +20530,11 @@
"redirect_url": "/windows/client-management/mdm/vpnv2-csp#profilexml-xsd-schema",
"redirect_document_id": true
},
{
"source_path": "windows/client-management/mdm/enterprisedesktopappmanagement2-xsd.md",
"redirect_url": "/windows/client-management/mdm/windows/enterprisedesktopappmanagement-csp#downloadinstall-xsd-schema",
"redirect_document_id": true
},
{
"source_path": "education/windows/education-scenarios-store-for-business.md",
"redirect_url": "/windows/resources",

1229
windows/client-management/mdm/enterprisedesktopappmanagement-csp.md
View File

File diff suppressed because it is too large Load Diff

512
windows/client-management/mdm/enterprisedesktopappmanagement-ddf-file.md
View File

@ -1,36 +1,37 @@
---
title: EnterpriseDesktopAppManagement DDF
description: This topic shows the OMA DM device description framework (DDF) for the EnterpriseDesktopAppManagement configuration service provider.
ms.reviewer:
title: EnterpriseDesktopAppManagement DDF file
description: View the XML file containing the device description framework (DDF) for the EnterpriseDesktopAppManagement configuration service provider.
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa
ms.topic: article
ms.date: 02/27/2023
ms.localizationpriority: medium
ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.date: 06/26/2017
ms.topic: reference
---
# EnterpriseDesktopAppManagement DDF
<!-- Auto-Generated CSP Document -->
This topic shows the OMA DM device description framework (DDF) for the **EnterpriseDesktopAppManagement** configuration service provider.
# EnterpriseDesktopAppManagement DDF file
DDF files are used only with OMA DM provisioning XML.
The following XML file contains the device description framework (DDF) for the EnterpriseDesktopAppManagement configuration service provider.
```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE MgmtTree PUBLIC " -//OMA//DTD-DM-DDF 1.2//EN"
"http://www.openmobilealliance.org/tech/DTD/DM_DDF-V1_2.dtd"
[<?oma-dm-ddf-ver supported-versions="1.2"?>]>
<!DOCTYPE MgmtTree PUBLIC " -//OMA//DTD-DM-DDF 1.2//EN" "http://www.openmobilealliance.org/tech/DTD/DM_DDF-V1_2.dtd"[<?oma-dm-ddf-ver supported-versions="1.2"?>]>
<MgmtTree xmlns:MSFT="http://schemas.microsoft.com/MobileDevice/DM">
<VerDTD>1.2</VerDTD>
<MSFT:Diagnostics>
</MSFT:Diagnostics>
<Node>
<NodeName>EnterpriseDesktopAppManagement</NodeName>
<Path>./Device/Vendor/MSFT</Path>
<Path>./User/Vendor/MSFT</Path>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>The root node for the EnterpriseDesktopAppManagement configuration service provider.</Description>
<DFFormat>
<node />
</DFFormat>
@ -41,8 +42,13 @@ DDF files are used only with OMA DM provisioning XML.
<Permanent />
</Scope>
<DFType>
<MIME>com.microsoft/1.0/MDM/EnterpriseDesktopAppManagement</MIME>
<MIME />
</DFType>
<MSFT:Applicability>
<MSFT:OsBuildVersion>10.0.10586</MSFT:OsBuildVersion>
<MSFT:CspVersion>1.0</MSFT:CspVersion>
<MSFT:EditionAllowList>0x4;0x1B;0x30;0x31;0x48;0x54;0x77;0x79;0x7A;0x7D;0x7E;0x81;0x82;0x8A;0x8B;0xA1;0xA2;0xA4;0xA5;0xAB;0xAC;0xAF;0xB4;0xBC;0xBF;0xCA;0xCB;0xCD;</MSFT:EditionAllowList>
</MSFT:Applicability>
</DFProperties>
<Node>
<NodeName>MSI</NodeName>
@ -60,22 +66,23 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<DDFName></DDFName>
</DFType>
</DFProperties>
<Node>
<NodeName></NodeName>
<NodeName>
</NodeName>
<DFProperties>
<AccessType>
<Add />
<Delete />
<Get />
</AccessType>
<Description>MSI product code for Threshold</Description>
<Description>The MSI product code for the application.</Description>
<DFFormat>
<node />
</DFFormat>
@ -85,13 +92,17 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFTitle>ProductID</DFTitle>
<DFType>
<DDFName />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFTitle>ProductID</DFTitle>
<DFType>
<DDFName></DDFName>
</DFType>
<MSFT:DynamicNodeNaming>
<MSFT:UniqueName>The MSI product code for the application.</MSFT:UniqueName>
</MSFT:DynamicNodeNaming>
<MSFT:AtomicRequired />
</DFProperties>
<Node>
<NodeName>Version</NodeName>
@ -109,12 +120,12 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
@ -123,6 +134,7 @@ DDF files are used only with OMA DM provisioning XML.
<AccessType>
<Get />
</AccessType>
<Description>Name of the application.</Description>
<DFFormat>
<chr />
</DFFormat>
@ -132,12 +144,12 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
@ -146,6 +158,7 @@ DDF files are used only with OMA DM provisioning XML.
<AccessType>
<Get />
</AccessType>
<Description>Publisher of application.</Description>
<DFFormat>
<chr />
</DFFormat>
@ -155,12 +168,12 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
@ -169,6 +182,7 @@ DDF files are used only with OMA DM provisioning XML.
<AccessType>
<Get />
</AccessType>
<Description>Installation path of the application.</Description>
<DFFormat>
<chr />
</DFFormat>
@ -178,12 +192,12 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
@ -192,6 +206,7 @@ DDF files are used only with OMA DM provisioning XML.
<AccessType>
<Get />
</AccessType>
<Description>Installation date of the application.</Description>
<DFFormat>
<chr />
</DFFormat>
@ -201,12 +216,12 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
@ -218,7 +233,7 @@ DDF files are used only with OMA DM provisioning XML.
<Exec />
<Get />
</AccessType>
<Description>Method to download and install an MSI app</Description>
<Description><![CDATA[Executes the download and installation of the application. In Windows 10, version 1703 service release, a new tag <DownloadFromAad> was added to the <Enforcement> section of the XML. The default value is 0 (do not send token). This tag is optional and needs to be set to 1 in case the server wants the download URL to get the AADUserToken.]]></Description>
<DFFormat>
<xml />
</DFFormat>
@ -228,12 +243,14 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
<MSFT:AllowedValues ValueType="None">
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
@ -242,6 +259,7 @@ DDF files are used only with OMA DM provisioning XML.
<AccessType>
<Get />
</AccessType>
<Description>Status of the application. Valid values: 10-Initialized, 20-Download In Progress, 25-Pending Download Retry, 30-Download Failed, 40-Download Completed, 48-Pending User Session, 50-Enforcement In Progress, 55-Pending Enforcement Retry, 60-Enforcement Failed, 70-Enforcement Completed</Description>
<DFFormat>
<int />
</DFFormat>
@ -251,12 +269,12 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
@ -265,6 +283,7 @@ DDF files are used only with OMA DM provisioning XML.
<AccessType>
<Get />
</AccessType>
<Description>The last error code during the application installation process. This is typically stored as an HRESULT format. Depending on what was occurring when the error happened, this could be the result of executing MSIExec.exe or the error result from an API that failed.</Description>
<DFFormat>
<int />
</DFFormat>
@ -274,12 +293,12 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
<Node>
@ -288,6 +307,7 @@ DDF files are used only with OMA DM provisioning XML.
<AccessType>
<Get />
</AccessType>
<Description>Contains the last error code description. The LastErrorDesc value is looked up for the matching LastError value. Sometimes there is no LastErrorDesc returned.</Description>
<DFFormat>
<chr />
</DFFormat>
@ -297,12 +317,12 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<DFType>
<MIME>text/plain</MIME>
</DFType>
</DFProperties>
</Node>
</Node>
@ -321,19 +341,25 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
<CaseSense>
<CS />
</CaseSense>
<DFType>
<DDFName></DDFName>
</DFType>
<MSFT:Applicability>
<MSFT:OsBuildVersion>10.0.14393</MSFT:OsBuildVersion>
<MSFT:CspVersion>1.0</MSFT:CspVersion>
</MSFT:Applicability>
</DFProperties>
<Node>
<NodeName></NodeName>
<NodeName>
</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description> A gateway (or device management server) uses this method to detect matching upgrade MSI product when a Admin wants to update an existing MSI app. If the same upgrade product is installed, then the update is allowed.</Description>
<DFFormat>
<chr />
</DFFormat>
@ -343,28 +369,384 @@ DDF files are used only with OMA DM provisioning XML.
<Scope>
<Dynamic />
</Scope>
<DFTitle>Guid</DFTitle>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<MSFT:DynamicNodeNaming>
<MSFT:ClientInventory />
</MSFT:DynamicNodeNaming>
</DFProperties>
</Node>
</Node>
</Node>
</Node>
<Node>
<NodeName>EnterpriseDesktopAppManagement</NodeName>
<Path>./Device/Vendor/MSFT</Path>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>The root node for the EnterpriseDesktopAppManagement configuration service provider.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<MIME />
</DFType>
<MSFT:Applicability>
<MSFT:OsBuildVersion>10.0.10586</MSFT:OsBuildVersion>
<MSFT:CspVersion>1.0</MSFT:CspVersion>
<MSFT:EditionAllowList>0x4;0x1B;0x30;0x31;0x48;0x54;0x77;0x79;0x7A;0x7D;0x7E;0x81;0x82;0x8A;0x8B;0xA1;0xA2;0xA4;0xA5;0xAB;0xAC;0xAF;0xB4;0xBC;0xBF;0xCA;0xCB;0xCD;</MSFT:EditionAllowList>
</MSFT:Applicability>
</DFProperties>
<Node>
<NodeName>MSI</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Product Type is MSI</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
<Node>
<NodeName>
</NodeName>
<DFProperties>
<AccessType>
<Add />
<Delete />
<Get />
</AccessType>
<Description>The MSI product code for the application.</Description>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<ZeroOrMore />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFTitle>ProductID</DFTitle>
<DFType>
<DDFName />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<MSFT:DynamicNodeNaming>
<MSFT:UniqueName>The MSI product code for the application.</MSFT:UniqueName>
</MSFT:DynamicNodeNaming>
<MSFT:AtomicRequired />
</DFProperties>
<Node>
<NodeName>Version</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>MSI Product Version</Description>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
</Node>
<Node>
<NodeName>Name</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Name of the application.</Description>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
</Node>
<Node>
<NodeName>Publisher</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Publisher of application.</Description>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
</Node>
<Node>
<NodeName>InstallPath</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Installation path of the application.</Description>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
</Node>
<Node>
<NodeName>InstallDate</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Installation date of the application.</Description>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
</Node>
<Node>
<NodeName>DownloadInstall</NodeName>
<DFProperties>
<AccessType>
<Add />
<Delete />
<Exec />
<Get />
</AccessType>
<Description><![CDATA[Executes the download and installation of the application. In Windows 10, version 1703 service release, a new tag <DownloadFromAad> was added to the <Enforcement> section of the XML. The default value is 0 (do not send token). This tag is optional and needs to be set to 1 in case the server wants the download URL to get the AADUserToken.]]></Description>
<DFFormat>
<xml />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<MSFT:AllowedValues ValueType="None">
</MSFT:AllowedValues>
</DFProperties>
</Node>
<Node>
<NodeName>Status</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Status of the application. Valid values: 10-Initialized, 20-Download In Progress, 25-Pending Download Retry, 30-Download Failed, 40-Download Completed, 48-Pending User Session, 50-Enforcement In Progress, 55-Pending Enforcement Retry, 60-Enforcement Failed, 70-Enforcement Completed</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
</Node>
<Node>
<NodeName>LastError</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>The last error code during the application installation process. This is typically stored as an HRESULT format. Depending on what was occurring when the error happened, this could be the result of executing MSIExec.exe or the error result from an API that failed.</Description>
<DFFormat>
<int />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
</Node>
<Node>
<NodeName>LastErrorDesc</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description>Contains the last error code description. The LastErrorDesc value is looked up for the matching LastError value. Sometimes there is no LastErrorDesc returned.</Description>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFType>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
</DFProperties>
</Node>
</Node>
<Node>
<NodeName>UpgradeCode</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<DFType>
<DDFName />
</DFType>
<CaseSense>
<CS />
</CaseSense>
<MSFT:Applicability>
<MSFT:OsBuildVersion>10.0.14393</MSFT:OsBuildVersion>
<MSFT:CspVersion>1.0</MSFT:CspVersion>
</MSFT:Applicability>
</DFProperties>
<Node>
<NodeName>
</NodeName>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<Description> A gateway (or device management server) uses this method to detect matching upgrade MSI product when a Admin wants to update an existing MSI app. If the same upgrade product is installed, then the update is allowed.</Description>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<OneOrMore />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<DFTitle>Guid</DFTitle>
<DFType>
<MIME>text/plain</MIME>
<MIME />
</DFType>
<CaseSense>
<CIS />
</CaseSense>
<MSFT:DynamicNodeNaming>
<MSFT:ClientInventory />
</MSFT:DynamicNodeNaming>
</DFProperties>
</Node>
</Node>
</Node>
</Node>
</MgmtTree>
```
 
 
## Related articles
[EnterpriseDesktopAppManagement configuration service provider reference](enterprisedesktopappmanagement-csp.md)

4
windows/client-management/mdm/toc.yml
View File

@ -738,10 +738,8 @@ items:
- name: EnterpriseDesktopAppManagement
href: enterprisedesktopappmanagement-csp.md
items:
- name: EnterpriseDesktopAppManagement DDF
- name: EnterpriseDesktopAppManagement DDF file
href: enterprisedesktopappmanagement-ddf-file.md
- name: EnterpriseDesktopAppManagement XSD
href: enterprisedesktopappmanagement2-xsd.md
- name: EnterpriseModernAppManagement
href: enterprisemodernappmanagement-csp.md
items: