none
Where can find the Sepcification for 'Virtual Machine Remote Client' Protocol? RRS feed

  • Question

  • Hi All
        I would like to know Where can find the Sepcification for 'Virtual Machine Remote Client' Protocol?. Is this specification open for public?

    Thanks in Advance.
    Thursday, November 6, 2008 2:34 AM

Answers

  •  

    PC Varma,

     

    The VMRC client shipped with Virtual Server 2005 and is not supported under the open protocols documentation which is why a document is not published under that license.  Having said that, the VMRC client utilizes an implementation of the VNC which is based on the RFB Protocol that has some additions to make it more secure. 

     

    Windows Server 2008 ships with virtualization as a role called Hyper-V.  That component utilizes RDP and documentation can be found in the following two MCPP documents

    ·         [MS-RDPEPS]: Remote Desktop Protocol: Session Selection Extension http://msdn.microsoft.com/en-us/library/cc242359.aspx

    ·         [MS-RDPBCGR]: Remote Desktop Protocol: Basic Connectivity http://msdn.microsoft.com/en-us/library/cc240445.aspx

     

    Richard Guthrie

    Escalation Engineer

    Wednesday, November 19, 2008 10:25 PM
  • Hi Slchen,

    I researched this issue for you because my teammate was tied up with other assignments. 

    The RDP scenario you described does not appear to be related to session selection. RDP Session selection is used in Windows HyperV environment to select the virtual machine (VM) to connect to among multiple VMs present on the host machine.

     [MS-RDPEPS] — v20101001 – Excerpt

    1.6 Applicability Statement

    This protocol is applicable when there is a need to allow multiple processes to accept connections on the same TCP/IP port.

    - End Excerpt

    MS-RDPEPS defines the PDUs in RDP that helps VMMS.exe (of HyperV) bind a connection from a VMConnect to the appropriate VMWP.exe. The session selection occurs with the exchange of pre-connection PDU (ref. [MS-RDPEPS] Section 2.2.1). The Id (v1) and the wszPCB (v2) fields are used to identify the RDP source process and the connection is handed over that that process. The wszPCB string represents the GUID of the virtual machine to which the client tries to connect. The server uses the GUID to identify the virtual machine the connection is intended for.

    Currently, RDP session selection only works with HyperV servers to connect to VMs. Terminal services servers do not support RDP session selection.

     

    The scenario you described seems related to terminal services (remote desktop services) reconnection to disconnected sessions, and this has no bearing with RDP session selection.

     

    Additional resources:

     

    Windows Server Forums > Remote Desktop Services (Terminal Services)

    http://social.technet.microsoft.com/Forums/en-US/winserverTS/threads

    Remote Desktop Services (Terminal Services) Team Blog

    http://blogs.msdn.com/b/rds/

    Overview of Remote Desktop Connection Broker (RD Connection Broker)

    http://technet.microsoft.com/en-us/library/cc772245.aspx

    Remote Desktop Connection Broker

    http://technet.microsoft.com/en-us/library/dd560675(WS.10).aspx

    Terminal Services Session Broker (TS Session Broker)

    http://technet.microsoft.com/en-us/library/cc731045(WS.10).aspx

    TS Session Broker Load Balancing Step-by-Step Guide

    http://technet.microsoft.com/en-us/library/cc772418(WS.10).aspx

    TS Session Broker

    http://technet.microsoft.com/en-us/library/cc732594(WS.10).aspx

     

    Regards,

    Edgar

    Tuesday, October 26, 2010 4:13 PM
    Moderator

All replies

  •  

    Good Morning PC Varma:

    I have alerted our Protocols Support team concerning your questions about 'Virtual Machine Remote Client' Protocol. One of our team members will be in contact with you soon.

    Thanks for your questions!


    Regards, Obaid Farooqi
    Thursday, November 6, 2008 4:46 PM
    Owner
  • Hi Obaid Farooqi
        Thanks for your quick response. pc.varma@hotmail.com is my email id for furthur contact. I have one question, Does the same VMRC protocol supports "VMWare Remote Client by vmware.com"?

    Thanks in advance.

    Saturday, November 8, 2008 12:53 PM
  • Good Afternoon PC Varma:
    I have alerted the team member who is researching your question about your new query  and your email address. The research on your question is in progress and we'll update you when our research is complete.

    Thanks for your question.
    Regards, Obaid Farooqi
    Saturday, November 8, 2008 6:39 PM
    Owner
  •  Hi Obaid Farooqi
        Any update on this request? Thanks in advance.
    Saturday, November 15, 2008 5:25 AM
  •  

    PC Varma,

     

    The VMRC client shipped with Virtual Server 2005 and is not supported under the open protocols documentation which is why a document is not published under that license.  Having said that, the VMRC client utilizes an implementation of the VNC which is based on the RFB Protocol that has some additions to make it more secure. 

     

    Windows Server 2008 ships with virtualization as a role called Hyper-V.  That component utilizes RDP and documentation can be found in the following two MCPP documents

    ·         [MS-RDPEPS]: Remote Desktop Protocol: Session Selection Extension http://msdn.microsoft.com/en-us/library/cc242359.aspx

    ·         [MS-RDPBCGR]: Remote Desktop Protocol: Basic Connectivity http://msdn.microsoft.com/en-us/library/cc240445.aspx

     

    Richard Guthrie

    Escalation Engineer

    Wednesday, November 19, 2008 10:25 PM
  • Hello all,

    I am wondering how the session selection extension works in a real case?

    Is the following situation a session selection?

    1. The server have 3 disconnected sessions for a user named user1

    2. The client connect to the server and type user1 as the username with the correspond password.

    3. The display shows a dialog with 3 disconnections with "session number", "resolution", "last connected time".

    4. user1 choose the prefered session and the session is connected after the prefered session is choosen.

    The above case also works on Windows 2003 but the MS-RDPEPS said that "Session Selection" work on Vista, Windows 2008, and Windows 7.

    So I don't know what is the "Session Selection" and how it works? Thank you very much.

    Tuesday, October 12, 2010 2:12 AM
  • Slchen,

     

    Thank you for your question.  Someone from the Protocols team will follow-up with you.

     


    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team
    Tuesday, October 12, 2010 4:47 AM
    Moderator
  • Hi Slchen:

    I have taken the ownership of this issue. I'll post my answer here as soon as I finish my investigation. Please feel to get in touch if you have any clarification/question regarding this issue through this thread.


    Regards, Obaid Farooqi
    Tuesday, October 12, 2010 4:18 PM
    Owner
  • Hi Slchen,

    I researched this issue for you because my teammate was tied up with other assignments. 

    The RDP scenario you described does not appear to be related to session selection. RDP Session selection is used in Windows HyperV environment to select the virtual machine (VM) to connect to among multiple VMs present on the host machine.

     [MS-RDPEPS] — v20101001 – Excerpt

    1.6 Applicability Statement

    This protocol is applicable when there is a need to allow multiple processes to accept connections on the same TCP/IP port.

    - End Excerpt

    MS-RDPEPS defines the PDUs in RDP that helps VMMS.exe (of HyperV) bind a connection from a VMConnect to the appropriate VMWP.exe. The session selection occurs with the exchange of pre-connection PDU (ref. [MS-RDPEPS] Section 2.2.1). The Id (v1) and the wszPCB (v2) fields are used to identify the RDP source process and the connection is handed over that that process. The wszPCB string represents the GUID of the virtual machine to which the client tries to connect. The server uses the GUID to identify the virtual machine the connection is intended for.

    Currently, RDP session selection only works with HyperV servers to connect to VMs. Terminal services servers do not support RDP session selection.

     

    The scenario you described seems related to terminal services (remote desktop services) reconnection to disconnected sessions, and this has no bearing with RDP session selection.

     

    Additional resources:

     

    Windows Server Forums > Remote Desktop Services (Terminal Services)

    http://social.technet.microsoft.com/Forums/en-US/winserverTS/threads

    Remote Desktop Services (Terminal Services) Team Blog

    http://blogs.msdn.com/b/rds/

    Overview of Remote Desktop Connection Broker (RD Connection Broker)

    http://technet.microsoft.com/en-us/library/cc772245.aspx

    Remote Desktop Connection Broker

    http://technet.microsoft.com/en-us/library/dd560675(WS.10).aspx

    Terminal Services Session Broker (TS Session Broker)

    http://technet.microsoft.com/en-us/library/cc731045(WS.10).aspx

    TS Session Broker Load Balancing Step-by-Step Guide

    http://technet.microsoft.com/en-us/library/cc772418(WS.10).aspx

    TS Session Broker

    http://technet.microsoft.com/en-us/library/cc732594(WS.10).aspx

     

    Regards,

    Edgar

    Tuesday, October 26, 2010 4:13 PM
    Moderator
  • Hi  Edgar A Olougouna

    Good Evening.

                          we follow the above instructions,but we were unable to connect virtual machine on Hyper V.

    so could you please give me some other suggestions.

     Thanks in Advance.


    Friday, November 18, 2011 12:49 PM
  • Hi Thiru464,

     

    Thanks for your inquiry.

    Someone from our team will contact you shortly.

     

    Regards,

     

     


    SEBASTIAN CANEVARI - MSFT Escalation Engineer Protocol Documentation Team
    Friday, November 18, 2011 3:33 PM
  • Hi Sebastian Canevari!

           Thanks For your Response.

    Sunday, November 20, 2011 9:48 AM
  • Thiru464,

     

    I can work with you on this.  Can you send me mail via "dochelp (at) microsoft (dot) com" and describe what you are trying to do and the issue you are having?

     

     


    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team
    Thursday, November 24, 2011 12:51 AM
    Moderator
  • Thiru464,

     

    I didn't see mail regarding this.  I'm going to close this issue.  However, if you continue to have an issue, please contact us via "dochelp (at) microsoft (dot) com".  Please describe what you are trying to do and the issue you are having and we can re-engage?

     


    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team
    Friday, December 2, 2011 9:31 PM
    Moderator