It just shoves you to the next server in line.That's a good idea, however, it would not be suitable for us for two reasons. In RR mode the RDCB does not care which server you get put on it just goes to the next one in line, so it does not keep tabs on if there are existing connections or not. You can terminate disconnected sessions after X amount of time. In light of this, would you have any other recommendations? Therefore, it would be preferable to find a solution without having to set up a separate server as the session broker. I believe the session broker role was set up on one of the terminal servers in order to save cost.įortunately, other than the issue mentioned above, we aren't experiencing any problems with this configuration. If the host was also the broker, we'd have major issues.Yes, both servers are in the same farm and everything else seems to be configured correctly. I also separated the broker and gateway from the hosts because there were instances I had to take a host down for maintenance. I was an administrator of a cloud-hosted RDS farm with 3 hosts and never had this problem with Macs. Are they in the same farm/collection? Is everything correctly configured in the RDP profile in Microsoft Remote Desktop? They should never be able to log into another host in the same farm with a broker. The session broker should be the load balancer and directing where the sessions should go.
#MICROSOFT REMOTE DESKTOP BETA MAC#
So my questions are, why is this occurring? Is there a way to fix it? Or, would it be possible to stop the MRD client on Macs from trying to reconnect users to their existing sessions after they are disconnected? I know there's a way to do this in the Windows client (by unticking 'Reconnect if connection is dropped'), but I haven't been able to find a similar setting in the Mac version. This issue does not occur if users connect to the terminal servers using their public IPs or if they close the session and attempt to reconnect using the domain name. This is how they end up with two sessions, one on each terminal server. Upon entering their login credentials, users are logged on the other server. Unfortunately, MRD often seems to fail to 'negotiate credentials' as it lands users on the login page.
#MICROSOFT REMOTE DESKTOP BETA PC#
"Connection to the remote PC was lost.Upon waking up from sleep, MRD attempts to reconnect to the terminal server. The issue occurs if a user's Macbook goes to sleep. Users connect to the farm using a domain name.
Load balancing is achieved through DNS round robin.Our setup comprises of two terminal servers in a farm (running Win Server 2008 R2), let's call them S1 and S2.This issue only occurs for users that are connecting from Macbooks - they are using Microsoft Remote Desktop for Mac.
0 kommentar(er)
