How to Setup Remote Desktop Services in Windows Server 2016

Updated on August 28, 2018

There was quite a change from installing Remote Desktop Services (aka Terminal Services) with the introduction of Windows 2012. It was confusing, and when you install the Remote Desktop Services host server, there was no longer the familiar Remote Desktop Manager, 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. This tutorial will show how to install Remote Desktop Services in Windows Server 2016, but it can be applied to Windows 2012 or Windows 2012R2. This tutorial assumes that there are no Windows 2012 or later version 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.

  1. 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.
  2. Add servers that will have the roles installed on the list of servers that will be managed by the Server Manager where we will run the Remote Desktop Services installation wizard
  3. Install Remote Desktop Services from Server Manager
  4. Install the RD Connection Broker role on a server
  5. Install the RD Web Access role on a server
  6. Install the RD Session Host server role on a server
  7. Install the RD Licensing Manager role on a server
  8. Create Session Collections
  9. Configure Collection settings
  10. Test Remote Desktop connection into the RD Session Host Server

Pre-Installation Steps

The Remote Desktop Services installation is a wizard for installing the following roles:

- Remote Desktop Gateway
- Remote Desktop Session Host Server
- Remote Desktop Connection Broker
- RD Web Access server
- RD Licensing Manager

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

If you only have one server to test on, you can install all the roles on the one server.

However, for the purpose of trying to understand Remote Desktop Services better, we will install it across multiple servers.

I have already setup the following servers with the below names (highlighted in bold) and the planned role to be installed on them :

RDGateway - this will have the Remote Desktop Gateway role, however, we won't install it in this tutorial. Here is a link to an article on how to install Remote Desktop Gateway for Windows Server 2016.

http://hub.me/alW4n


However, this linked article uses the Role-based or feature-based installation option from the Add roles and features wizard to install the role. This method still works for Remote Desktop Gateway in Windows 2016.

I will create a follow up article on installing Remote Desktop Gateway from the Remote Desktop Services installation wizard.

RDSessionBroker - this will have the Remote Desktop Connection Broker role

RDServices - this will have the Remote Desktop Session Host Server Role and the RD Web Access role

DC - this will be a domain controller and will have 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 will still have capacity to perform as a licensing server.

Add Servers to Manage in Server Manager

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 Manager and click on Add other Servers to manager

Type in DC (one of the servers to be managed) and click on Find Now
Type in DC (one of the servers to be managed) and click on Find 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 arrow 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 right 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 it's own list.

Install Remote Desktop Services

Open Server Manager and click on Add roles and features.

Click Next

The following is the most important step. While it’s possible to select the Role-based or feature based installation and then select just individual components of Remote Desktop Services such as Remote Desktop Gateway, if you are going to be setting up 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 will choose Standard deployment.

Choose Standard deployment and click Next

Select Session-based desktop deployment and click Next

Windows Server 2016 will now ask you to install the roles that you would not normally have installed in Remote Desktop Services for Windows 2008R2.

Click Next

Installing the Remote Desktop Connection Broker server

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

Click Next
Click Next

Installing RD Web Access

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 will have the RD Session Host Server role i.e. the server users will be accessing either directly or via a Connection Broker or Remote Desktop Gateway (RDServices.domain.local in this tutorial) by highlighting it, and clicking the button with the right arrow icon, then click Next

Click Next
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 adding the role services.

Installing 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 Manager role (dc.domain.local in our tutorial). Click the right arrow icon to select it.

Click Next
Click Next
Click Add
Click Add
Click Close
Click Close

There is a grace period 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 will create a followup article on how to add RD CALs.

Creating Session Collections

We now need to create a session collection.

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

A session collection contains the apps and desktops that you want your users to use.

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

Click on Collections.

From the Tasks dropdown menu, select Create session Collection.

Click Next
Click Next

Name the Collection

Enter a name for the collection, and click Next.

Add RD Session Host Server to Collection

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

Click Next
Click Next

Specify User Groups Who can Access the Collection

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

Click Add.

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

Highlight Domain Users and click Remove
Highlight Domain Users and click Remove
Click Next
Click Next

Specify User Profile Disks

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

Untick the box and click Next
Untick the box and click Next

Click Create

Click Close
Click Close

Configure Collection Settings

Click on the Applications1 collection on the left pane

In the Tasks drop down menu, select Edit Properties

The collection's properties window will appear. Some sections were properties we had already set during the creation of the collection. We can make changes to those settings here.

For other sections, we can leave as default or alter the settings to suit. For users who have setup Remote Desktop Services for Windows Server 2008R2 before, the sections here 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 now Remote Desktop to the RD Session Host server which was part of the Applications1 collection. In our tutorial, it’s the RDServices.domain.local server.

In this setup, TCP Port 3389 must be opened on the firewall for connection to the RD Session Host server. You 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 part of the collection to use the applications that are installed on the RD Session Host server.

© 2018 sengstar2005

Comments

    0 of 8192 characters used
    Post Comment

    • profile image

      Al 

      5 days ago

      Dear,

      i'm missing some pieces...

      I'm 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 only RDGW and RDWEB roles on the external server?

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

    • sengstar2005 profile imageAUTHOR

      sengstar2005 

      4 months ago from Sydney

      Thanks Zoshef.

    • profile image

      Zoshef Anzum 

      4 months ago

      Thanks for your information. Very impressive and detailed.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, turbofuture.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://turbofuture.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)