Publishing Terminal Servers (TS/RDS)

From vmWIKI
Jump to: navigation, search

Originating Author

Michelle Laverick

Michelle Laverick.jpg

Barry Coombs

Screen Shot 2014-04-28 at 09.41.39.png

Video Content [TBA]

Introduction Publishing Terminal Servers (TS/RDS)

Version: Horizon View 5.1

VMware View is not limited to merely allowing access to virtual desktops, it can also securely broker connections to other devices and systems such as Terminal Servers now called Remote Desktop Services (RDS), Physical PCs (with RDP enabled) and PC Blades. This configuration begins with an installation of the View Agent that then registers the system with the Connection Server(s). Before you begin, it’s worth confirming that the client(s) can connect to the external system using its normal RDP connection. The PCoIP protocol can only be used transparently with virtual desktops, the only way to use PCoIP with these non-virtual desktops is if they have Teradici hardware present.

View Authentication Requirements

As with Windows Vista and Windows 7 there are two types of authentication supported in Windows 2008 R2 RDS. We would recommend using “Do not require NLA” if you are setting up a new RDS host. This will allow so-called legacy clients like Windows XP and Apple Mac to connect without an error.


Remember on a TS/RDS server, it must be in “install mode” before installing any software. This can be achieved by using the command:

change user /install

When the installation is over, remove the server from “install mode” with the “change user /execute” command. Alternatively, within Control Panel, Programs in Windows 2008 R2 you should see a “Install Application on Remote Desktop” link


Install the View Agent to Terminal Server

The first step in preparing a TS or RDS host for View is to install the View Agent just as you would for a virtual desktop. Remember to download the right version of the agent. If you are running Windows 2008 R2 64-bit you will need the 64-bit version of the Agent. The agent installs differently to server editions of Windows than to Windows XP or Windows 7. In this case you need administrator credentials to “register” the server with the View Connection Server.

1. Run the vmware-viewagent-xxxxx.exe

2. In the Register with View Connection Server dialog box – type in the name of the Connection Server, together with your credentials for the Connection Server


3. Click Next and Install

Publishing Terminal Servers in View

1. The next step is to publish the Terminal Server in the View administration pages. Begin by navigating to Inventory and Pools


2. Click the Add button and Select Terminal Services Pool

3. Type in a unique ID and Friendly Name


4. Configure the Pool Settings based on your own preferences

5. Select your Terminal Server from the list like so:


6. Click Next and Finish

7. Once the Terminal Server appears in the Pools list, select it and then entitle the shared desktop to your users


The Terminal Server’s shared desktop should appear in the list alongside any other virtual desktops that you have entitled the user to use.


As you can see enrolling your existing TS or RDS commitment into View is very easy. All you need is the right software and the right credentials to complete the job. In our next couple of chapters we are going to focus on the settings and policies that control the user experience. Chapter 17 focuses on Microsoft Group Policies as method of bolting down the users interface. If you are very familiar with Microsoft GPO system you may well decide to skip this chapter – we felt it was so important that we couldn’t skirt over the topic. Chapter 18 is more focused on settings that control the users experience from a VMware View perspective. This includes both settings that appear in the View management console and custom settings available within Microsoft GPOs. VMware have provided their own custom templates (or .adm files) that allow great customization beyond their own console.