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 »

, , , , , , , , , ,


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 »

, , , , , , , , , , ,


Mapped Drives are not being personalized for random users with AppSense Environment Manager

Product: AppSense Environment Manager 8.x

** NOTE: For AppSense Environment Manager Version 8.0, the following is in the user’s desktop settings within personalization. For any newer version it will be in the user’s Session Data within personalization.


A user logs into their desktop and they report they cannot see their mapped drives. If the user creates a new mapped drive within their session, logs off and back into their desktop, the mapped drive is no longer there. This only occurs for random users. Upon further investigation, when looking at the user’s session data in personalization analysis, the mapped drives are being personalized. This is found under the registry key HKCU\Network. In fact, even the newly mapped drive shows up here as well. Read the rest of this entry »

, , , , ,

Leave a comment

User’s default printer not saving in XenDesktop 5.6 using AppSense Environment Manager

During the testing phase of a new VDI rollout, there were many users complaining they had to set their default printer each time they logged into their desktop. I worked with a few of the users and noticed the issue would only occur if they were setting one of their Citrix auto-created printers as the default. We did not see the issue if the user set a network printer as their default printer. Before we go further, lets look at what the environment consisted of:

Citrix XenDesktop 5.6
Citrix Provisioning Server 6.1
VDI Image Operating System: Windows 7 Sp1
AppSense: Environment Manager 8.4

Within our AppSense configuration, we were utilizing Session Data in personalization to capture the user’s default printer which is held under the following registry string entry: Read the rest of this entry »

, , , , , , , , , ,

Leave a comment