Link to home
Start Free TrialLog in
Avatar of matt
mattFlag for United States of America

asked on

Remote Desktop Services 2012- cert and RD gateway question

My first time setting up RDS and a question on the RD gateway where it is asking for a FQDN. the full domain name for the terminal server is terminalserver.domain.com, is that what I should be putting here or just domain.com?
If it is just domain.com...then my question is that domain.com, is also what is used for our website publicly so should I create a subdomain for access to this?
As for the cert- will just a standard SSL cert with domain.com be fine, or do I need some sort of multi-domain SSL?
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

you should have www.domain.com at an external source
remote.domain.com or terminalserver.domain.com

probably easier to get a wildcard certificate *.domain.com or for remote.domain.com but in your certificate request you need to add the common names of the servers involved. i.e.
remote.domain.com resides on iis on server1.domain.com so it requires the common name of server1.domain.com, add also the connection broker and final connection machines common names.
Avatar of matt

ASKER

If this is just for internal use, do I need to go through this process. I really don't want public access to a terminal server on our network? And can all services required for Remote Desktop run on one server? Broker, Gateway, etc
If it's just for internal use, you don't really need RD Gateway at all, unless there's an internal firewall between the Remote Desktop clients and the session host server(s). The most common use of RD Gateway is to allow external users to connect to internal session host servers by using an SSL-secured connection rather than a straight RDP connection.
Avatar of matt

ASKER

we use VPNs from our hubs to our main office where the current terminal server (2003 server) exists. On the new system we are migrating to I was wondering If I even needed a RD gateway. currently we just use RDP connection, is that how it is still done with new Remote Desktop?
ASKER CERTIFIED SOLUTION
Avatar of DrDave242
DrDave242
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of matt

ASKER

OK. what about Web access role?
Avatar of matt

ASKER

OK- what about the Web Access Role? Do I need that if I'm using the VPN?
RD Web Access is optional. It allows users to access Remote Desktop connections or published RemoteApps through either the Start menu or a browser. In an environment with a large number of published RemoteApps or several different session-host collections, this comes in handy, but in a smaller environment, it's not necessary.