How To Install Terminal Services On Server 2016

Accomplished systems and network administrator with ten+ years of feel managing server infrastructures and data-center operations.

how-to-setup-remote-desktop-services-windows-2016

In that location was quite a modify from installing Remote Desktop Services (aka Terminal Services) with the introduction of Windows 2012. It was disruptive, and when you install the Remote Desktop Services host server, there was no longer the familiar Remote Desktop Director, and you could either work through the settings in the registry directly or bring over the remote desktop manager snap-in from Windows 2008R2.

However, that wasn't quite the right way to install Remote Desktop Services on Windows 2012 and later on. This tutorial will show how to install Remote Desktop Services in Windows Server 2016, merely it tin can be practical to Windows 2012 or Windows 2012R2. This tutorial assumes that there are no Windows 2012 or after versions of Remote Desktop Services installation in the Windows domain.

Summary of Steps

The following is a list of steps required to setup Remote Desktop Services. It is more of a checklist.

Pre-installation steps. This is where you determine which servers will hold the RD Session Host Server, RD Connection Broker, RD Web Access server, RD Licensing Manager, and Remote Desktop Gateway roles.
Add servers that will have the roles installed on the list of servers that will exist managed past the Server Manager where nosotros will run the Remote Desktop Services installation magician
Install Remote Desktop Services from Server Manager
Install the RD Connection Banker role on a server
Install the RD Web Admission role on a server
Install the RD Session Host server role on a server
Install the RD Licensing Director role on a server
Create Session Collections
Configure Drove settings
Test Remote Desktop connexion into the RD Session Host Server

Pre-Installation Steps

The Remote Desktop Services installation is a wizard for installing the post-obit roles:

Remote Desktop Gateway
Remote Desktop Session Host Server
Remote Desktop Connection Broker
RD Spider web Access server
RD Licensing Director

We will be installing these roles across multiple servers instead of installing all these roles onto one server.

If yous only take one server to exam on, y'all can install all the roles on the ane server. Yet, for the purpose of trying to understand Remote Desktop Services better, we will install it across multiple servers.

I have already ready the following servers with the below names (highlighted in assuming) and the planned part to be installed on them :

RDGateway: This will accept the Remote Desktop Gateway function, notwithstanding, we won't install it in this tutorial.
RDSessionBroker: This will have the Remote Desktop Connection Broker function
RDServices: This will have the Remote Desktop Session Host Server Function and the RD Web Access part
DC: This volition be a domain controller and will accept the RD Licensing Manager role installed. It is not necessary that this role is installed on a domain controller. However, it makes sense since the domain controller volition withal have the capacity to perform as a licensing server.

Add together Servers to Manage in Server Managing director

I will remote desktop into the RDServices server to do the Remote Desktop services installation.

I will then add the other servers as listed above to be managed.

Open Server Managing director and click on Add together other Servers to manager.

Scroll to Continue

Type in DC (one of the servers to be managed) and click on Find Now — Blazon in DC (ane of the servers to be managed) and click on Discover Now

Highlight the server in the bottom pane, and click on the Right arrow to select the server — Highlight the server in the bottom pane, and click on the Right pointer to select the server

When selected, the server is displayed on the right hand side. Repeat for the other servers to be managed — When selected, the server is displayed on the correct hand side. Repeat for the other servers to be managed

Once the three servers are added, click on OK. We are currently running on the RDServices server, so we don't need to add it to it's own list. — Once the three servers are added, click on OK. We are currently running on the RDServices server, so we don't need to add it to information technology's own list.

Install Remote Desktop Services

Open Server Manager and click on Add roles and features.

Click Next

The following is the almost of import step. While it'south possible to select the Role-based or feature-based installation and then select merely private components of Remote Desktop Services such every bit Remote Desktop Gateway, if you are going to be setting upward a Remote Desktop Services server, you Will NEED to select the Remote Desktop Services installation option.

Select Remote Desktop Services Installation, then click Next.

We volition cull Standard deployment.

Choose Standard deployment and click Next

Select Session-based desktop deployment and click Next

Windows Server 2016 volition at present ask you to install the roles that yous would non unremarkably have installed in Remote Desktop Services for Windows 2008R2.

Click Next

Installing the Remote Desktop Connection Broker server

Select the server that volition have the Connection Broker role ( RDSessionBroker.domain.local in this tutorial) by highlighting it, and clicking the push button with the correct arrow icon.

Install RD Web Admission

Select the RDServices.domain.local by highlighting it, and clicking the button with the right arrow icon.

Install the RD Session Host Servers

Select the server that volition accept the RD Session Host Server role i.e. the server users will be accessing either directly or via a Connexion Broker or Remote Desktop Gateway (RDServices.domain.local in this tutorial) by highlighting it, and clicking the button with the right arrow icon, so click Next

Tick Restart the destination server automatically if required, and click Deploy.

The server will restart upon completion of adding the role services. — The server will restart upon completion of calculation the office services.

Install the RD Licensing Manager

Open Server Manager.

In the left pane, click on Remote Desktop Services.

Click on RD Licensing.

The wizard will display the list of servers we've added to Server Manager. Highlight the server that will have the RD Licensing Director role (dc.domain.local in our tutorial). Click the correct arrow icon to select it.

There is a grace flow of 120 days to use the Remote Desktop Session Host server as a Remote Desktop Server (aka Terminal Server) without pointing it to an RD Licensing Manager with RD CALs installed.

I volition create a followup article on how to add RD CALs.

Create Session Collections

We at present need to create a session drove.

A session collection consists of one or more than Remote Desktop Session Host servers. An RD Session Host server cannot exist a member of more than one collection.

A session drove contains the apps and desktops that you lot desire your users to utilise.

In Windows Server 2008R2, we didn't have to create session collections.

Click on Collections.

From the Tasks dropdown menu, select Create session Collection.

Proper name the Collection

Enter a name for the collection, and click Side by side.

Add RD Session Host Server to Collection

Select RDServices.domain.local for the RD Session Host server to add to the Drove. Click on the button with the correct arrow icon.

Specify User Groups Who can Admission the Collection

We can enable specific groups of users to be able to access this Collection.

Click Add.

Enter the grouping that is allowed to access this drove. Nosotros will remove the Domain Users grouping because we don't necessarily want everyone on the domain to be able to Remote Desktop into the Remote Desktop server.

Specify User Contour Disks

In this tutorial, we won't allow user profile disks for this collection. Some applications may require users to have user profiles to shop temporary files etc. If so, nosotros will demand to enable this option and specify a location to a share that will shop the user profiles. We specify a share since the collection tin can exist hosted on multiple RD Session Host servers and we need to exist able to access the share from any of the RD Session Host servers.

Click Create

Configure Collection Settings

Click on the Applications1 collection on the left pane

In the Tasks driblet downward menu, select Edit Backdrop

The drove's properties window volition appear. Some sections were properties we had already fix during the cosmos of the collection. We tin make changes to those settings here.

For other sections, we can leave as default or alter the settings to suit. For users who take setup Remote Desktop Services for Windows Server 2008R2 before, the sections hither will be familiar as they used to be in the RD Session Host Server's properties.

Remote Desktop into the Collection

The Remote Desktop Services installation is now complete.

Users who are in the group that was allowed access to the collection can at present Remote Desktop to the RD Session Host server which was function of the Applications1 collection. In our tutorial, it's the RDServices.domain.local server.

In this setup, TCP Port 3389 must exist opened on the firewall for connection to the RD Session Host server. Y'all will need to setup any NAT-ing where appropriate on the firewall.

Summary

We have now setup Remote Desktop Services for Windows Server 2016. In this type of Remote Desktop Services setup, the clients will Remote Desktop directly to the RD Session Host server that is office of the collection to employ the applications that are installed on the RD Session Host server.

This article is authentic and true to the best of the writer's cognition. Content is for informational or entertainment purposes just and does not substitute for personal counsel or professional advice in business, financial, legal, or technical matters.

jergomez on December 23, 2019:

Hello Seng

Thank you for this steps. I wanted to know in this scenario, how or where to setup the remote desktop services. i windows 2019 st: domain controller, windows 2019 2 terminal servers with license. Were do we setup terminal service Broker services? on domain controller ? and if this is the case we should come across the two terminal servers to exist added to banker in the drop down as available services? Also I am bold the banker volition perform the "round robin" on proving the admission for users?

Please advise.

Jerry

sengstar2005 (author) from Sydney on November 08, 2019:

Hi Byju, I've got no suggestions other than if you lot want to check the following article on how to setup RDS session broker for Windows 2016 :

http://hub.me/amfc3

Byju on November 08, 2019:

Hi @Sengstar2005,

Thank you for the article. I was non able to observe proper steps for 2016 online.

In my surround I take build RDS in loftier availability for 2012r2. But the same is declining when I am trying to exercise information technology for 2016 datacenter edition. I am able to configure loftier availability just addition of another server is not happening. It keeps failing, I accept checked the permission of the group(session broker servers ad security group) at sql level and information technology has dbowner permission. Merely still while adding the other server in high availability the installation fails.

Any suggestion on this?

sengstar2005 (author) from Sydney on May 28, 2019:

How-do-you-do Jackland, in the old Windows 2008R2 environment, you would but demand to install the RD License server and RD Session Host roles. In Windows 2012 and higher up, information technology is even so possible to install the roles separately i.e. the RD Session Host role (which is what you lot demand to permit User1 to piece of work on App A, User2 to work on App A, etc.. on the same server) and install the RD License server separately. However, the RD Session Host role no longer comes with the nice GUI management interface you see in Windows 2008R2. You lot tin can either change the registry settings directly or port over the RD management tool from Windows 2008R2 server, or merely acquire the new fashion Microsoft wants us to install the RDS services.

Jackland on May 16, 2019:

Hello, I simply need a RD licence server and do not need residue of the stack. the sole intention is to allow 125 users to log on to a windows machine to work on application in independent sessions. like if User1 is working on Application A, User2 should also be able to work on Awarding A. User3 should also be allowed to work on Application A.

Which components of the RDS should I install.

sengstar2005 (author) from Sydney on December 12, 2018:

Hi Al,

It is possible to install only the RDGW and RDWEB roles on the external server. When you utilise the wizard, you can cull to install those 2 roles on the external server, and then choose to install the other roles on your internal servers.

The RDGW volition use the internal DNS server to redirect requests to the internal server.

If you want to understand the principle of how to set it up you tin read the following articles. They were setup for Windows 2008R2 but the principle is the same fifty-fifty though the admin tool to practise it is different from Windows 2016.

When you combine RD Web and RDGW, you can accept your external users scan through to the RD Web. Because it is a Spider web Site, it tin go through their proxy server if they use one. You publish your internal applications on RDWEB, and the RDGW volition redirect requests to those resource.

https://turbofuture.com/computers/How-to-Remote-De...

https://turbofuture.com/computers/Remote-Desktop-v...

Here'southward how to configure a remote desktop gateway in Windows 2016.

https://turbofuture.com/computers/How-To-Setup-a-R...

Al on Dec 06, 2018:

Dearest,

i'm missing some pieces...

I'g trying a soluzione where in DMZ i'v a RDGW/RDWEB on the same server and on the internal network the RDSH and RDLS.

1- is it possible to install merely RDGW and RDWEB roles on the external server?

2- How to tell the perimeter server to redirect the requests to the internal server?

sengstar2005 (author) from Sydney on August 05, 2018:

Thanks Zoshef.

Zoshef Anzum on August 05, 2018:

Thank you for your information. Very impressive and detailed.