RD Connection Broker requires an Active Directory domain, but cannot be installed on a domain controller (DC). RD Connection Broker uses the Windows Internal database to store session and configuration information, except when installed in high availability (HA) mode where SQL Server 2008 R2 (or later) is used. Starting in Windows Server 2012, RD Connection Brokers not only store user session data, but also configuration information. When establishing new sessions, RD Connection Brokers also perform a role by connecting users to RD Session Host servers under the least load. This information is used to connect users to existing sessions, should they exist, on RD Session Host servers. To keep track of user sessions, RD Connection Brokers store information such as the name of the RD Session Host server where each session resides, session state and ID, and the user logged in to each session. When a remote desktop session is disconnected, the apps in the user’s session continue to run. Before you plan a RDS deployment, it’s important to understand the role of the RD Connection Broker. But even in a single-server deployment scenario, an RD Connection Broker is mandatory. RD Session Hosts perform the dirty work by serving up your users’ terminal services sessions. Remote Desktop Services in Windows Server has improved over the years, but can be difficult to understand because of the many components involved.
In today’s Ask the Admin, I’ll explain how RDS Session Host deployment in Windows Server 2012 R2 differs from earlier versions of Windows Server and the deployment options available.
0 kommentar(er)
