Start by building RDS01, RSH01 and RSH02 as per your server build processes. This can be avoided if your internal domain name matches your external domain name. This configuration requires the use of a SQL database accessed via the SQL Native Client.
As this deployment assumes an non publicly routable internal domain name the Connection Broker will be installed in Highly Available mode to allow it to have a custom DNS name in. Split DNS should be configured on internal DNS servers for the zone. A certificate covering, and will be installed on RDS01. One public IP address is required for use with inbound traffic to the Remote Desktop Web, Gateway and Connection Broker roles. A further two servers, RSH01 and RSH02 will host the Remote Desktop Session Host role. The following roles will be installed on one server, RDS01: Remote Desktop Connection Broker, Remote Desktop Licensing, Remote Desktop Gateway and Remote Desktop Web Access. All servers are running Server 2012 R2 Standard. To standardise the guide for use in other networks, an internal domain name of fabrikam.local and an external domain name of will be assumed. Access will be available via Remote Desktop Gateway, Remote Desktop Web Access or via the Start Menu using RemoteApp and Desktop Connections.
2012 R2 REMOTE DESKTOP SERVICES SSL CERTIFICATE FULL
This platform will allow access to either full Remote Desktop or Remote App sessions via a load balanced set of Session Hosts. This step by step guide will outline the stages to setup a Remote Desktop Services (RDS)deployment with Server 2012 R2.
0 kommentar(er)
