Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, September 20, 2017 1:19 PM
Hi,
I am very confused by session host load balancing in 2012 R2 and 2016. According to this link we should create a DNS record that is the name of the collection and that dns record needs to point to connection broker ip address.
https://social.technet.microsoft.com/Forums/en-US/2ec5e96e-7ca6-44b5-85f8-5286c6881dea/2012-r2-loadbalanced-rds-farm?forum=winserverTS
That is wrong because if you specify connection broker ip address you will go to broker and because we don't have access we will get access denied. I think that DNS should point to session host servers and not the broker ip. I tried and it is not working if I specify broker ip.
All replies (15)
Wednesday, September 20, 2017 1:41 PM
If you have an RDS farm then the broker should indeed be the DNS record used. The Connection Broker performs the loadbalancing. Have a look at the below articles:
https://thewolfblog.com/2014/02/08/deploying-a-2012-2012r2-remote-desktop-services-farm/
Ensure you are connecting with the published RDP file from the RDS farm. Using a regular Remote Desktop attempt may not yield the expected results.
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
Wednesday, September 20, 2017 1:43 PM
Hi,
The second link was the same I posted and that is confusing me. If you create a dns record and point to broker you will get access denied because no regular user can connect to broker server.
Wednesday, September 20, 2017 1:56 PM
Hi,
The second link was the same I posted and that is confusing me. If you create a dns record and point to broker you will get access denied because no regular user can connect to broker server.
But when the Connection Broker is configured correctly it will forward the requests to the Session Host Servers. Have you added the connection broker in the farm config?
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
Wednesday, September 20, 2017 2:05 PM
Hi,
What do you mean by farm config? I created rds with standard method. I have rdcb, and 2 session host servers. Then I created a collection and added the host to it. Next I created dns record (name is the same as the collection) and point to rd broker ip address and when I try to connect I get access denied.
Wednesday, September 20, 2017 2:13 PM
Hi,
What do you mean by farm config? I created rds with standard method. I have rdcb, and 2 session host servers. Then I created a collection and added the host to it. Next I created dns record (name is the same as the collection) and point to rd broker ip address and when I try to connect I get access denied.
Can you verify you have followed the steps in the below article? By farm config I mean the RDS farm config, not just the collection of session hosts. Is your broker added as a broker to the farm? It seems that your connection broker is not functioning as a session broker,it should not be accepting RDP connections directly, it should be forwarding to your session host servers. If you configure your DNS record to point at your session hosts and simply RDS to it you will lose the core load-balancing and fault tolerance functionality of the Connection Broker. You can also test it for yourself by using the RD Web Server role.
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
Wednesday, September 20, 2017 2:24 PM
Hi,Yes, everything is configured good. If I am not wrong if we have 2 group of users and 2 session host servers. If I want that group 1 connects to server 1 then I create a collection and add only that session host to it. When users are connecting to session host they are specifying the session host ip address and broker knows if they have right to access or not. Is it not the same if I have 2. Link that I provided and you as well showing that a lot of users have the same issue and I think that we are not able to specify broker ip address in dns record coz we don't have access to broker. I have never seen post on internet that is showing that configuration, step-by-step.
Link you provided is for connection broker load balancing not session host load balancing
Wednesday, September 20, 2017 2:28 PM
Hi,Yes, everything is configured good. If I am not wrong if we have 2 group of users and 2 session host servers. If I want that group 1 connects to server 1 then I create a collection and add only that session host to it. When users are connecting to session host they are specifying the session host ip address and broker knows if they have right to access or not. Is it not the same if I have 2. Link that I provided and you as well showing that a lot of users have the same issue and I think that we are not able to specify broker ip address in dns record coz we don't have access to broker. I have never seen post on internet that is showing that configuration, step-by-step.
Link you provided is for connection broker load balancing not session host load balancing
I know it's for connection broker load balancing but we need to ensure that you have added the connection broker to the RD Farm Config through server manager. Can you confirm?
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
Wednesday, September 20, 2017 2:32 PM
Yes,
I have added all servers to server manager and configured rds from connection broker server.
Wednesday, September 20, 2017 2:36 PM
Great,
The DNS record 100% needs to point to connection broker. Without seeing the environment I cannot say for sure what is wrong. I advise following the steps in the below article to verify you have everything required.
https://geekdudes.wordpress.com/2017/01/21/remote-desktop-services-lab-on-windows-server-2016/
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
Thursday, September 21, 2017 6:10 AM
Hmmm I have configured that way but cannot get to work if dns record points to connection broker. Access denied is the message I get. Anyone else who can jump in and help
Thursday, September 21, 2017 9:50 AM | 2 votes
Hi,
Since Windows Server 2012, it's intended to have users connecting to RD resources via RD Web Access page, .rdp file downloaded from the page or RemoteApp and Desktop Connections configured via Control Panel or Group Policy, as RD Web plug-in would generate proper .rdp files.
If you'd like to get it to work by connecting to RD Connection Broker directly with mstsc.exe, you may configure default collection on RD Connection Broker via registry below:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings
DefaultTsvUrl REG_SZ tsv://MS Terminal Services Plugin.1.<Collection Alias>
You may find more details from TP's replies within this thread below:
Connection Broker (Server 2012) what server to connect to
Best Regards,
Amy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thursday, September 21, 2017 11:29 AM
Hi Amy,
According to the post you posted I need to configure default collection and edit the rdp file which I download from web access. Our users are not going to use web access role and what if I have 2 collections with 2 session host in each. How to specify default collection if there are 2?
According to your post I don't need to create dns record which points to broker if I specify default colelction, right?
Friday, September 22, 2017 10:08 AM | 1 vote
According to the post you posted I need to configure default collection and edit the rdp file which I download from web access. Our users are not going to use web access role and what if I have 2 collections with 2 session host in each. How to specify default collection if there are 2?
According to your post I don't need to create dns record which points to broker if I specify default colelction, right?
Hi,
There is no need to modify .rdp file downloaded from RD Web Access, as it's generated properly.
After default connection is configured, you can connect to the default connection via mstsc.exe by typing the collection name (specified within registry above).
If there are multiple collections, as this method only redirects users to default collection, users would need to connect via RD Web related methods that I mentioned above to connect to non-default collections.
If for some reason users are not able to access RD Web Access page or configure RemoteApp and Desktop Connections/Remote Resources, you may download .rdp files then distribute them to clients.
One DNS Host record is needed, which is the collection name pointing to the IP address of RD Connection Broker server.
Best Regards,
Amy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Tuesday, September 26, 2017 2:10 AM
Hi,
Please remember to mark useful reply as answer, which would be much more efficient for other forum community members to find useful information.
Best Regards,
Amy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Tuesday, October 3, 2017 3:02 AM
Hi,
I am checking to see how things are going there on this query.
Please feel free to let us know if further assistance is required.
Best Regards,
Amy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.