Query regarding MDM Unenrollment initiated by the User.

%3CLINGO-SUB%20id%3D%22lingo-sub-1719694%22%20slang%3D%22en-US%22%3EQuery%20regarding%20MDM%20Unenrollment%20initiated%20by%20the%20User.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1719694%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20facing%20one%20Issue%20regarding%20MDM%20Unrenrollment%20process%20initiated%20by%20User%2C%3CBR%20%2F%3EIn%20which%20when%20MDM%20server%20is%20receiving%20Unenrollment%20the%20request%2C%20it%20does%20not%20contain%20Meta%20value%20for%20%3CSTRONG%3EAlert(1226)%3C%2FSTRONG%3E%20in%20the%20SyncBody.%3CBR%20%2F%3EPlease%20find%20following%20logs%20for%20the%20same%20behavior%20%3A%3C%2FP%3E%3CP%3E%5BWindows%20MDM%20Sync%20request%20for%20device%20guid%20%26lt%3B%26gt%3B%20%3CSYNCML%20xmlns%3D%22%26quot%3BSYNCML%3ASYNCML1.2%26quot%3B%22%3E%3C%2FSYNCML%3E%3C%2FP%3E%3CP%3E%3CSYNCBODY%3E%3CBR%20%2F%3E%3CALERT%3E%3CBR%20%2F%3E%3CCMDID%3E2%3C%2FCMDID%3E%3CBR%20%2F%3E%3CDATA%3E1201%3C%2FDATA%3E%3CBR%20%2F%3E%3C%2FALERT%3E%3CBR%20%2F%3E%3CALERT%3E%3CBR%20%2F%3E%3CCMDID%3E3%3C%2FCMDID%3E%3CBR%20%2F%3E%3CDATA%3E1224%3C%2FDATA%3E%3CBR%20%2F%3E%3CITEM%3E%3CBR%20%2F%3E%26lt%3Bmeta%20%2F%26gt%3B%3CBR%20%2F%3E%3CDATA%3Euser%3C%2FDATA%3E%3CBR%20%2F%3E%3C%2FITEM%3E%3CBR%20%2F%3E%3C%2FALERT%3E%3CBR%20%2F%3E%3CALERT%3E%3CBR%20%2F%3E%3CCMDID%3E4%3C%2FCMDID%3E%3CBR%20%2F%3E%3CDATA%3E1226%3C%2FDATA%3E%3CBR%20%2F%3E%3CITEM%3E%3CBR%20%2F%3E%3CSTRONG%3E%26lt%3Bmeta%20%2F%26gt%3B%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CDATA%3E1%3C%2FDATA%3E%3CBR%20%2F%3E%3C%2FITEM%3E%3CBR%20%2F%3E%3C%2FALERT%3E%3CBR%20%2F%3E%3C!--%20other%20device%20information%20--%3E%3CBR%20%2F%3E%3CSYNCBODY%3E%3CBR%20%2F%3E%3CBR%20%2F%3EEarlier%2C%20Under%20this%20Alert%20tag%20we%20had%20a%20Meta%20tag%20which%20contained%20string%20%3A%20%22%3CSTRONG%3Ecom.microsoft%3Amdm.unenrollment.userrequest%3C%2FSTRONG%3E%22%20as%20part%20of%20User%20Initiated%20disconnection%2C%20on%20basis%20of%20which%20MDM%20Server%20proceeds%20with%20further%20action.%3CBR%20%2F%3E%3CALERT%3E%3CBR%20%2F%3E%3CCMDID%3E4%3C%2FCMDID%3E%3CBR%20%2F%3E%3CDATA%3E1226%3C%2FDATA%3E%3CBR%20%2F%3E%3CITEM%3E%3CBR%20%2F%3E%26lt%3Bmeta%20%2F%26gt%3B%3CBR%20%2F%3E%3CTYPE%3Ecom.microsoft%3Amdm.unenrollment.userrequest%3C%2FTYPE%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDATA%3E1%3C%2FDATA%3E%3CBR%20%2F%3E%3C%2FITEM%3E%3CBR%20%2F%3E%3C%2FALERT%3E%3C%2FSYNCBODY%3E%3C%2FSYNCBODY%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20now%20the%20above%20%26lt%3Bmeta%20%2F%26gt%3B%20that%20MDM%20Server%20receives%20is%20Empty%20tag%20without%20any%20String%20(%26lt%3Bmeta%20%2F%26gt%3B).%3CBR%20%2F%3EThis%20behavior%20can%20be%20seen%20on%20various%20windows%20versions%20like%20%3A%20%3CEM%3E1803%2C%201809%2C%201903%2C%201909%20and%202004%3C%2FEM%3E%20that%20has%20been%20tested%20and%20getting%20the%20same%20result.%3CBR%20%2F%3EIn%20the%20document%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fdisconnecting-from-mdm-unenrollment%23user-initiated-disconnection%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fdisconnecting-from-mdm-unenrollment%23user-initiated-disconnection%3C%2FA%3E%26nbsp%3B%2C%20nothing%20is%20updated%20or%20mentioned%20regarding%20change%20in%20unenrollment%20process%20initiated%20by%20the%20User.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ECan%20we%20use%20the%20alert%20value%201226%20without%20the%20%22com.microsoft%3Amdm.unenrollment.userrequest%22%20value%20be%20used%20to%20trigger%20unenrollment%20for%20the%20device.%20Any%20reason%20why%20the%20type%20has%20been%20removed%20from%20these%20versions.%3C%2FP%3E%3CP%3EPlease%20clarify%20on%20same%20so%20that%20we%20can%20proceed%20on%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1719694%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMDM%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows10%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

Hi,

 

We are facing one Issue regarding MDM Unrenrollment process initiated by User,
In which when MDM server is receiving Unenrollment the request, it does not contain Meta value for Alert(1226) in the SyncBody.
Please find following logs for the same behavior :

[Windows MDM Sync request for device guid <> <SyncML xmlns="SYNCML:SYNCML1.2">

<SyncBody>
<Alert>
<CmdID>2</CmdID>
<Data>1201</Data>
</Alert>
<Alert>
<CmdID>3</CmdID>
<Data>1224</Data>
<Item>
<Meta/>
<Data>user</Data>
</Item>
</Alert>
<Alert>
<CmdID>4</CmdID>
<Data>1226</Data>
<Item>
<Meta/>
<Data>1</Data>
</Item>
</Alert>
<!-- other device information -->
<SyncBody>

Earlier, Under this Alert tag we had a Meta tag which contained string : "com.microsoft:mdm.unenrollment.userrequest" as part of User Initiated disconnection, on basis of which MDM Server proceeds with further action.
<Alert>
<CmdID>4</CmdID>
<Data>1226</Data>
<Item>
<Meta>
<ns2:Type>com.microsoft:mdm.unenrollment.userrequest</ns2:Type>
</Meta>
<Data>1</Data>
</Item>
</Alert>

 

But now the above <Meta> that MDM Server receives is Empty tag without any String (<Meta/>).
This behavior can be seen on various windows versions like : 1803, 1809, 1903, 1909 and 2004 that has been tested and getting the same result.
In the document : https://docs.microsoft.com/en-us/windows/client-management/mdm/disconnecting-from-mdm-unenrollment#u... , nothing is updated or mentioned regarding change in unenrollment process initiated by the User.


Can we use the alert value 1226 without the "com.microsoft:mdm.unenrollment.userrequest" value be used to trigger unenrollment for the device. Any reason why the type has been removed from these versions.

Please clarify on same so that we can proceed on this.

 

Thanks.

0 Replies