Reviewer's Guide for View in VMware Horizon 7: Desktop Pools ...

TECHNICAL WHITE PAPER – AUGUST 2017

REVIEWER’S GUIDE FOR VIEW IN VMWARE HORIZON 7: DESKTOP POOLS VMware Horizon 7 version 7.x

REVIEWER’S GUIDE FOR VIEW IN VMWARE HORIZON 7: DESKTOP POOLS

Table of Contents Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 JMP – Next-Generation Desktop and Application Delivery Platform. . . . . . . . . . . . . . . . . . . . . . . . . . 3 Purpose of This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Intended Audience for This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Section A: Single-User Desktops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Exercise A1: Deploying a Linked-Clone Desktop Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Exercise A2: Deploying a Full-Clone Desktop Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Section B: Session-Based RDSH Desktop Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Exercise B1: Creating an RDSH Server Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 Exercise B2: Deploying an RDSH Desktop Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Alll Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Appendix: Terminology Used in This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 About the Author and Contributors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

T E C H N I C A L W H I T E PA P E R | 2


Introduction Welcome to the Reviewer’s Guide for View in VMware Horizon 7: Desktop Pools. This guide shows you how to automate the process of making as many identical virtual desktops as you need. The View component (formerly the product called Horizon View) of VMware Horizon® 7 offers a virtual desktop infrastructure (VDI) and remote applications through Remote Desktop Session Host (RDSH). Desktop and application delivery are done through a single platform, which simplifies desktop administration and operations and enhances the user experience. By centrally maintaining desktops, applications, and data, Horizon 7 uses View to reduce costs, improve security, and increase availability and flexibility for end users. Horizon 7 includes JMP, the next-generation desktop and application delivery platform from VMware.

JMP – Next-Generation Desktop and Application Delivery Platform JMP (pronounced jump) represents capabilities in VMware Horizon 7 Enterprise Edition that deliver Just-in-Time Desktops and Apps in a flexible, fast, and personalized manner. JMP is composed of the following VMware technologies: • VMware Instant Clone Technology for fast desktop and RDSH provisioning • VMware App Volumes™ for real-time application delivery • VMware User Environment Manager™ for contextual policy management JMP allows components of a desktop or RDSH server to be decoupled and managed independently in a centralized manner, yet reconstituted on demand to deliver a personalized user workspace when needed. JMP is supported with both on-premises and cloud-based Horizon 7 deployments, providing a unified and consistent management platform regardless of your deployment topology. The JMP approach provides several key benefits, including simplified desktop and RDSH image management, faster delivery and maintenance of applications, and elimination of the need to manage “full persistent” desktops.

Purpose of This Guide The Reviewer’s Guide for View in VMware Horizon 7: Desktop Pools is one of a series of guides to help you evaluate the View component of Horizon 7. This guide provides exercises to demonstrate the process of creating full-clone desktop pools, linked-clone desktop pools, and session-based virtual desktops provided by RDSH servers. For instant-clone desktop pools, see the Reviewer’s Guide for View in VMware Horizon 7: Instant Clones. For an overview of View in Horizon 7 and information about key features, such as publishing applications and configuring Smart Policies, see All Guides. Important: This guide is designed for evaluation purposes only. It uses the minimum required resources for a basic deployment and does not explore all possible features. Do not use this evaluation environment as a template for deploying a production environment. To deploy a production environment, see VMware Horizon 7 Documentation.

Intended Audience for This Guide This guide is intended for IT administrators and product evaluators who want to install Horizon 7 and deploy a remote desktop environment. Both current and new users can benefit from using this guide. Familiarity with VMware vSphere® and VMware vCenter Server® is assumed. Some familiarity with other technologies is helpful, including networking and storage in a virtual environment, Active Directory, identity management, directory services, Simple Mail Transfer Protocol (SMTP), and RSA SecurID.



Before You Begin This guide is fifth in the series. We recommend that you follow the guides in order. For information about all guides in the series, see All Guides. Before you can perform the exercises in this guide, you must have the following infrastructure components installed and configured: • VMware vSphere 6.0 Update 1 or later, including vCenter Server 6.0 Update 1 or later. VMware vSphere 6.5 or later is recommended. For more information, see VMware vSphere 6 Documentation. • VMware ESXi™ host or hosts configured in the vCenter Server instance • An authentication infrastructure that includes Active Directory, DNS, DHCP, and Certificate Authority setup • View Connection Server, version 7.0 or later, set up as described in the Reviewer’s Guide for View in VMware Horizon 7: Installation and Configuration. Note: View Connection Server version 7.2 or later is recommended and is required if you plan to create instant-clone farms of RDSH servers. • A master image of the virtual machine on which the remote desktops will be based. For instructions, see the Reviewer’s Guide for View in VMware Horizon 7: Preparing Virtual Machines for Desktop Pools.

Section A: Single-User Desktops With single-user desktops, each virtual machine allows a single end-user connection at a time. In contrast, with session-based desktops, one RDSH server can accommodate many concurrent user connections. This section provides exercises for creating various types of pools that contain Windowsbased single-user desktops. • Exercise A1: Deploying a Linked-Clone Desktop Pool • Exercise A2: Deploying a Full-Clone Desktop Pool For instant-clone desktop pools, see the Reviewer’s Guide for View in VMware Horizon 7: Instant Clones. For Linux-based desktops, see Setting Up Horizon 7 for Linux Desktops. Exercises for session-based RDSH virtual desktops are provided in Section B.



Exercise A1: Deploying a Linked-Clone Desktop Pool Linked clones allow administrators to easily create and manage pools of similar desktops. Because linked-clone desktops share a base system-disk image, they use less storage than full VMs. All linkedcloned desktops can be patched or updated by updating the master VM and VM snapshot. Important: This exercise assumes that you have created the master VM and snapshot on which to base the linked-clone desktops. Creating the master image is the subject of the Reviewer’s Guide for View in VMware Horizon 7: Preparing Virtual Machines for Desktop Pools. 1. Verify that your environment includes the following prerequisites: • View Composer installed and configured according to the instructions in the Reviewer’s Guide for View in VMware Horizon 7: Installation and Configuration. A prerequisite for configuring View Composer is a vCenter Server account with permissions to create and delete computer objects and write properties in the domain. When you complete the Add Desktop Pool wizard, in one of the later steps of this procedure, you will be prompted to select this domain and user account. • (Optional) An organizational unit (OU) in Active Directory for linked-clone computer accounts. When you complete the Add Desktop Pool wizard, in one of the later steps of this procedure, you will be prompted to select this OU. For the purposes of this exercise, you can select the Computers OU instead of creating a new OU for linked clones. The benefit of having an OU specifically for a linked-clone desktop pool is that you can create group policies and apply them specifically to that OU. You can also delegate control of the OU to subordinate groups, such as server operators or individual users. • (Optional) A VM folder in the vCenter Server inventory. Having a specific folder in the vCenter Server inventory helps you locate and manage the virtual desktops in the linked-clone pool. 2. Log in to Horizon Administrator, and navigate to Catalog > Desktop Pools. 3. Click Add.



4. In the Add Desktop Pool wizard, select Automated Desktop Pool and click Next.

5. On the User Assignment page, select Floating and click Next. Linked-clone pools can use either floating or dedicated user assignment. For this exercise, we use floating assignment. • With a dedicated assignment, each desktop is assigned to a specific user. A user logging in for the first time gets a desktop that is not assigned to another user. The user always gets this same desktop after logging in, and this desktop is not available to any other user. • With a floating assignment, users get a random desktop every time they log in. When a user logs out, the desktop is either refreshed and returned to the pool or deleted, depending on pool settings. With automatic deletion, you keep only as many VMs as you need at one time.



6. On the vCenter Server page, select View Composer linked clones, select the vCenter Server, and click Next.

7. Complete the Desktop Pool Identification page and click Next. You must add a pool ID. If you do not provide a display name, the pool ID is used for the display name. If you do not specify an access group, the pool is placed in the root access group. For more information, see Configuring Role-Based Delegated Administration in View Administration.



8. On the Desktop Pool Settings page, complete the following settings and click Next. • Leave State set to Enabled. • Select VMware Blast to use Blast Extreme as the default display protocol. You can use any display protocol, but the new Blast Extreme display protocol is optimized for all types of devices. • Set HTML Access to Enabled. Because you are enabling HTML Access, you can access your desktop from a browser if you do not want to install VMware Horizon Client later. • For assistance with selecting the other settings, click the ? icon next to the setting, or use the default setting.



9. On the Provisioning Settings page, change the following settings and click Next. • Enter a naming pattern for the VMs, as described in the Naming Pattern panel of the Provisioning Settings page. For example, for this exercise, you can use Win-10-LC-. This naming pattern helps you identify Windows 10 linked clones in Horizon Administrator. • Set the maximum number of machines to 10 or fewer (for the purposes of this exercise). In a production environment, linked-clone pools have been tested to support up to 2,000 desktops. • Select Provision machines on demand, and set the minimum number of machines to 2.



10. On the View Composer Disks page, click Next. Disposable files consist of the paging file and the system-level Temp directory. The default is to redirect disposable files to a nonpersistent disk that will be deleted automatically when a user’s session ends. 11. On the Storage Optimization page, select Select separate datastores for replica and OS disks and click Next. For this exercise, use separate datastores so that you can see the extra settings on the next page. With separate datastores, you can place the replica VM on a solid-state, disk-backed datastore. Solid-state disks have low storage capacity but high read performance, typically supporting 20,000 IOPS. Separate datastores are used in tiered-storage models.

T E C H N I C A L W H I T E PA P E R | 1 0


12. On the vCenter Settings page, click Browse next to each text box to make your selections and click Next. When making your selections, use the following guidelines: • Parent VM – Select the master VM that you created for linked clones in the Reviewer’s Guide for View in VMware Horizon 7: Preparing Virtual Machines for Desktop Pools. • Snapshot – Select the snapshot of the master VM that you created. • VM folder location – If you do not have a folder created, select the data center, and click OK. • Linked clone datastores and Replica disk datastores – If you are not using a tiered-storage model, you can select the same datastore for replicas and clones.

13. On the Advanced Storage Options page, click Next. For the purposes of this exercise, you can use the defaults, but make sure to read the Advanced Storage Options page and the embedded help text on the page to learn about the storage features available for linked clones.



14. On the Guest Customization page, use the following settings and click Next. • Domain – Select the domain and user that were used when configuring View Composer settings. • AD container – Click Browse and navigate to the Computers OU in Active Directory or, if you created a specific OU for linked-clone computer objects, select that OU. • Use QuickPrep – Select this option. When you create linked-clone machines, you must modify each VM so that it can function as a unique computer on the network. QuickPrep and Microsoft Sysprep provide different approaches to customization. Because QuickPrep runs faster than Sysprep, and because QuickPrep does not require you to create a customization specification, use QuickPrep for this exercise.

Note: For this exercise, you do not enter scripts. In a production environment, you can specify that a script run immediately after a clone is created. You can also run another script before the clone is powered off. These scripts can invoke any process that can be created with the Windows CreateProcess API, such as CMD, VBScript (VBS), EXE, and batch-file processes. 15. On the Ready to Complete page, click Finish. You return to the Catalog > Desktop Pools inventory list. The new pool appears in the list.



16. Double-click the desktop pool to check the deployment status.

In the bottom Machine Status pane, the Machine Status area displays the VM state. The state changes from Provisioning to Customizing to Available. For example, in this figure, the Machine Status area shows that 2 virtual desktops are in the customization phase. Note: To create another linked-clone pool, you can select this pool on the Desktop Pools page and click Clone to clone this pool. The pool’s settings are copied into the Add Desktop Pool wizard, allowing you to create a new pool without having to fill in each setting manually. You can clone full-clone and linked-clone desktop pools.

Exercise A2: Deploying a Full-Clone Desktop Pool A full clone is an independent copy of a VM. It shares nothing with its master VM, and it operates entirely separately from the master VM used to create it. In this exercise, you create full-clone desktops with dedicated user assignment. Before Horizon 7 was released, full-clone dedicated desktops were created for users who needed to install their own applications. This requirement was weighed against the management overhead required to maintain each individual full clone and all the data and applications installed in the VM. With Horizon 7 and VMware App Volumes, you have the alternative of creating Just-in-Time Desktops. You can combine instant-clone desktops with App Volumes writable disks, which allow users to install their own applications. This strategy allows you to create disposable desktops that retain user customizations, personas, and user-installed apps from session to session, even though the cloned desktop is destroyed when the user logs out. Users experience a stateful desktop, while the enterprise realizes the economy of stateless desktops. For more information, see JMP and VMware Horizon 7 Deployment Considerations. Important: This exercise assumes that you have created the master VM template on which to base the full-clone desktops. Creating the master image is the subject of the Reviewer’s Guide for View in VMware Horizon 7: Preparing Virtual Machines for Desktop Pools.



1. If you do not already have a Microsoft Sysprep customization specification for the Windows 10 guest operating system, use the Guest Customization wizard in the vSphere Client to create one. For instructions, see the topics about using the Guest Customization wizard in VMware vSphere 6 Documentation. You will select this customization specification when completing the Add Desktop Pool wizard. VMware recommends that you test a customization specification in vSphere before you use it to create a desktop pool. When you use a Sysprep customization specification to join a Windows desktop to a domain, you must use the FQDN of the Active Directory domain. You cannot use the NetBIOS name. 2. Log in to Horizon Administrator, and navigate to Catalog > Desktop Pools. 3. Click Add.



4. In the Add Desktop Pool wizard, select Automated Desktop Pool and click Next.

5. On the User Assignment page, select Dedicated and Enable automatic assignment, and click Next.



6. On the vCenter Server page, select Full virtual machines, select the vCenter Server, and click Next.

7. Complete the Desktop Pool Identification page and click Next. You must add a pool ID. If you do not provide a display name, the pool ID is used for the display name. If you do not specify an access group, the pool is placed in the root access group. For more information, see Configuring Role-Based Delegated Administration in View Administration.



8. On the Desktop Pool Settings page, complete the following settings and click Next. • Leave State set to Enabled. • Select VMware Blast to use Blast Extreme as the default display protocol. You can use any display protocol, but the new Blast Extreme display protocol is optimized for all types of devices. • Set HTML Access to Enabled. Because you are enabling HTML Access, you can access your desktop from a browser if you do not want to install VMware Horizon Client later. • For assistance with selecting the other settings, click the ? icon next to the setting, or use the default setting.



9. On the Provisioning Settings page, change the following settings and click Next. • Enter a naming pattern for the VMs, as described in the Naming Pattern panel of the Provisioning Settings page. For example, for this exercise, you can use Win-10-FC-. This naming pattern helps you identify Windows 10 full clones in Horizon Administrator. • Set the maximum number of machines to 10 or fewer (for the purposes of this exercise). In a production environment, desktop pools have been tested to support up to 2,000 desktops. • Select Provision machines on demand, and use the default minimum of 1.



10. On the Storage Optimization page, click Next. 11. On the vCenter Settings page, click Browse next to each text box to make your selections and click Next. When making your selections, use the following guidelines: • Template – Select the VM template that you created for full clones in the Reviewer’s Guide for View in VMware Horizon 7: Preparing Virtual Machines for Desktop Pools. • VM folder location – If you do not have a folder created, select the data center, and click OK.

12. On the Advanced Storage Options page, click Next. 13. On the Guest Customization page, select the Sysprep customization specification and click Next.



14. On the Ready to Complete page, click Finish. You return to the Catalog > Desktop Pools inventory list. The new pool appears in the list. 15. Double-click the desktop pool to check the deployment status.

In the bottom Machine Status pane, one desktop is being customized and will soon be available. For this exercise, you selected to provision the desktops on demand, with a minimum of one desktop available. Note: To create another full-clone pool, you can select this pool on the Desktop Pools page and click Clone, to clone this pool. The pool’s settings are copied into the Add Desktop Pool wizard, allowing you to create a new pool without having to fill in each setting manually. You can clone full-clone and linked-clone desktop pools.

Section B: Session-Based RDSH Desktop Pools An RDSH desktop pool has different characteristics than a full-clone or linked-clone automated desktop pool. An RDSH desktop pool is based on a session to an RDSH server. This section provides exercises for creating a pool of session-based virtual desktops. The exercises are sequential and build upon one another, so make sure to complete each exercise before moving on to the next. The exercises cover the following topics: • Exercise B1: Creating an RDSH Server Farm • Exercise B2: Deploying an RDSH Desktop Pool



Exercise B1: Creating an RDSH Server Farm A farm can contain from 1 to 200 RDSH servers. For the exercises in this guide, you manually add a single RDSH VM to an RDSH server farm before creating a desktop pool. Another option is to create an automated farm of RDSH servers, which is similar to creating an automated pool of linked-clone or instant-clone desktops. Creating an automated farm is beyond the scope of this guide but is included in the Quick-Start Guide: Publishing Applications in VMware Horizon 7. Important: This exercise assumes that you have created and prepared an RDSH server VM. Creating this VM is the subject of the Reviewer’s Guide for View in VMware Horizon 7: Preparing Virtual Machines for Desktop Pools. 1. Log in to Horizon Administrator, and navigate to Resources > Farms. 2. Click Add.



3. In the Add Farm wizard, select Manual Farm and click Next.



4. On the Identification and Settings page, change the following settings and click Next. • Add a farm ID. • Select VMware Blast to use Blast Extreme as the default display protocol. You can use any display protocol, but the new Blast Extreme display protocol is optimized for all types of devices. • Set HTML Access to Enabled. Because you are enabling HTML Access, you can access your desktop from a browser if you do not want to install VMware Horizon Client later. • For assistance with selecting the other settings, click the ? icon next to the setting, or use the default setting.

5. On the Select RDS Hosts page, select the RDSH server you prepared and click Next.



6. On the Ready to Complete page, click Finish.

You are returned to the Farms list and the newly created farm is added to the list.



Exercise B2: Deploying an RDSH Desktop Pool Now that you have created an RDSH server farm, you can select that farm when creating your desktop pool. 1. Log in to Horizon Administrator, and navigate to Catalog > Desktop Pools. 2. Click Add.

3. In the Add Desktop Pool wizard, select RDS Desktop Pool and click Next.



4. Complete the Desktop Pool Identification page and click Next. You must add a pool ID. If you do not provide a display name, the pool ID is used for the display name.

5. On the Desktop Pool Settings page, click Next. Note: For RDSH desktop pools, the Desktop Pool Settings page has far fewer options than for linked-clone or full-clone pools. For RDSH desktops, many of the settings appear in farm settings rather than desktop pool settings.



6. On the Select an RDS Farm page, select Select an RDS farm for this desktop pool, click the farm name in the list, and click Next.

Note: As an alternative to creating the RDSH server farm before you complete this Add Desktop Pool wizard, you can select Create a new RDS farm. If you use this option, additional pages are added to this wizard, and you are prompted to specify farm settings and select the RDSH server or servers to add to the farm. 7. On the Ready to Complete page, click Finish. You return to the Catalog > Desktop Pools inventory list. The new pool appears in the list.



8. Double-click the desktop pool to check the deployment status.

In the bottom Machine Status pane, the Machine Status area displays the VM state. The state changes from Customizing to Provisioning to Available. For example, in this figure, the Machine Status area shows that 1 virtual desktop is available.

Summary The Reviewer’s Guide for View in VMware Horizon 7: Desktop Pools is one of a series of guides that explore the View component of VMware Horizon 7. This guide provided exercises to explore and evaluate the process of creating a full-clone desktop pool, a linked-clone desktop pool, and a session-based RDSH desktop pool. Before end users can log in to a virtual desktop, you must entitle one or more users to the desktop. Entitled users can log in by using a natively installed Horizon Client or by opening a browser and using HTML Access. For more information, see the Reviewer’s Guide for View in VMware Horizon 7: Provisioning Users.



All Guides You can explore many key features and capabilities in the Reviewer’s Guide series for View in Horizon 7: • Overview • Installation and Configuration • Preparing Virtual Machines for Desktop Pools • Instant Clones • Desktop Pools • Publishing Applications with VMware Horizon 7 • Smart Policies • Provisioning Users Note: For information about features that are not covered in this series of guides, see VMware Horizon 7 Documentation.



Appendix: Terminology Used in This Guide The following terms are used in this guide: Instant clone

A rapidly generated and nonpersistent clone of a powered-on virtual machine. An instant clone provides users with a virtual desktop in seconds.

Linked clone

A copy of a master virtual machine that shares virtual disks with it by using a snapshot. This conserves disk space and ensures all users receive the same software installation.

Linked-clone desktop

The user interface of a linked clone which is remotely displayed to a user, and which provides a nonpersistent environment, that can be refreshed or recomposed.

Master virtual machine (VM)

A single desktop source that is used to deploy a group of virtual desktops or virtual machines. A master virtual machine is sometimes referred to as a master image, desktop image or golden image. In a physical environment, a master virtual machine can be referred to as a disk image file.

Recompose

A process by which changes are made to a master virtual machine, and new linked clones are created from that revised master virtual machine. This allows administrators to quickly provide an updated virtual desktop to multiple users at once.

Refresh

A process by which a linked clone is reverted to the snapshot it uses. This removes the current and nonpersistent state, and allows administrators to easily reset a user’s virtual desktop to a corporate standard.

Snapshot

A set of files that contain the entire state of a virtual machine— its data, memory, and configuration. If you revert to a snapshot, the current state of the virtual machine is lost, and its saved state is restored. Multiple snapshots are differential, and have a parent and child relationship. The files of a child snapshot contain only changes made to its parent snapshot.

Virtual desktop

The user interface of a virtual machine that is made available to an end user.

Virtual machine

A software-based computer, running an operating system or application environment, that is located in the data center and backed by the resources of a physical computer.

For more information about terms, see the VMware Glossary.



Additional Resources For more information about the View component of VMware Horizon 7, you can explore the following resources: • VMware Horizon 7 Hands-On Lab • VMware Horizon 7 (which includes the View component) • VMware Horizon 7 Documentation • VMware Horizon Pricing, Packaging, and Licensing • VMware Knowledge Base • VMware Product Evaluation • VMware Product Guide • VMware Product Interoperability Matrixes • What’s New with VMware Horizon 7 (VMware blog post) • White papers • Self-help resources • VMware vSphere and VMware vCenter Server resources ––Product overview ––Product documentation ––White papers and other resources • VMware consultation and support ––VMware Horizon Support Center ––VMware Consulting Professional Services Organization

About the Author and Contributors The Reviewer’s Guide for View in VMware Horizon 7: Desktop Pools was written by Caroline Arakelian, Senior Technical Marketing Manager, End-User-Computing Technical Marketing, VMware, with appreciation and acknowledgement for considerable contributions from Graeme Gordon, Senior End-User-Computing Architect, End-User-Computing Technical Marketing, VMware. The Reviewer’s Guide for View was originally written by Marilyn Basanta, Group Manager, End-User-Computing Solution Engineering, VMware. To comment on this paper, contact VMware End-User-Computing Technical Marketing at [email protected].


VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com

Copyright © 2017 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. Item No: 5135-VMW-WP-HORIZON72-RG-DESKTOP_POOLS-USLET-20170811 8/17