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

Merge pull request #3044 from nenonix/patch-7

Browse Source 
Update oma-dm-protocol-support.md
This commit is contained in:
Jeanie Decker
2019-03-25 05:53:11 -07:00
committed by GitHub
parent 3e7dfb81f8 2ea4649c76
commit 190d59bbd2
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
windows/client-management/mdm/oma-dm-protocol-support.md
View File

@ -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, 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:
- 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: