#2012 R2 REMOTE DESKTOP SERVICES SETUP LICENSE#
#2012 R2 REMOTE DESKTOP SERVICES SETUP WINDOWS#

The same functionality is provided by the Server Manager by navigating to the Collection, selecting Tasks->Edit Properties and then the Security Tab The first tab is the General Tab which is used to configure security settings and Certificate Settings on the RDP-Tcp Listener This configuration was done through the Remote Desktop Session Host

#2012 R2 REMOTE DESKTOP SERVICES SETUP WINDOWS#

For example a single Licensing server can provide licenses to both Windows Server 2008 R2 and Server 2012 R2 deployments and a GatewayĪs installation completes on Windows Server 2008 R2 for the Remote Desktop Session Host, a number of settings would be revised by an administrator to provide users with optimal experience. Only Licensing and Gateway server consoles are available due to the fact that these roles can exist on different servers. Servers as needed empowering administrators with true scale out options. It also provides an easy way to add or remove This management change effectively pushes all of the configuration changes to the servers providing Remote Desktop functionality and eases the administrative burden of having to move through different consoles. Some of the options in the previous release consoles are moved to either PowerShell or Group Policy. Server Manager hosts the Remote Desktop Services administration page for most of the settings an administrator need to configure. The new unified administrative experience in Windows Server 20 R2 is provided within Server Manager. The Server Manager in Windows Server 2012 and Windows Server 2012 R2. These settings are automatically configured by This console is unchanged in Windows Server 2012 and Windows Server 2012 R2.įinally the Remote Desktop Web Access Configuration is a web page with which we can configure the sources a Remote Desktop Services Web Access server can connect and provide Remote Desktop services to users.

#2012 R2 REMOTE DESKTOP SERVICES SETUP LICENSE#

The Remote Desktop Licensing Manager is used to configure a License Server for the Remote Desktop Services Deployment.

The Remote Desktop Gateway Manager is the console used to manage Remote Desktop Services Gateway Settings. An administrator can still use the Remote Desktop Client in order to connect to a Remote Desktop Server. This console is no longer used in Windows ServerĢ012 and Windows Server 2012 R2. The Remote Desktops MMC is used to host connection information on a single pane providing administrators with quick access to Remote Desktop Servers instead of the Remote Desktop Services Client functionality.

Essentially this console provides the RDP Settings in each. The RemoteAPP manager is used to publish and configure all of the remote application settings. The Remote Desktop Services Manager is used to manage the user connections like disconnect users and provide connection info. RDP-Tcp server specific settings such as Color Depth, Session Settings, licensing options etc. The Remote Desktop Session Host configuration is used on a server running Remote Desktop Session Host to configure The consoles used to manage the settings are the following: Remote Desktop Session Host Configuration In order to gain a better understanding of the administration in the previous release of Windows Server, I will quickly go through the MMC consoles used in order to configure the deployment options.

SRV2012Web1 /Windows Server 2012 R2 Remote Desktop Services Web and Gateway Services.

SRV2012RDS1 /Windows Server 2012 R2 Remote Desktop Services Session Host.

SRV2012CB1 /Windows Server 2012 R2 Remote Desktop Services Connection Broker.

SRV2012DC /Windows Server 2012 R2 Domain Controller, DNS and DHCP.

The second lab is a pure Windows Server 2012 R2 installation, the virtual machines used are the following:

SRV2008Web1 / Windows Server 2008 R2 Remote Desktop Services Web and Gateway Services.

SRV2008RDS1 / Windows Server 2008 R2 Remote Desktop Session Host.

SRV2008DC / Windows Server 2008 R2 Domain Controller, DNS and DHCP.

The first lab consists of a pure Windows Server 2008 R2 installation, the virtual machines used are the following: In order to provide the best possible guidance in this article, two virtual machine based labs are being used to generate screenshots. All of the configuration is now stored in the Connection Broker database. The RDMS is responsible for adding, removing and updating configuration for all of the servers comprising a Remote Desktop Services deployment. Windows Server 2012 introduced the Remote Desktop Management Service (RDMS) effectively removing the standard MMC consoles used to manage a Windows Server 2008 R2 Remote Desktop Services server. This wiki article main purpose is to provide administrators familiar with Windows Server 2008 R2 Remote Desktop Services a quick overview of management changes in Windows Server 2012.It covers settings locations only and does not provide information about the Management (how to) changes for RDS in Windows Server 20R2

2012 r2 remote desktop services setup