When you want to implement an RDS (Remote Desktop Services) infrastructure in a production environment, it's important that it's highly available.
To do this, you will need to make sure that there is no single point of failure that can knock down your RDS infrastructure.
Warning: this tutorial is very long and refers to many concepts related mainly to RDS.
We therefore recommend that you first learn how RDS works, through our previous tutorials, before attempting to implement its high availability.
In addition, we apologize in advance for the length of the tutorial, but it's the minimum necessary (for RDS*) so that your RDS infrastructure is fully highly available.
* The Active Directory server and the SQL database installed on the same server are not replicated in this tutorial, as this will lengthen it with concepts specific to Active Directory Services and SQL Server.
Nevertheless, in production, it's obvious that you will have to implement the replication of your Active Directory, as well as of your SQL database (on which depends the broker of your RDS infrastructure) so that your infrastructure is completely highly available.
Without these additional replications, the Active Directory (physical) server used in this tutorial would be a single point of failure.
As for the RDS infrastructure, we will use 5 servers :
2 servers running Windows Server 2012 that will be fully redundant for all RDS services (except the virtualization host) :
2 RDS gateway servers (if you want to provide secure access from the Internet to your RDS infrastructure) which will also be redundant.
For client PCs, we will only use 1 client under Windows 8.
To get started, log in with a domain administrator account and install Remote Desktop Services on your 1st RDS server through the "Remote Desktop Services installation" option.
Choose : Standard Deployment.
Choose : Session-based desktop deployment.
The wizard displays a description of the different roles.
For more information about these RDS roles, refer to our "RDS - Deploy a RDS infrastructure (session-based desktops)" tutorial.
Select your 1st RDS server and click on the arrow in the center.
Then, click Next.
Check the "Install the RD Web Access role service ..." check box on your 1st RDS server and click Next.
Select your 1st RDS server again and move it to the right.
At the end, the wizard will deploy the Broker service, web access and session host on your 1st RDS server.
Check the "Restart the destination server automatically if required" box and click Deploy.
Wait while deploying and installing Remote Desktop Services on your 1st RDS server.
When the deployment is complete, click Close.
For the configuration of your 1st RDS server, follow our tutorial "RDS - Deploy a RDS infrastructure (session-based desktops)" up to step 6 included.
Once you have followed the tutorial mentioned above, your license server will be activated and configured correctly.
You will have created a share on your Active Directory server for user profile disks of the RDS collection.
You will have created a collection hosted by your 1st RDS server.
The collection should not contain any RemoteApp programs.
Indeed, these can be published only after adding all the desired session host servers to this collection.
For the moment, your collection will be hosted by a single session host server.
Windows Server 8/27/2014
Windows Server 2/16/2019
Windows Server 5/24/2019
Windows Server 2/1/2019
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2020 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.