RDS (Remote Desktop Services) is the successor of TSE (Terminal Server) technology that you may have heard about in Windows Server 2003.
With RDS, you can provide desktops (based on Terminal Server sessions or virtual machines) or applications to your users without having to install them on each client workstation.
Indeed, thanks to RDS, you will be able to install all the applications on one or several servers (to ensure a better quality of service and to obtain a better fault tolerance), then to make them accessible at a distance to your users in a completely transparent way.
Note that the applications that you provide to your users will be called RemoteApp and will have to be installed with a special licensing mode called Volume Licensing (VL).
This will be especially the case for applications created by Microsoft, such as Microsoft Office, for example.
That being said, in this first tutorial, we will only publish a collection of session-based desktops.
A RDS infrastructure consists of one or more servers on which you will install one or more RDS role services.
For most of our tutorials about RDS, we will use :
Note that Remote Desktop Services can't work without linking your different RDS servers to your Active Directory.
If you use the Add Roles and Features Wizard, you will see that Remote Desktop Services consists of several role services :
Note that the VDI will be the subject of separate tutorials, as it also requires the installation and configuration of a Hyper-V virtualization server.
To begin, we'll explain how to install and configure a basic RDS infrastructure to provide session-based desktops to your users.
To avoid getting errors when deploying Remote Desktop Services (RDS), we recommend that you log in with a Domain Administrator account and install the "Remote Desktop Connection Broker" role service first.
Select "Role-based or feature-based installation".
Select your future RDS server.
Check the "Remote Desktop Services" box.
As mentioned earlier, Remote Desktop Services gives your users access to :
Check the "Remote Desktop Connection Broker" role service.
As you can see, adding this role service will also add the "Windows Internal Database" feature.
Note : if you deploy RDS services directly without first installing the broker, you may get these errors :
Unable to install RD Connection Broker role service on server ...
These errors are due to the fact that the "Windows Internal Database" service did not start correctly.
To avoid this problem, we install the Broker before deploying RDS and these errors will not appear.
Once the box is checked, click Next.
The installation starts.
When the installation is complete, click Close.
From the Windows Server 2012 modern interface, type services and click on the program of the same name.
In the list, check that the "Windows Internal Database" service is running.
Windows Server 6/22/2019
Windows Server 1/25/2019
Windows Server 6/7/2019
Windows Server 5/3/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.