Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update oma-dm-protocol-support.md #3044

Merged
merged 3 commits into from Mar 25, 2019

Conversation

Projects
None yet
5 participants
@nenonix
Copy link
Contributor

nenonix commented Mar 25, 2019

Grammar and formatting fixes #673

Update oma-dm-protocol-support.md
Grammar and formatting fixes #673
@mypil

This comment has been minimized.

Copy link
Collaborator

mypil commented Mar 25, 2019

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@@ -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.

This comment has been minimized.

Copy link
@JohanFreelancer9

JohanFreelancer9 Mar 25, 2019

For CSPs and policies that support per user configuration, the MDM server could send user targeted setting values to the device that the user who enrolled 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.

This comment has been minimized.

Copy link
@mypil

mypil Mar 25, 2019

Collaborator

@nenonix - can you possibly make the necessary suggested changes made by Johan or merge the new commit for this PR? Thanks.

nenonix added some commits Mar 25, 2019

Update oma-dm-protocol-support.md
further grammar fixes
Update oma-dm-protocol-support.md
more improvements
@mypil

This comment has been minimized.

Copy link
Collaborator

mypil commented Mar 25, 2019

@kenwith - this article is authored by @MariciaAlforque. Would you be able to merge the content for this PR based on issue #673?

Thank you.

@jdeckerms jdeckerms merged commit 190d59b into MicrosoftDocs:master Mar 25, 2019

1 check passed

license/cla All CLA requirements met.
@@ -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.

This comment has been minimized.

Copy link
@JohanFreelancer9

JohanFreelancer9 Mar 25, 2019

Copy edit - no changes.

@@ -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.

This comment has been minimized.

Copy link
@JohanFreelancer9

JohanFreelancer9 Mar 25, 2019

For CSPs and policies that support per user configuration, the MDM server can send user targeted setting values to the device that an 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.

- 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).

This comment has been minimized.

Copy link
@JohanFreelancer9

JohanFreelancer9 Mar 25, 2019

  • 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).

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

This comment has been minimized.

Copy link
@JohanFreelancer9

JohanFreelancer9 Mar 25, 2019

  • 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
@JohanFreelancer9
Copy link

JohanFreelancer9 left a comment

Please review changes.

@illfated

This comment has been minimized.

Copy link
Contributor

illfated commented Mar 25, 2019

@JohanFreelancer9 : the Pull Request above has already been merged, so your belated requests for change need to be moved to a new PR or issue ticket (depending on your preferred route of action).

@mypil

This comment has been minimized.

Copy link
Collaborator

mypil commented Mar 26, 2019

@nenonix - were you able to merge the new commits on the copy/edit review done by @JohanFreelancer9 before jdeckerms merged the entire PR content? if not, there may be a need to create another PR with the copy/edit recommendations. thanks

@nenonix

This comment has been minimized.

Copy link
Contributor Author

nenonix commented Mar 26, 2019

No need, I incorporated those that were valid,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.