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

Note; code tag

Browse Source
This commit is contained in:
Mandi Ohlinger
2021-12-02 13:22:20 -05:00
committed by GitHub
parent 55d84a65a4
commit 699078fc6f
1 changed files with 3 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -81,7 +81,8 @@ This information is used to by the client device to properly manage the DM sessi
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. 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.
> **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](devinfo-csp.md). > [!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](devinfo-csp.md).
   
@ -125,7 +126,7 @@ The following example shows the body component of a DM message. In this example,
When using SyncML for OMA DM provisioning, a LocURI in SyncBody can have a "." as a valid segment name only in the first segment. However, a "." is not a valid segment name for the other segments. For example, the following LocURI is not valid because the segment name of the seventh segment is a ".". When using SyncML for OMA DM provisioning, a LocURI in SyncBody can have a "." as a valid segment name only in the first segment. However, a "." is not a valid segment name for the other segments. For example, the following LocURI is not valid because the segment name of the seventh segment is a ".".
``` ```xml
<LocURI>./Vendor/MSFT/Registry/HKLM/Security/./Test</LocURI> <LocURI>./Vendor/MSFT/Registry/HKLM/Security/./Test</LocURI>
``` ```
@ -166,11 +167,3 @@ The following example illustrates how to use the Replace command to update a dev
<Final /> <Final />
</SyncBody> </SyncBody>
``` ```