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

Set appliesto

Browse Source
This commit is contained in:
Vinay Pamnani
2023-04-04 17:46:00 -04:00
parent b813bf46d4
commit a44ba87186
42 changed files with 920 additions and 987 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
windows/client-management/structure-of-oma-dm-provisioning-files.md
View File

@ -9,6 +9,9 @@ ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.date: 06/26/2017
appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
---
# Structure of OMA DM provisioning files
@ -65,17 +68,16 @@ The following example shows the general structure of the XML document sent by th
SyncHdr includes the following information:
- Document Type Definition (DTD) and protocol version numbers
- Document Type Definition (DTD) and protocol version numbers
- Session and message identifiers. Each message in the same DM session must have a different MsgID.
- Session and message identifiers. Each message in the same DM session must have a different MsgID.
- Message source and destination Uniform Resource Identifiers (URIs)
- Message source and destination Uniform Resource Identifiers (URIs)
- Credentials for authentication
- Credentials for authentication
This information is used to by the client device to properly manage the DM session.
**Code example**
The following example shows the header component of a DM message. In this case, OMA DM version 1.2 is used as an example only.
@ -83,7 +85,7 @@ The following example shows the header component of a DM message. In this case,
> [!NOTE]
> The `<LocURI>` node value for the `<Source>` element in the SyncHdr of the device-generated DM package should be the same as the value of ./DevInfo/DevID. For more information about DevID, see [DevInfo configuration service provider](mdm/devinfo-csp.md).
 
```xml
<SyncHdr>