7.0

When users submit print jobs concurrently from RDS desktops or applications that are hosted on the same
RDS host, the ThinPrint server on the RDS host processes the print requests serially rather than in parallel.
This can cause a delay for some users. Note that the print server does not wait for a print job to complete
before processing the next one. Print jobs that are sent to different printers will print in parallel.
If a user launches an application and also an RDS desktop, and both are hosted on the same RDS host, they
share the same user profile. If the user launches an application from the desktop, conflicts may result if both
applications try to access or modify the same parts of the user profile, and one of the applications may fail to
run properly.
The process of setting up applications or RDS desktops for remote access involves the following tasks:
1 Set up RDS hosts.
2 Create a farm. See Chapter 9, “Creating Farms,” on page 107.
3 Create an application pool or an RDS desktop pool. See Chapter 10, “Creating Application Pools,” on
page 119 or Chapter 11, “Creating RDS Desktop Pools,” on page 123.
4 Entitle users and groups. See Chapter 13, “Entitling Users and Groups,” on page 159.
5 (Optional) Enable time zone redirection for RDS desktop and application sessions. See “Enable Time
Zone Redirection for RDS Desktop and Application Sessions,” on page 102.
NOTE If smart card authentication is enabled, make sure that the Smart Card service is disabled on RDS
hosts. Otherwise, authentication might fail. By default, this service is disabled.
CAUTION When a user launches an application, for example, a Web browser, it is possible for a user to gain
access to the local drives on the RDS host that is hosting the application. This can happen if the application
provides functions that cause Windows Explorer to run. To prevent this type of access to the RDS host,
follow the procedure that is described in http://support.microsoft.com/kb/179221 to prevent an application
from running Windows Explorer.
Because the procedure described in http://support.microsoft.com/kb/179221 affects both desktop and
application sessions, it is recommended that you do not create RDS desktop pools and application pools on
the same farm if you plan to follow the procedure in the Microsoft KB article, so that desktop sessions are
not affected.
Installing Applications
If you plan to create application pools, you must install the applications on the RDS hosts. If you want
Horizon 7 to automatically display the list of installed applications, you must install the applications so that
they are available to all users from the Start menu. You can install an application at any time before you
create the application pool. If you plan to manually specify an application, you can install the application at
any time, either before or after creating an application pool.
IMPORTANT When you install an application, you must install it on all the RDS hosts in a farm and in the
same location on each RDS host. If you do not, a health warning will appear on the View Administrator
dashboard. In such a situation, if you create an application pool, users might encounter an error when they
try to run the application.
When you create an application pool, Horizon 7 automatically displays the applications that are available to
all users rather than individual users from the Start menu on all of the RDS hosts in a farm. You can choose
any applications from that list. In addition, you can manually specify an application that is not available to
all users from the Start menu. There is no limit on the number of applications that you can install on an RDS
host.
Setting Up Desktop and Application Pools in View
96 VMware, Inc.