#Windows terminal services server install
#Windows terminal services server update
#Windows terminal services server windows

pfx format and you need to have the private key in it. In my case I will use my private CA. This certificate needs to contain the FQDN you will use as the RD Web Access URL (mine is ). In real life you would purchase this certificate from a public CA (GoDaddy,VeriSign etc.).

We receive this error message because we didn’t configure certificate which is our second prerequisite. Type in credentials and hit OK and you will run into this error. Type in RDCB name and click on Advanced TabĪdvanced –> Settings and specify RD Gateway and click OK and Connect. Let’s try to connect to RDCB with RDP. Just open Run (Windows Button + R) and type in mstsc. Now if I try to ping from my “External Machine” ping will work. In my case I am not running NAT and I am not running firewalls so I will put in its internal IP In real life you would type in the external IP address of your NAT router or the firewall, public IP that is closest to the gateway. Once finish, right-click on the new zone and select New Host (A or AAAA)

#Windows terminal services server update

On Zone File, Dynamic Update page accept the defaults and click Finish On Zone Name page, type in your zone name, In my case and click next On Zone Type page accept the defaults and click next. On Welcome to the New Zone Wizard page click next. Right-Click on Forward Lookup Zones and select New Zone Open DNS Manager and browse to Forward Lookup Zones.

#Windows terminal services server windows

If I try to ping my gateway from external Windows 10 machine the ping will fail. In this case my “external DNS” (ROUTER -machine on my external network) will handle DNS for the external network.

You will configure it on your external DNS (hosted dns or DNS out on your ISP) somebody that we do not have the control over but that is accessible from the internet. As it said in the wizard, the external FQDN should be on the certificate.īefore we create new certificate, we need to configure DNS so that external users can resolve the name of the RD Gateway to the right IP address.

#Windows terminal services server install

Either install the self-signed certificate on all clients, or use a certificate for which the complete certificate chain is already trusted by all clients. Notice that the certificate level currently has a status of Not Configured. The RD Gateway certificate is used for Client to gateway communication and needs to be trusted by the clients. ( OBS!!! I will talk more about Deployment Properties in Exploring Deployment Properties series) Hit Next and Add. Wait until the role service is deployed and click on the Configure Certificate to review Certificate Options On SSL Certificate Name page, I will type in Fully Qualified Domain Name of my RDS server I will replace that certificate with Trusted one a little bit later. When we go through the wizard it’s gonna create a self-signed SSL certificate. Click the Add RD Gateway server green button. (I will talk more about Collections and Collection Properties in my Purpose of RD Collections post).Īs you can see the deployment is missing a RD Gateway server and a RD Licensing server.Ĭlick the Add RD Licensing server green button.Ĭonfirm selections and click add. Wait until the role service is deployed and click Close. When you choose Quick Deployment type, Collection (QuickSessionCollection) and Remote App Programs are already configured.Ĭollections separate out RD Sessions Hosts into separate farms and allow admins to organize resources. When you click on it, you will find your self in front of “RDS Manager”. We can access Remote Desktop Services through Server Manager if we click on Remote Desktop Service link in the left pane. When you click Deploy progress window will show up. After system restart check that all services configures successful and click Close On Confirmation page, check the box Restart the destination server automatically if required and click Deploy Since we did the Quick Start selection the Connection Broker, Web Access and Session Host roles will be installed on the single server. On Select Deployment Scenario page, Select Session-Based Desktop Deployment and click next On Select Deployment Type page, select Quick Start and click next On Select Installation Type page, select Remote Desktop Services Installation, Click Next In the wizard on the Before you begin page click on next. Open Server Manager and click Manage -> Add Roles and Features You will need to configure RDS using Powershell. OBS!!! Avoid adding RDS roles through Roles and Features Wizard if you are not a Powershell fan.

In this guide we will focus on Quick Deployment (All-In-One) In previous part I detailed what are RDS 2016 deployment types, news in RDS 2016 and what are core components.