none
Windows 8.1 MDM not responding to more than one SyncML from MDM server per session RRS feed

  • Question

  • Here is the behaviour i see, which was not expected by Windows 8.1.

    1) Device is enrolled

    2) Client initiates the connection with the MDM server defined in provisioning XML during enrollment.

    3) MDM Server sends some commands as a SyncML response.

    4) Client accepts the commands and sends Status and results.

    5) Again MDM Server sends some commands as a SyncML response.

    6) Client doesn't respond to these commands or not sending any SyncML. Here is the problem that i am referring to.

    We are capturing the traffic in fiddler and found that device is not sending the next request where we are expecting the status for these commands. 

    The same is being repeated in all the requests client initiates. DM Client responds back only for one syncML sent by the MDM server per session.

    Is this the expected behaviour with Windows 8.1? Or are we doing something wrong to see this behaviour?

    Below is the SyncML for which I am expecting the response from the DM client. (Note: I got the response for the same SyncML in the first connection, but not in the second.)

    <SyncML xml:lang="en" xmlns="syncml:SYNCML1.2">
      <SyncHdr>
        <VerDTD>1.2</VerDTD>
        <VerProto>DM/1.2</VerProto>
        <SessionID>1</SessionID>
        <MsgID>1</MsgID>
        <Target>
          <LocURI>0</LocURI>
        </Target>
        <Source>
          <LocURI>https://####</LocURI>
          <LocName>AfariaWinPhoneProvider</LocName>
        </Source>
        <RespURI>https://####</RespURI>
      </SyncHdr>
      <SyncBody>
        <Status>
          <CmdID>1</CmdID>
          <MsgRef>2</MsgRef>
          <CmdRef>0</CmdRef>
          <Cmd>SyncHdr</Cmd>
          <TargetRef>https://####</TargetRef>
          <SourceRef>0</SourceRef>
          <Data>200</Data>
        </Status>
        <Get>
          <CmdID>2</CmdID>
          <Item>
            <Target>
              <LocURI>./cimv2/Win32_ComputerSystemProduct</LocURI>
            </Target>
          </Item>
        </Get>
        <Final />
      </SyncBody>
    </SyncML>

    Tuesday, March 4, 2014 6:34 AM

Answers

All replies

  • Hello Sumanthp,
                            Thank you for your inquiry about MS-MDM specification. One of the Open specifications team member will contact you shortly.

     
    Regards,
    Sreekanth Nadendla
    Microsoft Windows Open specifications

    Tuesday, March 4, 2014 2:31 PM
    Moderator
  • Hello Sumanthp

    Thank you for contacting Microsoft Support. I'll be happy to assist and assume that you are interacting with your MDM server implementation during this above scenario. Kindly confirm if this assumption is correct.

    Regards.


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Tuesday, March 4, 2014 5:34 PM
  • Hello Sumanthp - Any update please ?

    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Thursday, March 6, 2014 4:14 PM
  • Hi

    This was an issue with our implementation. Please close this thread. 

    • Marked as answer by sumanthmp Monday, March 10, 2014 9:43 AM
    Monday, March 10, 2014 9:43 AM
  • Hello Sreekanth,

    I am facing similar issue, here is the behaviour description:

    1) Device is enrolled

    2) Client initiates the connection with the MDM server defined in provisioning XML during enrollment.

    3) MDM Server sends some commands as a SyncML response.

     4) Client doesn't respond to these commands or not sending any SyncML. 

    The same is being repeated in all client request. 

    Below is the SyncML for which I am expecting the response from the DM client:

    <SyncML xmlns="SYNCML:SYNCML1.2">
        <SyncHdr>
            <VerDTD>1.2</VerDTD>
            <VerProto>DM/1.2</VerProto>
            <SessionID>1</SessionID>
            <MsgID>1</MsgID>
            <Target>
                <LocURI>9302116</LocURI>
            </Target>
            <Source>
                <LocURI>https://#####</LocURI>
            </Source>
        </SyncHdr>
        <SyncBody>
            <Status>
                <CmdID>1</CmdID>
                <MsgRef>1</MsgRef>
                <CmdRef>0</CmdRef>
                <Cmd>SyncHdr</Cmd>
                <TargetRef>9302116</TargetRef>
                <Data>212</Data>
            </Status>
            <Status>
                <CmdID>2</CmdID>
                <MsgRef>1</MsgRef>
                <CmdRef>2</CmdRef>
                <Cmd>Alert</Cmd>
                <Data>200</Data>
            </Status>
            <Status>
                <CmdID>3</CmdID>
                <MsgRef>1</MsgRef>
                <CmdRef>3</CmdRef>
                <Cmd>Replace</Cmd>
                <TargetRef>./devinf12</TargetRef>
                <Data>200</Data>
            </Status>
            <Get>
                <CmdID>75</CmdID>
                <Item>
                    <Target>
                        <LocURI>./DevDetail/SwV</LocURI>
                    </Target>
                </Item>
            </Get>
        </SyncBody>
    </SyncML>

    Here we had tried sending 

     <Target>
                <LocURI>0</LocURI>
            </Target>

    But it didn't worked.




    Friday, January 16, 2015 10:52 AM
  • Hi, Swapnil

    I see you also asked this question in the new post at https://social.msdn.microsoft.com/Forums/en-US/cd88d7b4-1cfa-4b9e-8de5-61025632b8f7/windows-81-mdm-not-responding-to-first-syncml-from-mdm-server-per-session?forum=os_windowsprotocols.

    For those following this discussion, monitor it in the new thread cited above.


    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team

    Friday, January 16, 2015 6:12 PM
    Moderator
  • Yes Bryan, thought that your team has closed this thread

    Thanks for replying


    Monday, January 19, 2015 11:53 AM