[MS-MDM]: Mobile Device Management Protocol

This topic lists the Errata found in [MS-MDM] since it was last published. Since this topic is updated frequently, we recommend that you subscribe to these RSS or Atom feeds to receive update notifications.

Errata are subject to the same terms as the Open Specifications documentation referenced.

RSS

Atom

To view a PDF file of the errata for the previous versions of this document, see the following ERRATA Archives:

October 16, 2015 - Download

June 30, 2015 - Download

July 18, 2016 - Download

December 1, 2017 - Download

April 7, 2021 - Download

Errata below are for Protocol Document Version 14.0 - 2022/04/29

Errata Published*

Description

2022/06/14

In section 2.1 Transport: Added Note 9 to indicate client behavior when the ForceAadToken in the DMClient configuration service provider is set by the server.

Changed from:

. . .

Note 8: If the server has set EntDMID in the DMClient configuration service provider, the client adds client-request-id to the header and sets it to the value of EntDMID.<9> See [MSDOCS-DMClient-CSP] for more information.

Changed to:

. . .

Note 8: If the server has set EntDMID in the DMClient configuration service provider, the client adds client-request-id to the header and sets it to the value of EntDMID.<9> See [MSDOCS-DMClient-CSP] for more information.

Note 9: If the server has set ForceAadToken in the DMClient configuration service provider, and the device is joined to an Azure Active Domain (AAD), the client adds a custom header that contains the AAD token. The header is in the following format.

DeviceToken: CI6MTQxmCF5xgu6yYcmV9ng6vhQfaJYw…

See [MSDOCS-DMClient-CSP] for more information.<10>

Appendix B:

<10> Section 2.1: Not available in Windows 10 v19H2 and earlier.

2022/05/02

3.2.5.1 Windows Azure Virtual Desktop for Multi-users' User Setting Configuration, added a product note that the added support for user sessions multi-session Edition only in WVD was backported.

Changed from:

Windows Azure Virtual Desktop (AVD) supports multiple users that can log on simultaneously. To allow configuration of user settings, the MDM server must support "multi-user AVD" mode…

Changed to:

Windows Azure Virtual Desktop (AVD) supports multiple users that can log on simultaneously.<15> To allow configuration of user settings, the MDM server must support "multi-user AVD" mode…

<15> Section 3.2.5.1: Servicing May 2022, support for user sessions on Windows 11, version 22H2 operating system (version 2) multi-session Edition only in Windows Virtual Desktop was backported to Windows 11 (version 1).