When you launch a connection from RD Web Access, the prompt that comes up should show the FQDN of your broker for Remote computer. rdp file to use based on your deployment and collection settings that has the target collection embedded within it.
The reason for this is to provide them with an up to date, correctly configured. Another thing about 2012/2012R2/2016 is users are normally expected to launch a connection via RD Web Access or RemoteApp. Without this, when you RDP to the FARM name (which is pointing to RD broker) RDP will send you to the Connection Broker itself and you will get access denied because you have no way of specifying the target collection in the user interface. If manually using the RDP Client to connect is a requirement what you need to do is set the default collection in the RD Connection Broker server’s registry. You can only specify one Default collection. What we need to do is to create a new A record and point it to connection broker and not session host servers. Round robin won’t dynamically route new connections if a host goes down. If you have a special reason to configure it this way you can still do it, but it is not the preferred method.
#Server 2016 remote desktop services retain session id full#
In part 7 we will extend our deployment and add second Session Host server but before we configure and extend our farm we need to make some clarifications about how connection broker will balance sessions between session host servers and what we need to think about when we have users that are using built-in RDP to connect to the farm, as well as remoteapps and full desktop access on the same session host.Īs we know, from server 2012 we should use connection broker to balance sessions between session host servers.
0 kommentar(er)
