RDP Connections Sessions with no "Collection Name" attached in Connection Broker of Windows Server RDS 2012 R2

Hello,

My newly installed Windows 2012 R2 RDS (remote desktop servers) Connection Broker is having issues with the RDS Session displaying within the created "Collections".

My users are using RDP Client (mstsc.exe on port 3389) and can successfully connect to the 4 RDS Session Hosts (Win 2012 R2) using RDP from the Windows 7 PC's & Wyse TD10 terminals.  (We are not using remote apps nor VDI)
The systems are using DNS Round Robin using the DNS name "RDSFarm" which is pointing to the IP addresses of 4 RDS 2010 R2 Session Hosts, and a seperate Win 2012 R2 Server with Connection Broker.  
All 5 servers are standalone hardware and we are not using HA for the Connection Broker.  
And all servers and users are on the internal domain and have the same internal certificate, which was created on the RDS Connection Broker server, installed.
And I do not have RDS Gateway enabled.

The problem:
On the Win 2012 R2 Connection Broker server, in Server Manager, Remote Desktop Services, Collections, my "created collections" do not show any RDP session connections.  However the connection show directly under the main "Collections" heading and the RDP connections show with no "Collection Name" attached.
The user groups are configured within the properties of the created collections and the Host Servers are populated in the created Collections as well.

I did find an error in the event viewer log on the Connection Broker Server, under "TerminalServices-SessionBroker" stating:
RD Connection Broker failed to process the connection request for user <username1>.
Farm name specified in user's RDP file (hints) could not be found.
Error: The farm specified for the connection is not present."
Event ID: 802

This was working successfully last night, with MS Support watching remotely, and to my knowledge no changes have been made since.
Anthony LarsonIT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
In 2012, you do not create a farm in the same way you did in older versions of windows. EVERYTHING is orchestrated through the connection broker. Basically if you try to manually do things the old way, you'll get odd behavior because the connection broker may not have been made aware of the connection properly. "You must unlearn what you have learned."
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Anthony LarsonIT ManagerAuthor Commented:
I had to contact Microsoft Support and they deleted the Remote Desktop Host Collection within Server Manager, on the Windows 2012 R2 Remote Desktop Connection Broker Server (RDCB) and recreated a new collection and it worked.
They are unsure why the issue occurred or how to really fix it, without just deleting the collection and starting fresh.
0
Anthony LarsonIT ManagerAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for Anthony Larson's comment #a40525038

for the following reason:

Windows 2012 R2 RDHosts with Connection Broker is much different from Windows 2008 R2, and I have found it rather difficult/unstable in setup.
When looking for directions, only use Windows 2012 R2 documentation as it is much different than windows 2008 r2.
0
Anthony LarsonIT ManagerAuthor Commented:
I agree with this statement.  Needed more assistance.
Had to contact Microsoft Support and open a case.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.