windows server 2012 remote desktop certificate

The internal server names of your session hosts.The internal server name of the Connection Broker.Regardless of which certificate type you choose, it will need to cover all the servers in the environment: SAN certificates are certainly a little cheaper, however they have a maximum of 3 hosts, so if your RDS environment expands in the future, you’re going to need to issue a wildcard down the line anyway. In most cases I would always recommend a Wildcard certificate since it will cover an unlimited number of hosts under a single domain. Since we know that we need to potentially secure multiple server names, we need to purchase either a SAN or Wildcard Certificate. Now that we have defined the services that need to be covered by our SSL certificate, let’s talk about the certificate itself. RD Session Host: These are the workhorses of the environment, and are the servers that the users are logging into, and where the published RemoteApps execute from.In an environment with multiple session hosts, for example, the connection broker is responsible for load balancing the connections evenly across the farm.

RD Connection Broker: This is an internal service that handles all the session management for incoming RDS connections.RD Gateway: This is an externally facing service that receives the RDS connections from the internet, checks the connections against a defined set of connection and resource policies, and passes them on to the Connection Broker.RD Web Access: This is an externally facing service that provides the web interface the users will access to login and launch their RemoteApps.What do I do if my internal domain differs from my external domain?īefore we can talk about the questions above, we need to identify each of the core Remote Desktop Roles that will need securing and what their functions are.What server names need to be covered by the certificate?.How do I generate the certificate to deploy it across the environment?.The four core questions that most folks get stuck on are the following. While documentation exists on TechNet and other sources describing the SSL requirements, I have yet to find a comprehensive source that covers all the possible scenarios where the requirements differ from one to the next. For the purposes of this article, we’ll be discussing Remote Desktop Deployments on Windows Server 2012/2016. Properly securing Remote Desktop Services with an SSL certificate is a subject that causes frequent confusion among IT Professionals.

Windows server 2012 remote desktop certificate