we are building a Server 2012 R2 Remote Desktop Services Collection, with a single connection broker and two session broker servers. We find that we can only connect to the session brokers if we use the RDP shortcut generated by the Web access component within our deployment. if we try a "normal" RDP connection, it tries to connect to the connection broker only, and fails as the user is not a member of the remote desktop users group. if we try the RDP link generated by the RD Web Access component, it connects as it should do. is there something I am missing that is contained in the generated RDP link that a normal RDP connection doesn't have?