locked
WS-Discovery and Multipoint on Windows 2016 RRS feed

  • Question

  • Hello

    The WS-Discovery capability is used by one of our thin client model to discover Multipoint servers over the local network.
    Actually a WS-Discovery request is sent by our thin client (unicast or broadcast mode). And response(s) is/are parsed to find out Multipoint servers.

    This discovery mechanism worked with MultiPoint 2011 & 2012.

    But it seems it no longer works with the MutlPoint Role installed on a server 2016.

    Note: it was working with server 2016TP5.

    But a 'netstat - a' command issues on the server 2016 shows the UDP port 3702 is currently listened.

    Do you have any idea about that?
    Is there something to enable?

    If needed, I can give you the WS-Discovery request sent by our thin client.

    Regards

    Vincent



    Wednesday, October 26, 2016 8:35 AM

Answers

  • Hi Vincent,

    As it turns out, the following Scope is used for discovering MultiPoint 2011 & 2012 servers:

    http://www.microsoft.com/windowsserver/discovery/StationHostManagement

    However, since there is no cross-compatibility with Multipoint Services in Server 2016, you need a different scope for discovering Multipoint services in Server 2016:

    http://www.microsoft.com/windowsserver/discovery/StationHostManagement2016.

    Also, if the Multipoint Connecter feature is installed on Server 2016, the scope is:

    http://www.microsoft.com/windowsserver/discovery/MultiPointConnector2016

    Hope that helps!


    Jeff McCashland | Microsoft Protocols Open Specifications Team

    Tuesday, November 29, 2016 8:01 PM

All replies

  • Hi Vincent,

    Thank you for your question.  An engineer from the protocols team will contact you soon.


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

    Wednesday, October 26, 2016 3:16 PM
  • Hi Vincent,

    I would like to assist you with this issue. Please email me at dochelp at Microsoft dot com so that I can send you information to upload your WS-Discovery request trace. Also, please include any additional details around configuration and repro steps that may be relevant.

    Thank you,


    Jeff McCashland | Microsoft Protocols Open Specifications Team

    Wednesday, October 26, 2016 4:56 PM
  • Hi Vincent,

    As it turns out, the following Scope is used for discovering MultiPoint 2011 & 2012 servers:

    http://www.microsoft.com/windowsserver/discovery/StationHostManagement

    However, since there is no cross-compatibility with Multipoint Services in Server 2016, you need a different scope for discovering Multipoint services in Server 2016:

    http://www.microsoft.com/windowsserver/discovery/StationHostManagement2016.

    Also, if the Multipoint Connecter feature is installed on Server 2016, the scope is:

    http://www.microsoft.com/windowsserver/discovery/MultiPointConnector2016

    Hope that helps!


    Jeff McCashland | Microsoft Protocols Open Specifications Team

    Tuesday, November 29, 2016 8:01 PM