We want to have 2 collections, each consisting of 1 RD Session host running Server 2012. We want it this way because each one is running significantly different applications for a different user base.
Do we need to have a connection broker for each collection in this senario?
We have deployed a set of servers with just one connection broker, but are now seeing a few side effects in the event logs and in the Server Manager. Our current setup has the 2012 servers:
- dc ( domain controller, DNS, DHCP )
- office ( RD license server, RD web access, RD connection broker, RD Session Host in collection A )
- mill-control ( Session Host in collection B )
Our issues that we can see are
- The session host server in collection A displays the list of current users while the other does not. This is the case when looking at server manager on any of the servers.
- The event logs on the mill-control server under "Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational" error Event IDs 1296 "Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker" and 1306 "Remote Desktop Connection Broker Client failed to redirect the user Domain\Username"
- The event logs on the server "office" under "Microsoft-Windows-TerminalServices-SessionBroker/Operational" Warning Event ID 1016 "RD Connection Broker service denied the remote procedure call (RPC) from an unauthorized computer {IP of mill-control server}."