VMware Horizon View Architecture Planning Horizon View 5.2 View Manager 5.2 View Composer 5.2 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
VMware Horizon View Architecture Planning You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2009–2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents VMware Horizon View Architecture Planning 5 1 Introduction to Horizon View 7 Advantages of Using Horizon View 7 Horizon View Features 9 How the Components Fit Together 10 Integrating and Customizing Horizon View 14 2 Planning a Rich User Experience 17 Feature Support Matrix 17 Choosing a Display Protocol 19 Using View Persona Management to Retain User Data and Settings Benefits of Using View Desktops in Local Mode 23 Accessing USB Devices Connected to a Local Computer 24 Printing from a View
VMware Horizon View Architecture Planning Choosing a User Authentication Method 64 Restricting View Desktop Access 66 Using Group Policy Settings to Secure View Desktops 67 Implementing Best Practices to Secure Client Systems 68 Assigning Administrator Roles 68 Preparing to Use a Security Server 69 Understanding Horizon View Communications Protocols 74 6 Overview of Steps to Setting Up a Horizon View Environment 81 Index 83 4 VMware, Inc.
VMware Horizon View Architecture Planning ® VMware Horizon View Architecture Planning provides an introduction to VMware Horizon View™, including a description of its major features and deployment options and an overview of how the components are typically set up in a production environment.
VMware Horizon View Architecture Planning 6 VMware, Inc.
Introduction to Horizon View 1 With Horizon View, IT departments can run virtual desktops in the datacenter and deliver desktops to employees as a managed service. End users gain a familiar, personalized environment that they can access from any number of devices anywhere throughout the enterprise or from home. Administrators gain centralized control, efficiency, and security by having desktop data in the datacenter.
VMware Horizon View Architecture Planning Convenience The unified management console is built for scalability on Adobe Flex, so that even the largest Horizon View deployments can be efficiently managed from a single View Manager interface. Wizards and dashboards enhance the workflow and facilitate drilling down to see details or change settings. Figure 1-1 provides an example of the browser-based user interface for View Administrator. Figure 1-1.
Chapter 1 Introduction to Horizon View n If View desktops use the space-efficient disk format available with vSphere 5.1 and later, stale or deleted data within a guest operating system is automatically reclaimed with a wipe and shrink process. Hardware Independence Virtual machines are hardware-independent.
VMware Horizon View Architecture Planning Scalability features depend on the VMware virtualization platform to manage both desktops and servers: n Integrate with VMware vSphere to achieve cost-effective densities, high levels of availability, and advanced resource allocation control for your virtual desktops. n Use the Horizon View storage accelerator feature to support end-user logins at larger scales with the same storage resources.
Chapter 1 Introduction to Horizon View Figure 1-2.
VMware Horizon View Architecture Planning View Connection Server This software service acts as a broker for client connections. View Connection Server authenticates users through Windows Active Directory and directs the request to the appropriate virtual machine, physical or blade PC, or Windows Terminal Services server.
Chapter 1 Introduction to Horizon View n View Open Client, which supports the VMware partner certification program. View Open Client is not an official View client and is not supported as such. View Portal To use View Portal, end users on a Windows, Linux, or Mac PC or laptop open a Web browser and enter the URL of a View Connection Server instance. View Portal provides links for downloading the installers for the full View Client.
VMware Horizon View Architecture Planning vCenter Server This service acts as a central administrator for VMware ESX/ESXiservers that are connected on a network. vCenter Server, provides the central point for configuring, provisioning, and managing virtual machines in the datacenter.
Chapter 1 Introduction to Horizon View n IT managers can use the Horizon Workspace Administrator Web interface to monitor user and group entitlements to View desktops. Integrating Horizon View with Business Intelligence Software You can configure View Connection Server to record events to a Microsoft SQL Server or Oracle database. n End-user actions such as logging in and starting a desktop session. n Administrator actions such as adding entitlements and creating desktop pools.
VMware Horizon View Architecture Planning You can use VMware and Microsoft command-line tools to export and import LDAP configuration data in LDAP Data Interchange Format (LDIF) files from and into Horizon View. These commands are for advanced administrators who want to use scripts to update configuration data without using View Administrator or View PowerCLI. You can use LDIF files to perform a number of tasks. n Transfer configuration data between View Connection Server instances.
2 Planning a Rich User Experience VMware Horizon View provides the familiar, personalized desktop environment that end users expect. For example, on some client systems, end users can access USB and other devices connected to their local computer, send documents to any printer that their local computer can detect, authenticate with smart cards, and use multiple display monitors. Horizon View includes many features that you might want to make available to your end users.
VMware Horizon View Architecture Planning Table 2-1. View Agent Operating System Support (Continued) Guest Operating System Version Edition Service Pack Windows Vista 32-bit Business and Enterprise SP1 and SP2 Windows XP 32-bit Professional SP3 Windows 2008 R2 Terminal Server 64-bit Standard SP1 Windows 2008 Terminal Server 64-bit Standard SP2 Table 2-2.
Chapter 2 Planning a Rich User Experience In addition, several VMware partners offer thin client devices for Horizon View deployments. The features that are available for each thin client device are determined by the vendor and model and the configuration that an enterprise chooses to use. For information about the vendors and models for thin client devices, see the Thin Client Compatibility Guide, available on the VMware Web site.
VMware Horizon View Architecture Planning n 32-bit color is supported for virtual displays. n ClearType fonts are supported. n Copy and paste of text and images between a Windows-based client operating system and a View desktop is supported, up to 1MB. Supported file formats include text, images, and RTF (Rich Text Format). You cannot copy and paste system objects such as folders and files between systems. For information about which client devices support specific PCoIP features, go to https://www.
Chapter 2 Planning a Rich User Experience Microsoft RDP Remote Desktop Protocol is the same multichannel protocol many people already use to access their work computer from their home computer. Microsoft Remote Desktop Connection (RDC) uses RDP to transmit data. Microsoft RDP provides the following features: n With RDP 6, you can use multiple monitors in span mode. RDP 7 has true multiple monitor support, for up to 16 monitors.
VMware Horizon View Architecture Planning n During logon, by default, Horizon View downloads only the files that Windows requires, such as user registry files. Other files are copied to the View desktop when the user or an application opens them from the profile folder in the View desktop. You can configure Horizon View to download specified files when the user logs in and download other files in the background.
Chapter 2 Planning a Rich User Experience n Migrate user profiles from physical systems to View desktops. n Perform a staged migration from physical systems to View desktops. n Support up-to-date profiles when users go offline. Limitations View Persona Management has the following limitations and restrictions: n You must have a Horizon View license that includes the View Personal Management component. n View Persona Management requires a CIFS (Common Internet File System) share.
VMware Horizon View Architecture Planning Check-outs When the View desktop is checked out, a snapshot is taken in vCenter Server, to preserve the state of the virtual machine. The vCenter Server version of the desktop is locked so that no other users can access it. When a View desktop is locked, vCenter Serveroperations are disabled, including operations such as powering on the online desktop, taking snapshots, and editing the virtual machine settings.
Chapter 2 Planning a Rich User Experience You can specify which types of USB devices end users are allowed to connect to. For composite devices that contain multiple types of devices, such as a video input device and a storage device, on some client systems, you can split the device so that one device (for example, the video input device) is allowed but the other device (for example, the storage device) is not.
VMware Horizon View Architecture Planning n MMR is not supported on all versions of Windows clients and virtual desktops. To find out whether this feature is supported on a particular type of client, see the feature support matrix included in the "Using VMware Horizon View Client" document for the specific type of desktop or mobile client device. Go to https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html.
Managing Desktop Pools from a Central Location 3 You can create pools that include one or hundreds or thousands of virtual desktops. As a desktop source, you can use virtual machines, physical machines, and Windows Terminal Services servers. Create one virtual machine as a base image, and Horizon View can generate a pool of virtual desktops from that image. You can easily install or stream applications to pools with VMware ThinApp.
VMware Horizon View Architecture Planning In addition, using desktop pools provides many conveniences. Dedicated-assignment pools Each user is assigned a particular View desktop and returns to the same virtual desktop at each login. Users can personalize their desktops, install applications, and store data. Floating-assignment pools The virtual desktop is optionally deleted and re-created after each use, offering a highly controlled environment.
Chapter 3 Managing Desktop Pools from a Central Location n You can deploy a desktop pool on a cluster that contains up to 32 ESXi hosts, with certain restrictions. Replica disks must be stored on VMFS5 or later datastores or NFS datastores. If you store replicas on a VMFS version earlier than VMFS5, a cluster can have at most eight hosts. OS disks and persistent disks can be stored on NFS or VMFS datastores.
VMware Horizon View Architecture Planning Using local datastores is most likely to work well if the View desktops in your environment are stateless. For example, you might use local datastores if you deploy stateless kiosks or classroom and training stations. If you intend to take advantage of the benefits of local storage, you must carefully consider the following limitations: n You cannot use VMotion, VMware High Availability (HA), or vSphere Distributed Resource Scheduler (DRS).
Chapter 3 Managing Desktop Pools from a Central Location You can create a View Composer persistent disk that contains user settings and other user-generated data. This persistent disk is not affected by a recompose operation. When a linked clone is deleted, you can preserve the user data. When an employee leaves the company, another employee can access the departing employee's user data. A user who has multiple desktops can consolidate the user data on a single desktop.
VMware Horizon View Architecture Planning If your company allows users to install applications, you can continue your current policies, but you cannot take advantage of View Composer features such as refreshing and recomposing the desktop. With View Composer, if an application is not virtualized or otherwise included in the user's profile or data settings, that application is discarded whenever a View Composer refresh, recompose, or rebalance operation occurs.
Architecture Design Elements and Planning Guidelines 4 A typical Horizon View architecture design uses a pod strategy that consists of components that support up to 10,000 virtual desktops using a vSphere 5.1 or later infrastructure. Pod definitions can vary, based on hardware configuration, Horizon View and vSphere software versions used, and other environment-specific design factors.
VMware Horizon View Architecture Planning n Estimating Memory Requirements for Virtual Desktops on page 35 RAM costs more for servers than it does for PCs. Because the cost of RAM is a high percentage of overall server hardware costs and total storage capacity needed, determining the correct memory allocation is crucial to planning your desktop deployment.
Chapter 4 Architecture Design Elements and Planning Guidelines Estimating Memory Requirements for Virtual Desktops RAM costs more for servers than it does for PCs. Because the cost of RAM is a high percentage of overall server hardware costs and total storage capacity needed, determining the correct memory allocation is crucial to planning your desktop deployment. If the RAM allocation is too low, storage I/O can be negatively affected because too much Windows paging occurs.
VMware Horizon View Architecture Planning RAM Sizing Impact on Storage The amount of RAM that you allocate to a virtual machine is directly related to the size of the certain files that the virtual machine uses. To access the files in the following list, use the Windows guest operating system to locate the Windows page and hibernate files, and use the ESX/ESXi host's file system to locate the ESX/ESXi swap and suspend files. Windows page file By default, this file is sized at 150 percent of guest RAM.
Chapter 4 Architecture Design Elements and Planning Guidelines When you consider these requirements, note that virtual machine configuration of allocated RAM does not change. That is, you do not need to allocate 1GB of RAM for applications and another 31MB for dual 1080p monitors. Instead, consider the overhead RAM when calculating the total physical RAM required for each ESX/ESXi host. Add the guest operating system RAM to the overhead RAM and multiply by the number of virtual machines.
VMware Horizon View Architecture Planning n Schedule antivirus and software updates to run at nonpeak hours, when few users are likely to be logged in. n Stagger or randomize when updates occur. n Use an antivirus product that is compatible with the VMware vShield API. For example, this API has been ® integrated into VMware vCloud Networking and Security 5.1.
Chapter 4 Architecture Design Elements and Planning Guidelines Horizon View ESX/ESXi Node A node is a single VMware ESX/ESXi host that hosts virtual machine desktops in a Horizon View deployment. Horizon View is most cost-effective when you maximize the consolidation ratio, which is the number of desktops hosted on an ESX/ESXi host.
VMware Horizon View Architecture Planning Desktop Pools for Specific Types of Workers Horizon View provides many features to help you conserve storage and reduce the amount of processing power required for various use cases. Many of these features are available as pool settings. The most fundamental question to consider is whether a certain type of user needs a stateful desktop image or a stateless desktop image.
Chapter 4 Architecture Design Elements and Planning Guidelines Pools for Task Workers You can standardize on stateless desktop images for task workers so that the image is always in a well-known, easily supportable configuration and so that workers can log in to any available desktop. Because task workers perform repetitive tasks within a small set of applications, you can create stateless desktop images, which help conserve storage space and processing requirements.
VMware Horizon View Architecture Planning n Use vStorage thin provisioning so that at first, each desktop uses only as much storage space as the disk needs for its initial operation. n For power users and knowledge workers who must install their own applications, which adds data to the operating system disk, create full virtual machine desktops. n If knowledge workers do not require user-installed applications except for temporary use, you can create View Composer linked-clone desktops.
Chapter 4 Architecture Design Elements and Planning Guidelines Additional Recommendations Targeting Minimal Capital Expenditure You can reduce the number of ESX/ESXi hosts required for your local mode pool if you increase the number of virtual machines per ESX/ESXi host. An ESX/ESXi 4.1 host can accommodate up to 500 virtual machines if most are not powered on at the same time, as is frequently the case for local mode pools.
VMware Horizon View Architecture Planning n Use an Active Directory GPO (group policy object) to configure location-based printing, so that the desktop uses the nearest printer. For a complete list and description of the settings available through Group Policy administrative (ADM) templates, see the VMware Horizon View Administration document.
Chapter 4 Architecture Design Elements and Planning Guidelines Table 4-4.
VMware Horizon View Architecture Planning Table 4-5.
Chapter 4 Architecture Design Elements and Planning Guidelines Table 4-7. Connection Server Virtual Machine Example (Continued) Item Example Virtual SCSI adapter type LSI Logic SAS (the default for Windows Server 2008) Virtual network adapter VMXNET 3 1 NIC 1 Gigabit View Connection Server Cluster Design Considerations You can deploy multiple replicated View Connection Server instances in a group to support load balancing and high availability.
VMware Horizon View Architecture Planning Table 4-9.
Chapter 4 Architecture Design Elements and Planning Guidelines In cases where availability requirements are high, proper configuration of VMware HA is essential. If you use VMware HA and are planning for a fixed number of desktops per server, run each server at a reduced capacity. If a server fails, the capacity of desktops per server is not exceeded when the desktops are restarted on a different host.
VMware Horizon View Architecture Planning Storage and Bandwidth Requirements Several considerations go into planning for shared storage of desktops, planning for storage bandwidth requirements with regard to I/O storms, and planning network bandwidth needs. Details about the storage and networking components used in a test setup at VMware are provided in these related topics.
Chapter 4 Architecture Design Elements and Planning Guidelines View desktop storage tier n 500GB LUN for infrastructure n 75GB LUNs for replica stores (1 per desktop pool cluster) Two RAID 1/0 storage pools: For pool 1: n 360 15K 300GB HDD (47TB usable) n 97 450GB LUNs for desktops For pool 2: n 296 15K 300GB HDD (39TB usable) n 7 450GB LUNs for infrastructure n 85 450GB LUNs for desktops This storage strategy is illustrated in the following figure. Figure 4-1.
VMware Horizon View Architecture Planning From an architectural perspective, View Composer creates desktop images that share a base image, which can reduce storage requirements by 50 percent or more. You can further reduce storage requirements by setting a refresh policy that periodically returns the desktop to its original state and reclaims space that is used to track changes since the last refresh operation. If you use View Composer with vSphere 5.
Chapter 4 Architecture Design Elements and Planning Guidelines With the PCoIP display protocol, if you have an enterprise LAN with 100Mb or a 1Gb switched network, your end users can expect excellent performance under the following conditions: n Two monitors (1920x1080) n Heavy use of Microsoft Office applications n Heavy use of Flash-embedded Web browsing n Frequent use of multimedia with limited use of full screen mode n Frequent use of USB-based peripherals n Network-based printing For more
VMware Horizon View Architecture Planning Virtual VMotiondvswitch (1 uplink per host) Infra-dvswitch (2 uplink per host) Desktop-dvswitch (2 uplink per host) n One 1Gb vLAN for the management network n One 1Gb vLAN for the VMotion network n One 10Gb vLAN for the infrastructure network This switch was used by the ESXi hosts of infrastructure, parent, and desktop virtual machines. n Jumbo Frame (9000 MTU) n 1 Ephemeral Distributed Port Group n Private VLAN and 192.168.x.
Chapter 4 Architecture Design Elements and Planning Guidelines n Peak logon rate was 400/min, or 6.67/second. Time Required for Provisioning a Pool Pools are provisioned either up front, when you create the pool, or on demand, as users are assigned to them. Provisioning means creating the virtual machine and configuring it to use the correct operating system image and network settings.
VMware Horizon View Architecture Planning For information about the controls introduced with View 5 that you can use to adjust the way PCoIP consumes bandwidth, see “Optimization Controls Available with PCoIP,” on page 53.
Chapter 4 Architecture Design Elements and Planning Guidelines Horizon View Building Blocks A building block consists of physical servers, a vSphere infrastructure, Horizon View servers, shared storage, and virtual machine desktops for end users. You can include up to five building blocks in a Horizon View pod. Table 4-12.
VMware Horizon View Architecture Planning If a View Connection Server instance fails or becomes unresponsive during an active session, users do not lose data. Desktop states are preserved in the virtual machine desktop so that users can connect to a different View Connection Server instance and their desktop session resumes from where it was when the failure occurred. Figure 4-2.
Chapter 4 Architecture Design Elements and Planning Guidelines Advantages of Using Multiple vCenter Servers in a Pod When you create a design for a Horizon View production environment that accommodates more than 500 desktops, several considerations affect whether to use one vCenter Server instance rather than multiple instances. Starting with Horizon View 5.2, VMware supports managing up to 10,000 desktop virtual machines within a single Horizon View pod with a single vCenter 5.1 server.
VMware Horizon View Architecture Planning In addition to these automated options for vCenter Server failover, you can also choose to rebuild the failed server on a new virtual machine or physical server. Most key information is stored in the vCenter Server database. Risk tolerance is an important factor in determining whether to use one or multiple vCenter Server instances in your pod design.
Planning for Security Features 5 VMware Horizon View offers strong network security to protect sensitive corporate data. For added security, you can integrate Horizon View with certain third-party user-authentication solutions, use a security server, and implement the restricted entitlements feature.
VMware Horizon View Architecture Planning n Tunneled Client Connections with Microsoft RDP on page 62 When users connect to a View desktop with the Microsoft RDP display protocol, View Client can make a second HTTPS connection to the View Connection Server host. This connection is called the tunnel connection because it provides a tunnel for carrying RDP data.
Chapter 5 Planning for Security Features n Because Horizon View manages the HTTPS connection, the reliability of the underlying protocols is significantly improved. If a user temporarily loses a network connection, the HTTP connection is reestablished after the network connection is restored and the RDP connection automatically resumes without requiring the user to reconnect and log in again.
VMware Horizon View Architecture Planning The desktop has a lifetime controlled through policy. If the client loses contact with View Connection Server, the maximum time without server contact is the period in which the user can continue to use the desktop before the user is refused access. On the client side, this expiration policy is stored in a file that is encrypted by a key that is built into the application.
Chapter 5 Planning for Security Features Using Two-Factor Authentication You can configure a View Connection Server instance so that users are required to use RSA SecurID authentication or RADIUS (Remote Authentication Dial-In User Service) authentication. With Horizon View 5.1 and later releases, RADIUS support has been added to the two-factor authentication feature included with Horizon View: n RADIUS support offers a wide range of alternative two-factor token-based authentication options.
VMware Horizon View Architecture Planning Using the Log In as Current User Feature Available with Windows-Based View Client With View Client for Windows, when users select the Log in as current user check box, the credentials that they provided when logging in to the client system are used to authenticate to the View Connection Server instance and to the View desktop. No further user authentication is required.
Chapter 5 Planning for Security Features For example, your Horizon View deployment might include two View Connection Server instances. The first instance supports your internal users. The second instance is paired with a security server and supports your external users. To prevent external users from accessing certain desktops, you could set up restricted entitlements as follows: n Assign the tag "Internal" to the View Connection Server instance that supports your internal users.
VMware Horizon View Architecture Planning n Enable single sign-on for smart card authentication in View Client. n Configure server SSL certificate checking in View Client. n Prevent users from providing credential information with View Client command line options. n Prevent non-View client systems from using RDP to connect to View desktops. You can set this policy so that connections must be View-managed, which means that users must use View Client to connect to View desktops.
Chapter 5 Planning for Security Features 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. A security server resides within a DMZ and acts as a proxy host for connections inside your trusted network.
VMware Horizon View Architecture Planning Figure 5-2. Load-Balanced Security Servers in a DMZ remote View Client external network DMZ load balancing View Security Servers View Connection Servers Microsoft Active Directory vCenter Management Server ESX hosts running Virtual Desktop virtual machines When remote users connect to a security server, they must successfully authenticate before they can access View desktops.
Chapter 5 Planning for Security Features Figure 5-3. Multiple Security Servers remote View Client external network View Client internal network DMZ load balancing View Security Servers load balancing View Connection Servers vCenter Management Server Microsoft Active Directory ESX hosts running Virtual Desktop virtual machines You must implement a hardware or software load balancing solution if you install more than one security server.
VMware Horizon View Architecture Planning Figure 5-4.
Chapter 5 Planning for Security Features Table 5-1. Front-End Firewall Rules Source Default Port Protocol Destination Default Port View Client TCP Any HTTP Security Server TCP 80 (Optional) External client devices connect to a security server within the DMZ on TCP port 80 and are automatically directed to HTTPS. For information about the security considerations related to letting users connect with HTTP rather than HTTPS, see the VMware Horizon View Security guide.
VMware Horizon View Architecture Planning Table 5-2. Back-End Firewall Rules (Continued) Source Default Port Protocol Destination Default Port Security server TCP Any RDP View desktop TCP 3389 Security servers connect to View desktops on TCP port 3389 to exchange RDP traffic. Security server TCP Any MMR View desktop TCP 4927 Security servers connect to View desktops on TCP port 9427 to receive MMR traffic.
Chapter 5 Planning for Security Features Figure 5-5. Horizon View Components and Protocols Without a Security Server View Client RDP Client View Client PCoIP RDP HTTP(S) View Secure GW Server & PCoIP Secure GW View Connection Server View Messaging View Broker & Admin Server View Administrator HTTP(S) SOAP vCenter Server View Manager LDAP JMS RDP PCoIP View Agent View desktop virtual machine NOTE This figure shows direct connections for clients using either PCoIP or RDP.
VMware Horizon View Architecture Planning Figure 5-6.
Chapter 5 Planning for Security Features Table 5-3. Default Ports (Continued) Protocol Port PCoIP TCP port 4172 from View Client to the View desktop. PCoIP also uses UDP port 4172 in both directions. PCoIP or RDP For USB redirection, TCP port 32111 is used alongside PCoIP or RDP from the client to the View desktop.
VMware Horizon View Architecture Planning View LDAP View LDAP is an embedded LDAP directory in View Connection Server and is the configuration repository for all Horizon View configuration data. View LDAP contains entries that represent each View desktop, each accessible View desktop, multiple View desktops that are managed together, and View component configuration settings.
Chapter 5 Planning for Security Features Table 5-5. TCP Ports Opened During View Agent Installation (Continued) Protocol Ports MMR 9427 PCoIP 4172 (TCP and UDP) The View Agent installation program configures the local firewall rule for inbound RDP connections to match the current RDP port of the host operating system, which is typically 3389. If you change the RDP port number, you must change the associated firewall rules.
VMware Horizon View Architecture Planning 80 VMware, Inc.
Overview of Steps to Setting Up a Horizon View Environment 6 Complete these high-level tasks to install Horizon View and configure an initial deployment. Table 6-1. Horizon View Installation and Setup Check List Step Task 1 Set up the required administrator users and groups in Active Directory. Instructions: VMware Horizon View Installation and vSphere documentation 2 If you have not yet done so, install and set up ESX/ESXi hosts and vCenter Server.
VMware Horizon View Architecture Planning 82 VMware, Inc.
Index Symbols .
VMware Horizon View Architecture Planning H P HA cluster 45, 46, 48 hardware requirements, PCoIP 19 Horizon Workspace 7 parent virtual machine 29, 30 PCoIP, hardware requirements 19 PCoIP Secure Gateway connection 62, 69, 77 persistent disks 29 persona management, configuring and managing 21 Persona Management 9 physical PCs 46 pod design 59 policies, desktop 32 pools desktop 29, 40 kiosk users 43 knowledge workers 41 local mode users 42 task workers 41 pools, desktop 13, 27 power users 34 printers 17 p
Index security servers best practices for deploying 69 firewall rules for 72 implementing 69 load balancing 69 overview 12 PCoIP Secure Gateway 77 setup, VMware View 81 shared storage 28, 50 single sign-on (SSO) 13, 26, 66 smart card authentication 65 smart card readers 24, 65 snapshots 30 software provisioning 31 storage, reducing, with View Composer 28, 29 storage bandwidth 52 storage configurations 50 streaming applications 31 streaming multimedia 25 suspend files 35, 38 swap files 35 T tablets 11 task
VMware Horizon View Architecture Planning 86 VMware, Inc.
