- #WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER INSTALL#
- #WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER FULL#
- #WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER LICENSE#
- #WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER PLUS#
- #WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER WINDOWS#
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA. The connection string will vary depending on the environment but for SQL 2008 R2, this should work assuming a SQL server name of SQL01:ĭRIVER=SQL Server Native Client 10.0 SERVER=SQL01 Trusted_Connection=Yes APP=Remote Desktop Services Connection Broker DATABASE=RDCBĮnter a path for the database relative to the target SQL Server e.g. From the Remote Desktop Services dashboard in Server Manager, right click RD Connection Broker and select Configure High Availability.
#WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER INSTALL#
Install the SQL Native Client which can be found on the installation media used to install SQL.
#WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER LICENSE#
Ensure the computer account for RDS01 is in the Terminal Server License Servers group in Active Directory.Ĭreate a SQL login for the Remote Desktop Connection Brokers security group with the dbcreator Security Role. Complete the activation wizard as per your licensing arrangement. Expand the All servers entry then right click RDS01 and click Activate Server.
Open the Remote Desktop Licensing Manager from Administrative Tools.
#WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER PLUS#
Click the green plus to install RD Licensing and select RDS01 as the target server. The certificate and other settings will be configured later. Select the RDS01 server then enter for the certificate name. Open Remote Desktop Services from Server Manager and click the green plus to install RD Gateway. Confirm the choices in the Completion then click Deploy. Select RSH01 and RSH02 for the RD Session Host role. Continue through the wizard and select RDS01 for the RD Connection Broker and RD Web Access roles.
Click Add roles and features, select Remote Desktop Services installation, Standard Deployment then Session-based desktop deployment. Find RSH01 and RSH02 and add them to the selection on the right hand side. Open Server Manager on RDS01 and in the Dashboard section click Add other servers to manage. Policies>Administrative Templates>Windows Components>Remote Desktop Services>Remote Desktop Session Host>Licensing Specify the licensing mode for the RD Session Host server: Per User Use the specified Remote Desktop license servers:. rdp publishers: Thumbprint of RD Connection Broker Publishing certificate. Policies>Administrative Templates>Windows Components>Remote Desktop Services>Remote Desktop Connection Client Specify SHA1 thumbprints of certificates representing trusted. Policies>Administrative Templates>Windows Components>Remote Desktop Services>Remote App and Desktop Connections Specify default connection URL: Target Computers: RemoteApp Members: User Accounts and/or Groups of Users authorised to use particular Remote App Group Policy Target Users: Remote Desktop Gateway Users Members: User Accounts and/or Groups of Users authorised to connect via RD Gateway Remote Desktop Connection Brokers Members: RDS01 DNSĬreate the DNS entries for in both internal and external DNS TypeĮxternal DNS: Public IP Address / Internal DNS: LAN IP of RDS01įorward TCP Ports 80 + 443 and UDP 3391 to RDS01 Active Directory
#WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER WINDOWS#
The servers used in this guide are up to date with all Important Windows Updates. 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.
#WINDOWS SERVER 2012 TERMINAL SERVICES MANAGER 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)
