![]() Let’s take a look at the first step, preparing the RD Connection Broker HA. ![]() The second step would then be to add one or more additional RD Connection Broker servers to create the actual High Availability. ![]() By completing this first step you create a RD Connection Broker HA ready environment. The locally stored SQL Express database is moved to a central SQL Server instance. This is exactly what the first step does. The first step would obviously be to move that local database to a centrally running instance in order for multiple RD Connection Broker servers to start reading and writing content from and to the database. Without running in HA, the RD Connection Broker places its configuration on a SQL Server Express instance which is running locally on the RD Connection Broker server. The first step is to prepare the environment for HA. After that we’ll dive a little deeper in the configuration and explore the SQL database that gets centrally stored on a SQL Server instance by setting up the High Availability (HA).Ĭonfiguring RD Connection Broker HA is divided into two separate steps. ![]() Along the way, we’ll take a look at some of the pitfalls during the configuration. As a quick recap, we’ll start by summing up the requirements and performing an actual High Availability configuration. In this article we’ll be taking a closer look at the RD Connection Broker configuration and its database. #Windows server 2012 remote desktop management server windows#If you have been following the new features of Windows Server 2012, you’re probably already familiar with the new High Availability features of the RD Connection Broker role in Windows Server 2012. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |