Deploy and manage virtual applications - Managing Enterprise Devices and Apps - page 26

■ Users in remote offices where no VPN is in place.

Users who need to access corporate applications from a computer in a public location
such as a hotel or an airport.

■

Kiosk machines that are locked down so that they grant access to only a limited set of
applications through the Internet—for example, public access machines that grant any
user access to a certain corporate application.

■

Preparing RemoteApp applications
Before you can make an application available remotely, you must install it on each Remote
Desktop Session Host server that will offer that application. Proper planning and installation
of the application ensures that your users can access it in a multiuser environment. You can
deploy applications that you want to make remotely available only after you have deployed
the Remote Desktop Session Host role.
When you are planning a remote application deployment, consider the following factors:

Suitability for multiuser environments This consideration is the most important.
Historically, most end user applications have functioned well in a multiuser environ-
ment; however, this is not always the case. You must check with the application vendor
to see whether a multiuser configuration is supported. Some vendors can provide fixes
that enable you to deploy an application in a multiuser environment. If they cannot,
you might have to deploy the application to traditional desktops or find another
application that can support a multiuser environment.

■

Application compatibility You have to investigate whether there are compatibility
issues with existing applications on the Remote Desktop Session Host server. Ensure
that you thoroughly test the proposed application before putting it into the produc-
tion environment. You might need multiple Remote Desktop Session Hosts so that
incompatible applications can be run separately from each other, and you might need
multiple session collections to create silos of applications.

■

Application dependencies Install, on the same Remote Desktop Session Host
server, related applications or applications that have dependencies on other local
applications. For example, all the applications of an application suite should be
installed on the same Remote Desktop Session Host unless otherwise prescribed by
the vendor.

■

Capacity requirements There are no firm numbers that indicate how many clients
a single Remote Desktop Session Host server can support. Resource requirements for
remotely delivered applications depend on several factors, including the application
requirements, the number of concurrent sessions, and how many applications (and
other services) the Remote Desktop Session Host is running. Several tools can provide
sizing guidance. Server administrators should monitor their server performance closely
in Remote Desktop Session Hosts and listen to the feedback end users provide, adding

■