From 699078fc6fc1b5d769e05063da22e59fa3d838f1 Mon Sep 17 00:00:00 2001 From: Mandi Ohlinger Date: Thu, 2 Dec 2021 13:22:20 -0500 Subject: [PATCH] Note; code tag --- .../mdm/structure-of-oma-dm-provisioning-files.md | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/windows/client-management/mdm/structure-of-oma-dm-provisioning-files.md b/windows/client-management/mdm/structure-of-oma-dm-provisioning-files.md index 3533bdee35..00da69a8cb 100644 --- a/windows/client-management/mdm/structure-of-oma-dm-provisioning-files.md +++ b/windows/client-management/mdm/structure-of-oma-dm-provisioning-files.md @@ -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. -> **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 `` node value for the `` 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 ".". -``` +```xml ./Vendor/MSFT/Registry/HKLM/Security/./Test ``` @@ -166,11 +167,3 @@ The following example illustrates how to use the Replace command to update a dev ``` - -  - - - - - -