Posts Tagged RD Gateway

Deploying the RD Gateway Service Role in a 2012 / 2012 R2 RDS Farm

Applies to: Windows Server 2012 and 2012 R2

For any RDS farm, there is a very good chance users will be accessing the farm from a remote location outside of the corporate network. When doing so, it is critical to secure their connection, especially when corporate data is being accessed. In order to secure a user’s connection into a RDS farm, a RD Gateway server will be required. The RD Gateway enables authorized remote users to connect to resources in an internal corporate or private network, from any Internet-connected device that can run the Remote Desktop Connection (RDC) client. The network resources can be RD Session Host servers, RD Session Host servers running RemoteApp programs, or computers with Remote Desktop enabled.

The following will cover the steps needed in deploying a RD Gateway Server into a 2012 / 2012R2 RDS farm. Before deploying the RD Gateway Server, the RDS farm should already be built and configured. Please check out the following for more information on deploying a 2012 / 2012R2 Remote Desktop Services (RDS) farm. Read the rest of this entry »

, , , , , ,

18 Comments

Collections – Publishing RemoteApp programs and Session Desktops on RDS 2012 / 2012 R2

Applies to: Windows Server 2012 and 2012 R2

In a previous article, we went through the steps of deploying a 2012 / 2012R2 Remote Desktop Services (RDS) farm. Now with the farm built, let’s take a look at the changes and the process of publishing RemoteApp programs and session-based desktops in Server 2012 / 2012 R2.

Let’s open Server Manager and look at our farm. On the left column you will see a new node called Collections. Collections give you the ability to group a set of RD Session Host servers with a common set of applications and publish them to users. These can be RemoteApp programs or Session Host and VDI desktops. So think of collections as something similar to an application silo. For instance, let’s say we had a group of 5 RD session host servers which all have Office 2013 installed and are configured the same way. If we wanted to publish the Office applications across the 5 RD session host servers, we would first create a collection that included all 5 servers and publish the Office apps accordingly. This is the same if you wanted to provide users with a session host desktop. You would simply create a new collection, add the servers which will be providing the session desktop and publish them to the proper user group(s). One thing to note is you cannot publish a desktop to an existing collection which has already been configured for RemoteApps. The published desktop will require its own collection. Read the rest of this entry »

, , , , , , , , ,

55 Comments

Deploying a 2012 / 2012R2 Remote Desktop Services (RDS) farm

Applies to: Windows Server 2012 and 2012 R2

A lot of people were pretty excited when Microsoft released RDS for 2012 and for good reason. Not only did they overcome the shortcomings of the previous release of RDS on Windows 2008 R2, they have also made it very easy to setup and configure. One of the many great features of 2012 and 2012 R2 is the ability to push roles and features to multiple servers in an environment from a single Server Manager console. Not only does this save time when rolling out a new RDS environment, it also makes it easy.

The following will cover the step by step process in deploying the base components of a RDS 2012 /2012 R2 farm. Before we begin the process, let’s look at the different roles we will be deploying.
 
Read the rest of this entry »

, , , , , , , , ,

136 Comments

Configuring the RD Gateway Server for a 2012 RDS farm with HA enabled for the RD Connection Brokers

Applies to: Windows Server 2012 and 2012 R2

In a previous article, we demonstrated the steps needed to configure HA for the RD Connection Broker servers in an RDS 2012 farm. If you are using an RD Gateway server for a farm where HA is configured for the brokers, there are a few steps you will need to do in order for users to be able to successfully connect through the RD Gateway server(s).

When a user connects through the RD Gateway server, the gateway server will initially connect the user to one of the RD connection broker servers in order for the broker to determine what server or desktop the user will be connecting to. When HA is enabled for the farm, the gateway server will try to connect the user to the brokers using the DNS Round Robin name when HA was configured for the farm. By default, the DNS name used is not on the gateway’s allowable resource list for users to connect to. So for any user trying to connect to the farm through the RD Gateway, their access will be denied. To get around this, we will simply need to add a new resource authorization policy which will users to access resources through the gateway server using the designated DNS round robin name. Read the rest of this entry »

, , , , , , , , , ,

10 Comments

Configuring HA for the Remote Desktop Connection Broker in a 2012 RDS Farm

Applies to: Windows Server 2012 and 2012 R2

One of the biggest issues with Remote Desktop Services on Windows 2008 R2 was the limitation of only having a single active RD Connection Broker server per RDS farm. Yes, you still could have multiple broker servers, however they would run in an Active/Passive mode. This was a major problem since it would limit the size of the farm. The more servers, resources, and users added to the farm put a strain on the single active RD broker server. In most cases, you would have to create multiple RDS farms to get around this problem. This has changed with RDS for 2012. You can now have multiple active brokers in a single RDS farm.

As per Microsoft, the RD Connection Broker provides the following functionality: Read the rest of this entry »

, , , , , , , , , , ,

20 Comments