From 640a7510a5d76d3565d38891a8013ba7be739e3b Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 25 Mar 2019 09:12:20 +0200 Subject: [PATCH 1/3] Update oma-dm-protocol-support.md Grammar and formatting fixes https://github.com/MicrosoftDocs/windows-itpro-docs/issues/673 --- windows/client-management/mdm/oma-dm-protocol-support.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/client-management/mdm/oma-dm-protocol-support.md b/windows/client-management/mdm/oma-dm-protocol-support.md index 29344603d2..aab3c9d663 100644 --- a/windows/client-management/mdm/oma-dm-protocol-support.md +++ b/windows/client-management/mdm/oma-dm-protocol-support.md @@ -314,13 +314,13 @@ For more information about Basic or MD5 client authentication, MD5 server authen ## User targeted vs. Device targeted configuration -For CSPs and policies that supports per user configuration, MDM server could send user targeted setting values to the device the user that enrolled MDM is actively logged in. The device notifies the server the login status via a device alert (1224) with Alert type = in DM pkg\#1. +For CSPs and policies that support per user configuration, MDM server could send user targeted setting values to the device the user that enrolled MDM is actively logged in. The device notifies the server of the login status via a device alert (1224) with Alert type = in DM pkg\#1. The data part of this alert could be one of following strings: -- user – the user that enrolled the device is actively login. The MDM server could send user specific configuration for CSPs/policies that support per user configuration +- user – the user that enrolled the device is actively logged in. The MDM server could send user specific configuration for CSPs/policies that support per user configuration - others – another user login but that user does not have an MDM account. The server can only apply device wide configuration, e.g. configuration applies to all users in the device. -- none – no active user login. The server can only apply device wide configuration and available configuration is restricted to the device environment (no active user login +- none – no active user login. The server can only apply device wide configuration and available configuration is restricted to the device environment (no active user login). Below is an alert example: From d699172877a10b48ba3a790158aa0643fc49ed95 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 25 Mar 2019 13:24:07 +0200 Subject: [PATCH 2/3] Update oma-dm-protocol-support.md further grammar fixes --- windows/client-management/mdm/oma-dm-protocol-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/oma-dm-protocol-support.md b/windows/client-management/mdm/oma-dm-protocol-support.md index aab3c9d663..d2ec519a10 100644 --- a/windows/client-management/mdm/oma-dm-protocol-support.md +++ b/windows/client-management/mdm/oma-dm-protocol-support.md @@ -314,7 +314,7 @@ For more information about Basic or MD5 client authentication, MD5 server authen ## User targeted vs. Device targeted configuration -For CSPs and policies that support per user configuration, MDM server could send user targeted setting values to the device the user that enrolled MDM is actively logged in. The device notifies the server of the login status via a device alert (1224) with Alert type = in DM pkg\#1. +For CSPs and policies that support per user configuration, the MDM server can send user targeted setting values to the device that a user, who has enrolled with MDM, is actively logged into. The device notifies the server of the login status via a device alert (1224) with Alert type = in DM pkg\#1. The data part of this alert could be one of following strings: From 2ea4649c7633c1401d2813e2c40ae31f49bcec11 Mon Sep 17 00:00:00 2001 From: Nicole Turner <39884432+nenonix@users.noreply.github.com> Date: Mon, 25 Mar 2019 13:27:45 +0200 Subject: [PATCH 3/3] Update oma-dm-protocol-support.md more improvements --- windows/client-management/mdm/oma-dm-protocol-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/oma-dm-protocol-support.md b/windows/client-management/mdm/oma-dm-protocol-support.md index d2ec519a10..72df15b90d 100644 --- a/windows/client-management/mdm/oma-dm-protocol-support.md +++ b/windows/client-management/mdm/oma-dm-protocol-support.md @@ -314,7 +314,7 @@ For more information about Basic or MD5 client authentication, MD5 server authen ## User targeted vs. Device targeted configuration -For CSPs and policies that support per user configuration, the MDM server can send user targeted setting values to the device that a user, who has enrolled with MDM, is actively logged into. The device notifies the server of the login status via a device alert (1224) with Alert type = in DM pkg\#1. +For CSPs and policies that support per user configuration, the MDM server can send user targeted setting values to the device that a MDM-enrolled user is actively logged into. The device notifies the server of the login status via a device alert (1224) with Alert type = in DM pkg\#1. The data part of this alert could be one of following strings: