How To Set Up Windows Server 2016 Remote Desktop Services RemoteApps
Think you can do better? Show us!
In this video, Matt will take you through the steps to create a proof of concept environment for Microsoft Windows 2016 Remote Desktop Services, in particular, this video will focus on creating the infrastructure required to host a small RDS system and how to publish applications using collections, the demo will culminate in Matt showing you how to access your applications using RD Web Access. Even although Microsoft has partnered with Citrix to bring you XenApp Essentials in Azure, RDS remains an excellent means of accessing applications and desktops remotely. This is evident in Server 2019 where RDS is still present. Prerequisites include: Windows Server 2016
To start you first need to add the roles, so in server, manager click on manage and then add Roles and features. At the select installation type screen. He obviously need to choose a remote desktop services installation. For deployment type I'm choosing quickstart, which will install all the roles on a single server. But for large production environment. You want to choose the standard deployment. The multipoint services. Type is a managed standalone multiuser environment and is outside the scope of this video. We want to choose the session based desktop deployment rather than the vdi type of deployment. Here, having chosen quick start earlier. The install wizard wil, now go ahead and automatically install the remote desktop connection broker web access and. session host role services using the credentials of the currently logged in domain user and she'll get warning that a restart will be required. After the role services have been installed tick. The box for restart the destination server automatically then click deploy. Wait whilst the role serves distance install and then click close. So service rebooted and we're back in server manager. And you can now click on the remote desktop services to finish the setup. So for this deployment I'm installing all the roles on a single server. But again for large production environment, you'll be wanting to install the roles in different servers. So on to install the remote desktop gateway click on RD Gateway and then choose to install the role on the local server. And then enter the external fully qualified domain name of the Gateway Server. In this case, it's going to be RDS dash POC dot techsnips dot IO. Once installed you get a warning that you need to configure a certificate for the remote desktop gateway to use. And the next thing to configure will be a remote desktop license server. And again we're going to install the role here. But in a large production environment. You would have a central licensing server to issue licenses for all the session host servers. With all the roles installed looks like we would be almost done, but in fact, the deployment needs further configuration. Click on tasks and then edit deployment properties. Many of these settings have been configured in earlier steps when we are installing the roles. You want to keep the default settings for the gateway server and then you'll need to choose a licensing mode and I've opted here for the per user mode that we installed the role here. The remote desktop license server is ready specified. Again web access is already been configured so that just leaves the certificates to configure. There are 4 Role Services, which will require certificates to function correctly. So this could be a self signed certificates. Or one from an internal CA server. Or you can use one, signed by a Publix typical authority. We only to click on each role service intern at certificate and then click apply. And I'm going to be using the same certificate for each of the 4 role Services. With that done where now finally ready to publish the remote apps as we chose a quick start deployment at the start this process. A remote app collection has even set up for us and the calculator paint an wordpad applications have been automatically published. You might decide that you want to Unpublish, one of these applications, so just click on tasks and then unpublish remote app programs. And in the new window tick, the app you want to remove click next and then Unpublish. To then publish a new remote app click on tasks and then publish remote app program. The server will do a check and then you'll be presented with a list of all the installed applications. To publish an app from the list just simply take the box next to it. Or if you wish to published an app, which isn't in the list click on ADD. And then browse to the location of the executable file. And then click next and then publish. To them access the publisher applications. Open up your web browser and browse to the Rd web URL login with your domain username and password. You will then see a page of all the published apps click on app then click connect in the remote app pop up to launch it. You may wish to restrict the particular app to only certain users. Right click on the app and select edit properties. There are quite a number of different properties that you can configure here. But we're interested in user assignment click on this in the sidebar and then click the radio button for only specified users and groups. Click add and then select the group or individual that you wish to have access to this application. And then we're done. I hope that you enjoyed this video and thank you for watching.