Solved

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

Posted on 2014-09-04
4
1,492 Views
Last Modified: 2014-12-30
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.
0
Comment
Question by:Anthony Larson
  • 3
4 Comments
 
LVL 56

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 40304346
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
 

Author Comment

by:Anthony Larson
ID: 40525038
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
 

Author Comment

by:Anthony Larson
ID: 40525040
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
 

Author Closing Comment

by:Anthony Larson
ID: 40525041
I agree with this statement.  Needed more assistance.
Had to contact Microsoft Support and open a case.
0

Join & Write a Comment

Understanding the various editions available is vital when you decide to purchase Windows Server 2012. You need to have a basic understanding of the features and limitations in each edition in order to make a well-informed decision that best suits y…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now