#SERVER 2012 R2 REMOTE DESKTOP SERVICES SINGLE SERVER WINDOWS#

The management console for RDS in Windows 2012 and later are completely different than the one used in Windows 2008R2. The other option would be to perform the management through PowerShell cmdlet.ĭo not loose time and use the new installation process in order to get your RDS ready to go ! Explore the new RDS management console So, yes, you could do the installation using the role based approach but you will still have to use the remote desktop installation approach to finalize the installation. In a few words, you have to go back to the Add Server roles wizard and select the Remote desktop installation option in order to get the RDS role fully installed and working. When your installation is complete and you try to open the RDS management console, you will get the following screenshot You can perform the installation in such a way but this does not really make sense. So, with my first RDS installation in Windows 2012, I have used the Role-based scenario.

#SERVER 2012 R2 REMOTE DESKTOP SERVICES SINGLE SERVER INSTALL#

The first time I had to install the RDS in Windows 2012, I thought that the process would be similar to the one in Windows 2008 R2. Installing RDS in the old Fashion Way (Role-Based) In the View Progress Page, you can see the progress of the installation In the confirm page, tick the checkbox Restart Destination server which will make available the deploy button. In the Select a server page, select the future RDS Server add it to the right columns and Press Next (We are deploying RDS on Virtual machines so I cannot demonstrate yet the virtual machine based deployment). In the Deployment scenario, select the Session-based Desktop Deployment. In the Deployment Type page, select the option Quick start and Press In the Selection installation type page, you should select the option remote Desktop services installation and Press Next In the Add Roles and Feature Wizard, in the selection installation Type, you will have the option to choose from To perform the installation of a basic RDS role, you would start your server Manager console, click on add and remove Roles. Install RDS using the Remote Desktop Services installation (the New Way) One option is to use the Remote Desktop service installation option (which is the new and best way to install RDS roles) or you can use the role-based installation option (which is the old and not recommended way to install RDS). When you start the Add Roles and features Wizard, you will have two ways to install the RDS role. In our scenario, we want to install RDS Roles on a single Server.

1 Machine with the remaining roles (RD GW, RD Web, RD Connection broker, RD Licensing).

1 Machine with the Remote Session host (or virtualization host) or both.

If you have only 2 machines, you could spread the roles as follow:

1 Machine would host the RD Licensing (which could be combined with the RD Connection broker).

1 Machine would host the Remote Connection Broker.

1 Machine would host the Remote Desktop Gateway and the Remote Web Access.

1 Machine would host the Remote Session Host (or Virtualization Host) or both.

I usually spread the roles in the following manner when I have a more complex topology: In more advanced scenario/topologies, you might want to use different servers to host different RDS Services roles. The single server installation is to get used to the new installation procedure and the new management tool. In coming posts, we will have a look at a more complex deployment strategy. All the needed roles will be installed on a single server.

In this post, we will assume that we want to deploy the Remote Desktop Services on a single Server. We have also seen the different components that can be deployed through your organization based on your requirements. In part I and Part II, we have quickly describes the remote Desktop services role available in Windows 2012 R2.

Server 2012 r2 remote desktop services single server