Architecture Planning

n
Prevent users from providing credential information with Horizon Client command line options.
n
Prevent non-Horizon Client systems from using RDP to connect to remote desktops. You can set this
policy so that connections must be Horizon Client-managed, which means that users must use View to
connect to remote desktops.
See the Setting Up Desktop and Application Pools in View for information on using remote desktop and
Horizon Client group policy settings.
Implementing Best Practices to Secure Client Systems
You should implement best practices to secure client systems.
n
Make sure that client systems are configured to go to sleep after a period of inactivity and require users
to enter a password before the computer awakens.
n
Require users to enter a username and password when starting client systems. Do not configure client
systems to allow automatic logins.
n
For Mac client systems, consider setting different passwords for the Keychain and the user account.
When the passwords are different, users are prompted before the system enters any passwords on their
behalf. Also consider turning on FileVault protection.
For a concise reference to all the security features View provides, see the View Security document.
Assigning Administrator Roles
A key management task in a View environment is to determine who can use View Administrator and what
tasks those users are authorized to perform.
The authorization to perform tasks in View Administrator is governed by an access control system that
consists of administrator roles and privileges. A role is a collection of privileges. Privileges grant the ability
to perform specific actions, such as entitling a user to a desktop pool or changing a configuration setting.
Privileges also control what an administrator can see in View Administrator.
An administrator can create folders to subdivide desktop pools and delegate the administration of specific
desktop pools to different administrators in View Administrator. An administrator configures administrator
access to the resources in a folder by assigning a role to a user on that folder. Administrators can only access
the resources that reside in folders for which they have assigned roles. The role that an administrator has on
a folder determines the level of access that the administrator has to the resources in that folder.
View Administrator includes a set of predefined roles. Administrators can also create custom roles by
combining selected privileges.
Preparing to Use a Security Server
A security server is a special instance of View Connection Server that runs a subset of View Connection
Server functions. You can use a security server to provide an additional layer of security between the
Internet and your internal network.
IMPORTANT With Horizon 6 version 6.2 and later releases, you can use Access Point appliances in place of
security servers. Access Point appliances are deployed as hardened virtual appliances, which are based on a
Linux appliance that has been customized to provide secure access. For more information about Access
Point virtual appliances, see Deploying and Configuring Access Point.
A security server resides within a DMZ and acts as a proxy host for connections inside your trusted
network. Each security server is paired with an instance of View Connection Server and forwards all traffic
to that instance. You can pair multiple security servers to a single connection server. This design provides an
additional layer of security by shielding the View Connection Server instance from the public-facing
Internet and by forcing all unprotected session requests through the security server.
View Architecture Planning
80 VMware, Inc.