windows server 2012 r2 remote desktop services

#WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES UPDATE#
#WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES MANUAL#

You should now be able to log into Remote Desktop Services Web Access.I am struggling to understand this new RDS.

#WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES UPDATE#

Update 070316 You also will need to restart the Remote Desktop Services Service!Ĭonnect to the server on the address, and you can check the correct certificate is used. Select ‘https’ > Edit > Add in your certificate > OK > Close.īounce the services with an ‘ iisreset‘ command. Sites > Default Web Site > Edit Bindings. Import > Import your publicly signed certificate, (you can use a self signed certificate but DON’T FORGET your remote client needs to be able to check your CRL, and trust your issuing CA if you do).

#WINDOWS SERVER 2012 R2 REMOTE DESKTOP SERVICES MANUAL#

Note: You can change certificates from within Server Manger, but I prefer the manual approach, on the RD Gateway Server > Launch the IIS Manager > Select the server > Server Certificates. Select the applications, (or add them in if they are not displayed) > Next. To actually publish applications, select the collection you just created > RemoteApp Programs > Tasks >Publish RemoteApp Programs. If you want to deploy ‘profile disks’ enter a UNC path to the share > Next. Here Im simply using the domain users group > Next. Select the user groups that you want to grant access to. Server Manager > Remote Desktop Services > Collection > Task > Create Session Collection.Īdd in the server(s) running the RD Host role that will be included in this collection > Next. Now you need to create a ‘ Collection‘, this is a group of host servers that host applications you can publish. But I will still ‘Activate’ my licensing server. I’m content with the 120 day licence for my test deployment. In production you would now add your Remote Desktop Licences, If you don’t, the whole thing will run for 120 days, (though it continues to nag you about adding licences). Select ‘RD Gateway’.Īdd in the server that will host the RD Gateway role > Next.Īdd in the public name of the RD Gateway server, this will generate a self signed certificate, (you can replace this with a proper one later).Īdd in the server that will host the licensing role > Next. In Server Manager > Remote Desktop Services > Overview > Note: There are two options yet to be configured, (shown in green). ( Note: There will be a licensing error, we will address that in a minute). Tick the ‘restart the destination server automatically if required’ > Deploy.įinish. Select the server that will host the Connection Broker Rule and add it > Next.Īdd the server that will host the Remote Desktop Web Access role > Next.Īdd the server that will host the Remote Desktop Session Host role > Next. Note: If you choose Quick Start it puts all the roles on one server > Next. Manage > Add Roles and Features > Next > Remote Desktop Services Installation > Next. To save yourself some hassle, visit every server that will be in the Remote Desktop Server deployment, and add all the others into each others ‘server manager’ console. Below is a run though and my notes on deploying RDS ONLY (I’ll put the links to other articles at the bottom of this post as I write them). I’m a little rusty on RDS and needed to deploy a few roles, so for my proof of concept I deployed RDS on TWO servers. I’ve had to do a rollout of Remote Desktop Services on Server 2012 R2, and publish it with Active Directory Federation Services and Web Application Proxy.

Windows server 2012 r2 remote desktop services