stillskinny.blogg.se

1. #WINDOWS 2012 R2 REMOTE DESKTOP SERVICES QUICK SETUP INSTALL#
2. #WINDOWS 2012 R2 REMOTE DESKTOP SERVICES QUICK SETUP WINDOWS#

If you are setting this up in a enterprise where the RD Gateway is in the DMZ then there are quite a few ports that need to be opened up, to read about these ports and firewall scenarios check out this Microsoft MSDN blog post: If you are setting this up in your home lab where you don’t have a DMZ and only behind a single firewall (router) then you only need to setup port forwarding on 443 to your RD Gateway server. In order for traffic from the outside to reach your RD Gateway server you will need to pen some ports up in your firewall. This step does not involve configuration of your RDS environment but on your network. The least secure and should be used only in home labs! The last option is to allow any server to be connected.This is a nice option if you want only a few or small amount of servers accessiable. The second option allows you to create a RD Gateway managed group then add servers into the list.Example: You can select Domain Computers. The first option is to assign permission to a AD Organizational Unit.By default the middle option is selected with no groups created. To configure what computers can be access through the RD Gateway go to the Network Resources tab. You could create a Active Directory group called RD-Users so only users of that group have access for security purposes.

On the Users Groups tab you can change who has permissions to use the RD Gateway. Start -> Control Panel -> Administrative Tools -> Remote Desktop Services -> Remote Desktop Gateway Managerĭrill down to the Resource Authorization Policies and select RDG_AllDomainComputers then click Properties. To configure both these options open the Remote Desktop Gateway Manager: I create a wildcard cert using StartSSL, having a trusted SSL certificate makes external access to much easier:Ĭonfigure RD Gateway – Permissions and Network Resources:īy default the RD Gateway is set to allow all Domain Users access to use RD Gateway but with no Network Resources to connect to. If you have a third party SSL certificate (Such as GoDaddy, DigiCert, StartSSL, etc) you can apply it the same way. Click Ok.įor the new certificate to take affect either restart the RD Gateway server or restart the RD Gateway service (labeled as Remote Desktop Gateway in services.msc) The RD Gateway will now show Ready to apply. Check the box to Allow the certificate to be added to the Trust Root Certification Authorities.Check the box to Store this Certificate and pick a folder location for safe keeping.To create the self signed certificate go to Tasks -> Edit Deployment PropertiesĬlick Certificates -> RD Gateway -> Create new c ertificate It is easy to change once a trusted SSL certificate is obtained. I did my initial setup using self signed certs but will eventually change to a trusted SSL certificate. RDS Gateway will work on self signed certificates but it requires a few additional steps for it to work on remote computers outside your LAN. Enter the URL you want to use and click NextĬonfirm your selections and FQDN name, click Addīack on Server Manager the RD Gateway will have have a icon to signify the role is installed.Ĭonfigure RD Gateway – Apply SSL Certificate: Click Nextįor installation it will create a self-signed SSL certificate that can be changed later.

#WINDOWS 2012 R2 REMOTE DESKTOP SERVICES QUICK SETUP INSTALL#

Select the server from the server pool you want to install the RD Gateway role. In Server Manger of your RDS environment click the RD Gateway icon If your Gateway server is going to be a separate server add it to the Server Pool of your RDS Environment by going to Manage -> Add Servers

#WINDOWS 2012 R2 REMOTE DESKTOP SERVICES QUICK SETUP WINDOWS#