Setting Up Desktop and Application Pools in View VMware Horizon 6.0.0 VMware Horizon 6.0.1 VMware Horizon 6.0.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.
Setting Up Desktop and Application Pools in View 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 © 2014 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents Setting Up Desktop and Application Pools in View 7 1 Introduction to Desktop and Application Pools 9 Farms, RDS Hosts, and Desktop and Application Pools 9 Advantages of Desktop Pools 10 Desktop Pools for Specific Types of Workers 11 Advantages of Application Pools 14 2 Preparing Unmanaged Machines 15 Prepare an Unmanaged Machine for Remote Desktop Deployment 15 Install View Agent on an Unmanaged Machine 15 3 Creating and Preparing Virtual Machines 19 Creating Virtual Machines for Remote Des
Setting Up Desktop and Application Pools in View Worksheet for Creating a Manual Desktop Pool 77 Create a Manual Desktop Pool 79 Create a Manual Pool That Contains One Machine Desktop Pool Settings for Manual Pools 80 79 7 Setting Up Remote Desktop Services Hosts 83 Remote Desktop Services Hosts 83 Install Remote Desktop Services on Windows Server 2008 R2 85 Install Remote Desktop Services on Windows Server 2012 or 2012 R2 85 Install Desktop Experience on Windows Server 2008 R2 86 Install Desktop Expe
Contents Review Desktop or Application Pool Entitlements 128 Restricting Remote Desktop Access 128 13 Configuring Remote Desktop Features 133 Configuring Unity Touch 133 Configuring Flash URL Redirection for Multicast or Unicast Streaming 136 Configuring Real-Time Audio-Video 140 Configuring Scanner Redirection 154 Managing Access to Windows Media Multimedia Redirection (MMR) 158 14 Using USB Devices with Remote Desktops 163 Limitations Regarding USB Device Types 164 Overview of Setting Up USB Redire
Setting Up Desktop and Application Pools in View Migrating User Profiles with View Persona Management 241 Persona Management and Windows Roaming Profiles 243 Configuring a View Persona Management Deployment 244 Best Practices for Configuring a View Persona Management Deployment View Persona Management Group Policy Settings 256 253 18 Troubleshooting Machines and Desktop Pools 265 Display Problem Machines 265 Send Messages to Desktop Users 266 Troubleshooting Desktop Pool Creation Problems 266 Troubles
Setting Up Desktop and Application Pools in View Setting Up Desktop and Application Pools in View describes how to create and provision pools of machines and create pools of remote applications that run on Microsoft Remote Desktop Services (RDS) hosts. It includes information about preparing machines, configuring policies, entitling users and groups, configuring remote desktop features, and configuring user profiles with View Persona Management.
Setting Up Desktop and Application Pools in View 8 VMware, Inc.
Introduction to Desktop and Application Pools 1 With VMware Horizon with View, you can create desktop pools that include one or hundreds or thousands of virtual desktops. You can deploy desktops that run on virtual machines, physical machines, and Windows Remote Desktop Services (RDS) hosts. Create one virtual machine as a base image, and View can generate a pool of virtual desktops from that image. You can also create application pools that give users remote access to applications.
Setting Up Desktop and Application Pools in View Farms Farms are collections of RDS hosts and facilitate the management of those hosts. Farms can have a variable number of RDS hosts and provide a common set of applications or RDS desktops to users. When you create an RDS desktop pool or an application pool, you must specify a farm. The RDS hosts in the farm provide desktop and application sessions to users.
Chapter 1 Introduction to Desktop and Application Pools Desktop Pools for Specific Types of Workers 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.
Setting Up Desktop and Application Pools in View n If applicable, use Virtual SAN datastores. Virtual SAN virtualizes the local physical storage disks available on ESXi hosts into a single datastore shared by all hosts in a vSphere cluster. Virtual SAN also lets you manage virtual machine storage and performance by using storage policy profiles. For more information, see “Using Virtual SAN for High-Performance Storage and Policy-Based Management,” on page 182.
Chapter 1 Introduction to Desktop and Application Pools n If you use View Composer linked-clone desktops, implement View Persona Management, roaming profiles, or another profile management solution. Configure persistent disks so that you can refresh and recompose the linked-clone OS disks while keeping a copy of the user profile on the persistent disks.
Setting Up Desktop and Application Pools in View Advantages of Application Pools With application pools, you give users access to applications that run on servers in a data center instead of on their personal computers or devices. Application pools offer several important benefits: n Accessibility Users can access applications from anywhere on the network. You can also configure secure network access.
Preparing Unmanaged Machines 2 Users can access remote desktops delivered by machines that are not managed by vCenter Server. These unmanaged machines can include physical computers and virtual machines running on virtualization platforms other than vCenter Server. You must prepare an unmanaged machine to deliver remote desktop access. For information about preparing machines that are used as Remote Desktop Services (RDS) hosts, see Chapter 7, “Setting Up Remote Desktop Services Hosts,” on page 83.
Setting Up Desktop and Application Pools in View Prerequisites n Verify that you have administrative rights on the unmanaged machine. n To use an unmanaged Windows Server 2008 R2 machine as a remote desktop rather than as an RDS host, perform the steps described in “Prepare Windows Server 2008 R2 for Desktop Use,” on page 25. n Familiarize yourself with the View Agent custom setup options for unmanaged machines. See “View Agent Custom Setup Options for Unmanaged Machines,” on page 17.
Chapter 2 Preparing Unmanaged Machines View Agent Custom Setup Options for Unmanaged Machines When you install View Agent on an unmanaged machine, you can select or deselect certain custom setup options. In addition, View Agent installs certain features automatically on all guest operating systems on which they are supported. These features are not optional. Table 2‑1.
Setting Up Desktop and Application Pools in View 18 VMware, Inc.
Creating and Preparing Virtual Machines 3 You can use virtual machines managed by vCenter Server to provision and deploy remote desktops. You can use a virtual machine managed by vCenter Server as a template for an automated pool, a parent for a linked-clone pool, or a machine in a manual pool. You must prepare virtual machines to deliver remote desktop access.
Setting Up Desktop and Application Pools in View 5 Install Desktop Experience on Windows Server 2008 R2 on page 26 For RDS desktops and applications, and for VDI desktops that are deployed on single-user virtual machines that run Windows Server, scanner redirection requires that you install the Desktop Experience feature on the RDS hosts and the single-user virtual machines.
Chapter 3 Creating and Preparing Virtual Machines Table 3‑1. Custom Configuration Parameters (Continued) Parameter Description and Recommendations Resource Pool If the physical ESXi server resources are divided into resource pools, you can assign them to the virtual machine. Datastore The location of files associated with the virtual machine. Hardware Machine Version The hardware machine version that is available depends on the ESXi version you are running.
Setting Up Desktop and Application Pools in View Table 3‑1. Custom Configuration Parameters (Continued) Parameter Description and Recommendations SCSI Controller The type of SCSI adapter to use with the virtual machine. For Windows 8, Windows 7, and Windows XP guest operating systems, you should specify the LSI Logic adapter. The LSI Logic adapter has improved performance and works better with generic SCSI devices. LSI Logic SAS is available only for virtual machines with hardware version 7 and later.
Chapter 3 Creating and Preparing Virtual Machines What to do next Prepare the guest operating system for View desktop deployment. Prepare a Guest Operating System for Remote Desktop Deployment You must perform certain tasks to prepare a guest operating system for remote desktop deployment. Prerequisites n Create a virtual machine and install a guest operating system. n Configure an Active Directory domain controller for your remote desktops. See the View Installation document for more information.
Setting Up Desktop and Application Pools in View 7 Install other applications and software, such as smart card drivers if you are using smart card authentication. If you plan to use Workspace to offer a catalog that includes ThinApp applications, you must install Workspace for Windows. On Windows XP systems, install all third-party applications and software (except Microsoft .NET Framework) before you install View Agent. IMPORTANT If you are installing Microsoft .
Chapter 3 Creating and Preparing Virtual Machines Prepare Windows Server 2008 R2 for Desktop Use To use a Windows Server 2008 R2 virtual machine as a single-session View desktop (rather than as an RDS host), you must perform certain steps before you install View Agent in the virtual machine. You must also configure View Administrator to treat Windows Server 2008 R2 as a supported operating system for View desktop use.
Setting Up Desktop and Application Pools in View Install Desktop Experience on Windows Server 2008 R2 For RDS desktops and applications, and for VDI desktops that are deployed on single-user virtual machines that run Windows Server, scanner redirection requires that you install the Desktop Experience feature on the RDS hosts and the single-user virtual machines. Procedure 1 Log in as an administrator. 2 Start Server Manager. 3 Click Features. 4 Click Add Features.
Chapter 3 Creating and Preparing Virtual Machines Procedure 1 To start the View Agent installation program, double-click the installer file. The installer filename is VMware-viewagent-y.y.y-xxxxxx.exe or VMware-viewagent-x86_64-y.y.yxxxxxx.exe, where y.y.y is the version number and xxxxxx is the build number. 2 Accept the VMware license terms.
Setting Up Desktop and Application Pools in View Table 3‑2. View Agent Custom Setup Options 28 Option Description USB Redirection Gives users access to locally connected USB devices on their desktops. USB redirection is supported on remote desktops that are deployed on single-user machines but is not supported on RDS host-based remote desktops. NOTE You can use group policy settings to disable USB redirection for specific users.
Chapter 3 Creating and Preparing Virtual Machines Table 3‑2. View Agent Custom Setup Options (Continued) Option Description View Persona Management Synchronizes the user profile on the local desktop with a remote profile repository, so that users have access to their profiles whenever they log in to a desktop. PCoIP Smartcard Lets users authenticate with smart cards when they use the PCoIP display protocol. This option is not selected by default.
Setting Up Desktop and Application Pools in View Install View Agent Silently You can use the silent installation feature of the Microsoft Windows Installer (MSI) to install View Agent on several Windows virtual machines or physical computers. In a silent installation, you use the command line and do not have to respond to wizard prompts. With silent installation, you can efficiently deploy View components in a large enterprise.
Chapter 3 Creating and Preparing Virtual Machines 2 Type the installation command on one line. This example installs View Agent in a virtual machine that is managed by vCenter Server. The installer configures the View Composer Agent, Virtual Printing, USB redirection, HTML Access, and Real-Time Audio-Video custom setup options and the non-optional features that are installed automatically. VMware-viewagent-y.y.y-xxxxxx.
Setting Up Desktop and Application Pools in View Table 3‑4. Command-Line Options for a View Component's Bootstrap Program Option Description /s Disables the bootstrap splash screen and extraction dialog, which prevents the display of interactive dialogs. For example: VMware-viewconnectionserver-y.y.y-xxxxxx.exe /s The /s option is required to run a silent installation.
Chapter 3 Creating and Preparing Virtual Machines Table 3‑5. MSI Command-Line Options and MSI Properties (Continued) MSI Option or Property Description ADDLOCAL Determines the component-specific options to install. In an interactive installation, the View installer displays custom setup options that you can select or deselect. In a silent installation, you can use the ADDLOCAL property to selectively install individual setup options by specifying the options on the command line.
Setting Up Desktop and Application Pools in View Table 3‑6. MSI Properties for Silently Installing View Agent (Continued) MSI Property Description Default Value UNITY_DEFAULT_APPS Specifies a default list of default favorite applications that are displayed in the Unity Touch sidebar on a mobile device. This property was created to support the Unity Touch component. It is not a general MSI property.
Chapter 3 Creating and Preparing Virtual Machines Table 3‑7. View Agent Silent Installation Options and Interactive Custom Setup Options (Optional) (Continued) Silent Installation Option Custom Setup Option in an Interactive Installation RTAV Real-Time Audio-Video ScannerRedirection Scanner Redirection ThinPrint Virtual Printing V4V vCenter Operations Manager for View VPA View Persona Management Smartcard PCoIP Smartcard. This feature is not installed by default in an interactive installation.
Setting Up Desktop and Application Pools in View Optimize Guest Operating System Performance for All Windows Versions You can perform certain steps to optimize guest operating system performance for remote desktop deployment. The steps apply to all Windows operating systems. All of the steps are optional. These recommendations include turning off the screen saver and not specifying a sleep timer. Your organization might require the use of screen savers.
Chapter 3 Creating and Preparing Virtual Machines Without this optimization, brief freezes can occur, or the videos can stutter. NOTE Making this optimization delivers performance improvements in both ESXi 5.x and ESXi 5.1, but it is required for ESXi 5.1. What to do next For Windows 7 and Windows 8 guest operating systems, perform additional optimization tasks. See “Optimize Windows 7 and Windows 8 Guest Operating System Performance,” on page 37.
Setting Up Desktop and Application Pools in View 2 Click Customer Experience Improvement Program settings. 3 Select No, I don't want to participate in the program and click Save changes. 4 Start the control panel and click Administrative Tools > Task Scheduler. 5 In the Task Scheduler (Local) pane of the Task Scheduler dialog box, expand the Task Scheduler Library > Microsoft > Windows nodes and open the Application Experience folder. 6 Disable the AITAgent and ProgramDataUpdater tasks.
Chapter 3 Creating and Preparing Virtual Machines Overview of Windows 7 and Windows 8 Services and Tasks That Cause LinkedClone Growth Certain services and tasks in Windows 7 and Windows 8 can cause linked-clone OS disks to grow incrementally every few hours, even when the linked-clone machines are idle. If you disable these services and tasks, you can control the OS disk growth. Services that affect OS disk growth also generate IOPS on Windows 7 and Windows 8 virtual machines.
Setting Up Desktop and Application Pools in View Table 3‑9. Impact of Windows 7 and Windows 8 Services and Tasks on OS Disk Growth and IOPS When OS Is Left Idle (Continued) Default Occurrence or Startup Impact on Linked-Clone OS Disks Description Windows Diagnostic Policy Service Detects, troubleshoots, and resolves problems in Windows components. If you stop this service, diagnostics no longer function. Automatic startup Medium to high. The service is triggered on demand.
Chapter 3 Creating and Preparing Virtual Machines Table 3‑9. Impact of Windows 7 and Windows 8 Services and Tasks on OS Disk Growth and IOPS When OS Is Left Idle (Continued) Default Occurrence or Startup Impact on Linked-Clone OS Disks Impact on IOPS Turn Off This Service or Task? Service or Task Description Windows Defender Provides antispyware features. When Windows starts up. Performs a quick scan once a day. Checks for updates before each scan. Medium to high.
Setting Up Desktop and Application Pools in View 5 In the Disk Defragmenter dialog box, click Defragment disk. The Disk Defragmenter consolidates defragmented files on the virtual machine's hard disk. 6 In the Disk Defragmenter dialog box, click Configure schedule. 7 Deselect Run on a schedule (recommended) and click OK. Defragmentation operations will not take place on linked-clone virtual machines that are created from this parent virtual machine.
Chapter 3 Creating and Preparing Virtual Machines 6 In the Diagnostic Policy Service Properties (Local Computer) dialog, click Stop. 7 In the Startup type menu, select Disabled. 8 Click OK. Disable the Prefetch and Superfetch Features on Windows 7 and Windows 8 Virtual Machines By disabling the Windows prefetch and superfetch features, you can avoid generating prefetch files and the overhead associated with prefetch and superfetch operations.
Setting Up Desktop and Application Pools in View Disable the System Restore on Windows 7 and Windows 8 Virtual Machines You do not need to use the Windows System Restore feature if you use View Composer refresh to restore linked-clone OS disks to their original snapshots. When the operating system is idle, System Restore does not have a visible impact on OS-disk growth.
Chapter 3 Creating and Preparing Virtual Machines Procedure 1 In vSphere Client, select the parent virtual machine and select Open Console. 2 Log in to the Windows 7 or Windows 8 guest operating system as an administrator. 3 Click Start > Control Panel > Network and Internet > Internet Options. 4 Click the Content tab. 5 Under Feeds and Web Slices, click Settings. 6 Deselect Automatically check feeds and Web Slices for updates and click OK. 7 In the Internet Properties dialog, click OK.
Setting Up Desktop and Application Pools in View A parent virtual machine that you use for View Composer must either belong to the same Active Directory domain as the domain that the linked-clone machines will join or be a member of the local WORKGROUP. IMPORTANT To use features that are supported in View 4.5 or later, such as redirecting disposable data to a separate disk and customizing linked-clone machines with Sysprep, you must deploy the machines from a parent virtual machine on which View Agent 4.
Chapter 3 Creating and Preparing Virtual Machines n Verify that the system disk contains a single volume. You cannot deploy linked clones from a parent virtual machine that contains more than one volume. The View Composer service does not support multiple disk partitions. Multiple virtual disks are supported.
Setting Up Desktop and Application Pools in View Activating Windows on Linked-Clone Virtual Machines To make sure that View Composer properly activates Windows 8, Windows 7, and Windows Vista operating systems on linked-clone machines, you must use Microsoft volume activation on the parent virtual machine. The volume-activation technology requires a volume license key.
Chapter 3 Creating and Preparing Virtual Machines 3 Disable the hibernation option. Operating System Action Windows 8, Windows 7 or Windows Vista a b c d Windows XP 4 Click Start and type cmd in the Start Search box. In the search results list, right-click Command Prompt and click Run as Administrator. At the User Account Control prompt, click Continue. At the command prompt, type powercfg.exe /hibernate off and press Enter. e Type exit and press Enter. a b Click Start > Run.
Setting Up Desktop and Application Pools in View Keep a Record of the Parent Virtual Machine's Paging-File Size When you create a linked-clone pool, you can redirect the linked clones' guest OS paging and temp files to a separate disk. You must configure this disk to be larger than the paging file in the guest OS.
Chapter 3 Creating and Preparing Virtual Machines Alternatively, you can use your customization script to launch another script or process that performs the long-running task. NOTE Most QuickPrep customization scripts can finish running within the 20-second limit. Test your scripts before you increase the limit. Prerequisites n Install View Agent with the View Composer Agent option on the parent virtual machine. n Verify that the parent virtual machine is prepared to create a linked-clone pool.
Setting Up Desktop and Application Pools in View Creating Customization Specifications Customization specifications are optional, but they can greatly expedite automated pool deployments by providing configuration information for general properties such as licensing, domain attachment, and DHCP settings. With customization specifications, you can customize remote desktops as they are created in View Administrator.
Creating Automated Desktop Pools That Contain Full Virtual Machines 4 With an automated desktop pool that contains full virtual machines, you create a virtual machine template and View uses that template to create virtual machines for each desktop. You can optionally create customization specifications to expedite automated pool deployments.
Setting Up Desktop and Application Pools in View Table 4‑1. Worksheet: Configuration Options for Creating an Automated Pool That Contains Full Virtual Machines Option Description User assignment Choose the type of user assignment: n In a dedicated-assignment pool, each user is assigned to a machine. Users receive the same machine each time they log in to the pool. n In a floating-assignment pool, users receive different machines each time they log in.
Chapter 4 Creating Automated Desktop Pools That Contain Full Virtual Machines Table 4‑1. Worksheet: Configuration Options for Creating an Automated Pool That Contains Full Virtual Machines (Continued) Option Description Desktop Pool Settings Settings that determine the desktop state, power status when a virtual machine is not in use, display protocol, Adobe Flash quality, and so on. For descriptions, see “Desktop Pool Settings for All Desktop Pool Types,” on page 111.
Setting Up Desktop and Application Pools in View Table 4‑1. Worksheet: Configuration Options for Creating an Automated Pool That Contains Full Virtual Machines (Continued) 56 Option Description Minimum number of machines If you use a naming pattern and provision machines on demand, specify a minimum number of machines in the pool. The minimum number of machines is created when you create the pool.
Chapter 4 Creating Automated Desktop Pools That Contain Full Virtual Machines Create an Automated Pool That Contains Full Virtual Machines You can create an automated desktop pool based on a virtual machine template that you select. View dynamically deploys the desktops, creating a new virtual machine in vCenter Server for each desktop. To create a linked-clone pool, see “Linked-Clone Desktop Pools,” on page 59. Prerequisites n Prepare a virtual machine template that View will use to create the machines.
Setting Up Desktop and Application Pools in View Desktop Settings for Automated Pools That Contain Full Virtual Machines You must specify desktop pool settings when you configure automated pools that contain full virtual machines. Different settings apply to pools with dedicated user assignments and floating user assignments. Table 4-2 lists the settings that apply to automated pools with dedicated assignments and floating assignments.
Creating Linked-Clone Desktop Pools 5 With a linked-clone desktop pool, View creates a desktop pool based on a parent virtual machine that you select. The View Composer service dynamically creates a new linked-clone virtual machine in vCenter Server for each desktop.
Setting Up Desktop and Application Pools in View Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool 60 Option Description User assignment Choose the type of user assignment: n In a dedicated-assignment pool, each user is assigned to a machine. Users receive the same machine each time they log in. n In a floating-assignment pool, users receive different machines each time they log in. For details, see “User Assignment in Desktop Pools,” on page 103.
Chapter 5 Creating Linked-Clone Desktop Pools Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool (Continued) Option Description Desktop Pool Settings Settings that determine the machine state, power status when a virtual machine is not in use, display protocol, Adobe Flash quality, and so on. For descriptions, see “Desktop Pool Settings for All Desktop Pool Types,” on page 111.
Setting Up Desktop and Application Pools in View Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool (Continued) 62 Option Description Minimum number of ready (provisioned) machines during View Composer maintenance operations If you specify names manually or use a naming pattern, specify a minimum number of machines that are ready and provisioned while View Composer operations take place.
Chapter 5 Creating Linked-Clone Desktop Pools Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool (Continued) Option Description Disk size and drive letter for persistent disk If you store user profile data on a separate View Composer persistent disk, provide the disk size in megabytes and the drive letter. NOTE Do not select a drive letter that already exists on the parent virtual machine or that conflicts with a drive letter that is used for a network-mounted drive.
Setting Up Desktop and Application Pools in View Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool (Continued) 64 Option Description Select separate datastores for replica and OS disks (Available only if you do not use Virtual SAN) You can store the replica (master) virtual machine disk on a high performance datastore and the linked clones on separate datastores. For details, see “Storing View Composer Replicas and Linked Clones on Separate Datastores,” on page 194.
Chapter 5 Creating Linked-Clone Desktop Pools Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool (Continued) Option Description Datastores Select one or more datastores on which to store the desktop pool. A table on the Select Linked Clone Datastores page of the Add Desktop Pool wizard provides high-level guidelines for estimating the pool's storage requirements. These guidelines can help you determine which datastores are large enough to store the linked-clone disks.
Setting Up Desktop and Application Pools in View Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool (Continued) Option Description Use native NFS snapshots (VAAI) (Available only if you do not use Virtual SAN) If your deployment includes NAS devices that support the vStorage APIs for Array Integration (VAAI), you can use native snapshot technology to clone virtual machines.
Chapter 5 Creating Linked-Clone Desktop Pools Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool (Continued) Option Description Blackout Times Configure days and times during which View Storage Accelerator regeneration and the reclamation of virtual machine disk space do not take place.
Setting Up Desktop and Application Pools in View Table 5‑1. Worksheet: Configuration Options for Creating a Linked-Clone Desktop Pool (Continued) Option Description Use QuickPrep or a customization specification (Sysprep) Choose whether to use QuickPrep or select a customization specification (Sysprep) to configure licensing, domain attachment, DHCP settings, and other properties on the machines. Sysprep is supported for linked clones only on vSphere 4.1 or later software.
Chapter 5 Creating Linked-Clone Desktop Pools n Decide how to configure power settings, display protocol, Adobe Flash quality, and other settings. See “Desktop Pool Settings for All Desktop Pool Types,” on page 111. n If you intend to provide access to your desktops and applications through Workspace, verify that you create the desktop and application pools as a user who has the Administrators role on the root access group in View Administrator.
Setting Up Desktop and Application Pools in View Desktop Pool Settings for Linked-Clone Desktop Pools You must specify machine and desktop pool settings when you configure automated pools that contain linked clones created by View Composer. Different settings apply to pools with dedicated user assignments and floating user assignments. Table 5-2 lists the settings that apply to linked-clone pools with dedicated assignments and floating assignments.
Chapter 5 Creating Linked-Clone Desktop Pools 2 3 View Composer and View customize the linked clone with QuickPrep or a Sysprep customization specification, depending on which customization tool you select when you create the pool. n If you use Sysprep, a unique SID is generated for each clone. n If you use QuickPrep, no new SID is generated. The parent virtual machine's SID is replicated on all provisioned linked-clone machines in the pool. n Some applications generate a GUID during customization.
Setting Up Desktop and Application Pools in View Choosing QuickPrep or Sysprep to Customize Linked-Clone Machines QuickPrep and Microsoft Sysprep provide different approaches to customizing linked-clone machines. QuickPrep is designed to work efficiently with View Composer. Microsoft Sysprep offers standard customization tools. When you create linked-clone machines, you must modify each virtual machine so that it can function as a unique computer on the network.
Chapter 5 Creating Linked-Clone Desktop Pools n Redirects temp and paging files to a separate disk. These steps might require the linked clones to restart one or more times. QuickPrep uses KMS volume license keys to activate Windows 8, Windows 7, and Windows Vista linkedclone machines. For details, see the View Administration document. You can create your own scripts to further customize the linked clones.
Setting Up Desktop and Application Pools in View QuickPrep Script Timeout Limit View Composer terminates a post-synchronization or power-off script that takes longer than 20 seconds. If your script takes longer than 20 seconds, you can increase the timeout limit. For details, see “Increase the Timeout Limit of QuickPrep Customization Scripts,” on page 50. Alternatively, you can use your script to launch another script or process that performs the long-running task.
Chapter 5 Creating Linked-Clone Desktop Pools A recomposition restores the linked clone to its original state, before the customization specification was run the first time. In this state, the linked clone does not have a local computer SID or the GUID of any thirdparty software installed in the system drive. View must run the Sysprep customization specification after the linked clone is recomposed.
Setting Up Desktop and Application Pools in View You can set the Allow reuse of pre-existing computer accounts option when you create a new desktop pool or edit an existing pool. If you edit a pool and set this option, the setting affects linked-clone machines that are provisioned in the future. Linked clones that are already provisioned are not affected.
Creating Manual Desktop Pools 6 In a manual desktop pool, each remote desktop that is accessed by an end user is a separate machine. When you create a manual desktop pool, you select existing machines. You can create a pool that contains a single desktop by creating a manual desktop pool and selecting a single machine.
Setting Up Desktop and Application Pools in View Table 6‑1. Worksheet: Configuration Options for Creating a Manual Desktop Pool Option Description User assignment Choose the type of user assignment: n In a dedicated-assignment pool, each user is assigned to a machine. Users receive the same machine each time they log in. n In a floating-assignment pool, users receive different machines each time they log in. Fill In Your Value Here For details, see “User Assignment in Desktop Pools,” on page 103.
Chapter 6 Creating Manual Desktop Pools Create a Manual Desktop Pool You can create a manual desktop pool that provisions desktops from existing virtual machines or physical computers. You must select the machines that will be included in the desktop pool. For manual pools with virtual machines that are managed by vCenter Server, View ensures that a spare machine is powered on so that users can connect to it. The spare machine is powered on no matter which power policy is in effect.
Setting Up Desktop and Application Pools in View Prerequisites n Prepare the machine to deliver remote desktop access. View Agent must be installed and running on the machine. To prepare a virtual machine managed by vCenter Server, see Chapter 3, “Creating and Preparing Virtual Machines,” on page 19. To prepare an unmanaged virtual machine or physical computer, see Chapter 2, “Preparing Unmanaged Machines,” on page 15. n Gather the configuration information you must provide to create the manual pool.
Chapter 6 Creating Manual Desktop Pools For descriptions of each desktop pool setting, see “Desktop Pool Settings for All Desktop Pool Types,” on page 111. Table 6‑2.
Setting Up Desktop and Application Pools in View 82 VMware, Inc.
Setting Up Remote Desktop Services Hosts 7 Microsoft Remote Desktop Services (RDS) hosts provide desktop sessions and applications that users can access from client devices. If you plan to create RDS desktop pools or application pools, you must first set up RDS hosts.
Setting Up Desktop and Application Pools in View 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.
Chapter 7 Setting Up Remote Desktop Services Hosts Install Remote Desktop Services on Windows Server 2008 R2 Remote Desktop Services (RDS) is one of the roles that a Windows Server can have. You must install this role to set up an RDS host that runs Windows Server 2008 R2. Prerequisites n Verify that the RDS host is running Windows Server 2008 R2 Service Pack 1 (SP1). n Verify that the RDS host is part of the Active Directory domain for the View deployment.
Setting Up Desktop and Application Pools in View 8 On the Select Role Services page, select Remote Desktop Session Host. 9 Follow the prompts and finish the installation. What to do next If you plan to use HTML Access or scanner redirection, install the Desktop Experience feature. The steps for installing Desktop Experience differ on Windows Server 2008 R2 and Windows Server 2012 or 2012 R2. Restrict users to a single desktop session. See “Restrict Users to a Single Session,” on page 87.
Chapter 7 Setting Up Remote Desktop Services Hosts Restrict Users to a Single Session View supports at most one desktop session and one application session per user on an RDS host. You must configure the RDS host to restrict users to a single session. Prerequisites n Install the Remote Desktop Services role as described in “Install Remote Desktop Services on Windows Server 2008 R2,” on page 85 or “Install Remote Desktop Services on Windows Server 2012 or 2012 R2,” on page 85.
Setting Up Desktop and Application Pools in View 5 Select an authentication method to register the RDS host with the View Connection Server instance. Option Description Authenticate as the currently logged in user The Username and Password text boxes are disabled and you are logged in to the View Connection Server instance with your current username and password.
Chapter 7 Setting Up Remote Desktop Services Hosts Enable Time Zone Redirection for RDS Desktop and Application Sessions If an RDS host is in one time zone and a user is in another time zone, by default, when the user connects to an RDS desktop, the desktop displays time that is in the time zone of the RDS host. You can enable the Time Zone Redirection group policy setting to make the RDS desktop display time in the local time zone. This policy setting applies to application sessions as well.
Setting Up Desktop and Application Pools in View 5 Enable the setting Force a specific visual style file or force Windows classic and set the Path to Visual Style as %windir%\resources\Themes\Aero\aero.msstyles. Configure Group Policy to Start Runonce.exe By default, some applications that rely on the Explorer.exe file may not run in an application session. To avoid this issue, you must configure a GPO setting to start runonce.exe.
Chapter 7 Setting Up Remote Desktop Services Hosts Table 7‑4. View Settings Related to Windows Performance Options (Continued) View Setting Registry Value Disable ListView shadow DisableListViewShadow Disable Window Animation DisableWindowAnimation VMware, Inc.
Setting Up Desktop and Application Pools in View 92 VMware, Inc.
Creating Farms 8 A farm is a group of RDS hosts that provides a common set of applications or RDS desktops to users. This chapter includes the following topics: n “Farms,” on page 93 n “Worksheet for Creating a Farm,” on page 94 n “Create a Farm,” on page 95 Farms Farms simplify the task of managing RDS hosts, RDS desktops, and applications in an enterprise. You can create farms to serve groups of users that vary in size or have different desktop or application requirements.
Setting Up Desktop and Application Pools in View n The RDS hosts in a farm can run any supported version of Windows Server. See "System Requirements for Guest Operating Systems" in the View Installation document. IMPORTANT Microsoft recommends that you configure roaming profiles for users separately for each farm.
Chapter 8 Creating Farms Table 8‑1. Worksheet: Configuration Options for Creating a Farm (Continued) Option Description When timeout occurs Determines whether an empty application session is disconnected or logged off after the Empty session timeout limit is reached. Select Disconnect or Log off. A session that is logged off frees up resources, but opening an application takes longer. The default is Disconnect. Log off disconnected session Determines when a disconnected session is logged off.
Setting Up Desktop and Application Pools in View 96 VMware, Inc.
Creating Application Pools 9 One of the tasks that you perform to give users remote access to an application is to create an application pool. Users who are entitled to an application pool can access the application remotely from a variety of client devices.
Setting Up Desktop and Application Pools in View Table 9‑1. Worksheet: Application Properties for Creating an Application Pool Manually Property Description ID Unique name that identifies the pool in View Administrator. This field is required. Display Name Pool name that users see when they log in to Horizon Client. If you do not specify a display name, it will be the same as ID. Version Version of the application. Publisher Publisher of the application. Path Full pathname of the application.
Creating RDS Desktop Pools 10 One of the tasks that you perform to give users remote access to session-based desktops is to create a Remote Desktop Services (RDS) desktop pool. An RDS desktop pool has properties that can satisfy some specific needs of a remote desktop deployment.
Setting Up Desktop and Application Pools in View n RDS desktops do not support View Persona Management. n The copy and paste feature is disabled by default for HTML Access. To enable the feature, see "HTML Access Group Policy Settings" in the chapter "Configuring HTML Access for End Users" in the Using HTML Access document, available from https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html.
Chapter 10 Creating RDS Desktop Pools Configure Adobe Flash Throttling with Internet Explorer for RDS Desktop Pools To ensure that Adobe Flash throttling works with Internet Explorer in RDS desktops, users must enable third-party browser extensions. Procedure 1 Start Horizon Client and log in to a user's desktop. 2 In Internet Explorer, click Tools > Internet Options. 3 Click the Advanced tab, select Enable third-party browser extensions, and click OK. 4 Restart Internet Explorer. VMware, Inc.
Setting Up Desktop and Application Pools in View 102 VMware, Inc.
Provisioning Desktop Pools 11 When you create a desktop pool, you select configuration options that determine how the pool is managed and how users interact with the desktops. These provisioning tasks apply to desktop pools that are deployed on single-user machines. They do not apply to RDS desktop pools. However, the Adobe Flash quality and throttling settings apply to all types of desktop pools, including RDS.
Setting Up Desktop and Application Pools in View Naming Machines Manually or Providing a Naming Pattern You can provision the machines in an automated pool by manually specifying a list of machine names or by providing a naming pattern and the number of machines you want in the pool. These two approaches offer different advantages. If you name machines by specifying a list, you can use your company's naming scheme, and you can associate each machine name with a user.
Chapter 11 Provisioning Desktop Pools Table 11‑1. Naming machines Manually or Providing a machine-Naming Pattern (Continued) Feature Providing a Machine-Naming Pattern Naming Machines Manually Dynamic or fixed pool size Dynamic. If you remove a user assignment from a machine in a dedicated-assignment pool, the machine is returned to the pool of available machines.
Setting Up Desktop and Application Pools in View Prerequisites Make sure that each machine name is unique. You cannot use the names of existing virtual machines in vCenter Server. Procedure 1 Create a text file that contains the list of machine names. If you intend to create a desktop pool with only a few machines, you can type the machine names directly in the Add Desktop Pool wizard. You do not have to create a separate text file.
Chapter 11 Provisioning Desktop Pools Table 11‑2. Maximum Length of the Naming Pattern in a Machine Name If You Set This Number of Machines in the Pool This Is the Maximum Prefix Length 1-99 13 characters 100-999 12 characters 1,000 or more 11 characters Names that contain fixed-length tokens have different length limits. See “Length of the Naming Pattern When You Use a Fixed-Length Token,” on page 107.
Setting Up Desktop and Application Pools in View 2 In View Administrator, create the pool and specify machine names manually. 3 Click Enter Names and copy your list into the Enter Machine Names list box. 4 Repeat these steps for the second pool, using the names VDIABC-11 through VDIABC-20. For detailed instructions, see “Specify a List of Machine Names,” on page 105. You can add machines to each pool after it is created.
Chapter 11 Provisioning Desktop Pools In this example, two machines are added. The second machine is associated with a user: Desktop-001 Desktop-002,abccorp.com/jdoe NOTE In a floating-assignment pool, you cannot associate user names with machine names. The machines are not dedicated to the associated users. In a floating-assignment pool, all machines that are not currently in use remain accessible to any user who logs in.
Setting Up Desktop and Application Pools in View Customizing Machines in Maintenance Mode Maintenance mode prevents users from accessing their desktops. If you start machines in maintenance mode, View places each machine in maintenance mode when the machine is created. In a dedicated-assignment pool, you can use maintenance mode to log in to a machine without having to reassign ownership to your own administrator account.
Chapter 11 Provisioning Desktop Pools Desktop Pool Settings for All Desktop Pool Types You must specify machine and desktop pool settings when you configure automated pools that contain full virtual machines, linked-clone desktop pools, manual desktop pools, and RDS desktop pools. Not all settings apply to all types of desktop pools. Table 11‑4. Desktop Pool Setting Descriptions Setting Options State n n Enabled. After being created, the desktop pool is enabled and ready for immediate use. Disabled.
Setting Up Desktop and Application Pools in View Table 11‑4. Desktop Pool Setting Descriptions (Continued) Setting Options Refresh OS disk after logoff Select whether and when to refresh the OS disks for dedicated-assignment, linked-clone virtual machines. n Never. The OS disk is never refreshed. n Always. The OS disk is refreshed every time the user logs off. n Every. The OS disk is refreshed at regular intervals of a specified number of days. Type the number of days.
Chapter 11 Provisioning Desktop Pools Table 11‑4. Desktop Pool Setting Descriptions (Continued) Setting Options Max number of monitors If you use PCoIP as the display protocol, you can select the Maximum number of monitors on which users can display the desktop. When the 3D Renderer setting is not selected, the Max number of monitors setting affects the amount of VRAM that is assigned to machines in the pool. When you increase the number of monitors, more memory is consumed on the associated ESXi hosts.
Setting Up Desktop and Application Pools in View Table 11‑4. Desktop Pool Setting Descriptions (Continued) Setting Options Override global Mirage settings To specify the same Mirage server for all desktop pools, use the global View configuration setting rather than this pool-specific setting. Mirage Server configuration Allows you to specify the URL of a Mirage server, using the format mirage://server-name:port or mirages://server-name:port. Here server-name is the fully qualified domain name.
Chapter 11 Provisioning Desktop Pools Setting Power Policies for Desktop Pools You can configure a power policy for the virtual machines in a desktop pool if the virtual machines are managed by vCenter Server. Power policies control how a virtual machine behaves when its associated desktop is not in use. A desktop is considered not in use before a user logs in and after a user disconnects or logs off.
Setting Up Desktop and Application Pools in View Table 11‑7. Power Policies (Continued) Power Policy Description Suspend The virtual machine enters a suspended state when a user logs off, but not when a user disconnects. You can also configure machines in a dedicated pool to be suspended when a user disconnects without logging off. To configure this policy, you must set an attribute in View LDAP. See “Configure Dedicated Machines To Be Suspended After Users Disconnect,” on page 117.
Chapter 11 Provisioning Desktop Pools Table 11‑8. When View Applies the Power Policy (Continued) Desktop Pool Type The power policy is applied ... Manual pool with dedicated assignment To unassigned machines only. On assigned machines, power operations are initiated by session management. Virtual machines are powered on when a user requests an assigned machine and are powered off or suspended when the user logs off.
Setting Up Desktop and Application Pools in View The View Agent service running on the machine confirms the availability of the machine to View Connection Server. When you configure an automated pool, you can specify the minimum and maximum number of virtual machines that must be provisioned and the number of spare machines that must be kept powered on and available at any given time.
Chapter 11 Provisioning Desktop Pools Power Policy Example for Automated Pools with Dedicated Assignments Unlike a powered-on machine in an automated pool with floating assignments, a powered-on machine in an automated pool with dedicated assignments is not necessarily available. It is available only if the machine is not assigned to a user. Table 11-11 describes the dedicated-assignment, automated pool in this example. Table 11‑11.
Setting Up Desktop and Application Pools in View Configuring 3D Rendering on Windows 7 or Later Desktops When you create or edit a Windows 7 or later desktop pool, you can configure 3D graphics rendering for your desktops.
Chapter 11 Provisioning Desktop Pools Configuring 3D Rendering You select options to determine the way View manages 3D rendering. For details, see “3D Rendering Options,” on page 121. When you enable the 3D Renderer setting, you can configure the amount of VRAM that is assigned to the virtual machines in the pool by moving the slider in the Configure VRAM for 3D guests dialog box. The minimum VRAM size is 64MB.
Setting Up Desktop and Application Pools in View Table 11‑12. 3D Renderer Options for Pools Running on vSphere 5.1 or Later (Continued) Option Description Hardware 3D rendering is enabled. The ESXi host reserves GPU hardware resources on a first-come, firstserved basis as virtual machines are powered on. The ESXi host allocates VRAM to a virtual machine based on the value that is set in the Configure VRAM for 3D Guests dialog box.
Chapter 11 Provisioning Desktop Pools With the Hardware option, you must strictly control your vSphere environment: n For vSGA (Virtual Shared Graphics Acceleration), all ESXi hosts must be version 5.1 or later and must have GPU graphics cards installed. n For vDGA (Virtual Dedicated Graphics Acceleration), all ESXi hosts must be version 5.5 or later and must have GPU graphics cards installed.
Setting Up Desktop and Application Pools in View Prevent Access to View Desktops Through RDP In certain View environments, it is a priority to prohibit access to View desktops through the RDP display protocol. You can prevent users and administrators from using RDP to access View desktops by configuring pool settings and a group policy setting. By default, while a user is logged in to a View desktop session, you can use RDP to connect to the virtual machine from outside of View.
Chapter 11 Provisioning Desktop Pools Configuring Desktop Pools on Clusters With More Than Eight Hosts In vSphere 5.1 and later, you can deploy a linked clone desktop pool on a cluster that contains up to 32 ESXi hosts. All ESXi hosts in the cluster must be version 5.1 or later. The hosts can use VMFS or NFS datastores. VMFS datastores must be VMFS5 or later. In vSphere 5.
Setting Up Desktop and Application Pools in View 126 VMware, Inc.
Entitling Users and Groups 12 You configure entitlements to control which remote desktops and applications your users can access. You can also configure the restricted entitlements feature to control desktop access based on the View Connection Server instance that users connect to when they select remote desktops. In a Cloud Pod Architecture environment, you create global entitlements to entitle users or groups to multiple desktops across multiple pods in a pod federation.
Setting Up Desktop and Application Pools in View 3 Click Add, select one or more search criteria, and click Find to find users or groups based on your search criteria. NOTE Domain local groups are filtered out of search results for mixed-mode domains. You cannot entitle users in domain local groups if your domain is configured in mixed mode. 4 Select the users or groups you want to entitle to the desktops or applications in the pool and click OK. 5 Click OK to save your changes.
Chapter 12 Entitling Users and Groups When users log in through a tagged View Connection Server instance, they can access only those desktop pools that have at least one matching tag or no tags. NOTE You cannot configure the restricted entitlements feature to restrict access to remote applications. n Restricted Entitlement Example on page 129 This example shows a View deployment that includes two View Connection Server instances. The first instance supports internal users.
Setting Up Desktop and Application Pools in View Figure 12‑1.
Chapter 12 Entitling Users and Groups Considerations and Limitations for Restricted Entitlements Before implementing restricted entitlements, you must be aware of certain considerations and limitations. n A single View Connection Server instance or desktop pool can have multiple tags. n Multiple View Connection Server instances and desktop pools can have the same tag. n Desktop pools that do not have any tags can be accessed by any View Connection Server instance.
Setting Up Desktop and Application Pools in View Procedure 1 In View Administrator, select Catalog > Desktop Pools. 2 Select the pool that you want to assign a tag to. 3 Option Action Assign a tag to a new pool Click Add to start the Add Desktop Pool wizard and define and identify the pool. Assign a tag to an existing pool Select the pool and click Edit. Go to the Desktop Pool Settings page.
Configuring Remote Desktop Features 13 Certain remote desktop features that are installed with View Agent can be updated in Feature Pack Update releases as well as in core View releases. You can configure these features to enhance the remote desktop experience of your end users. These features include HTML Access, Unity Touch, Flash URL Redirection, Real-Time Audio-Video, Windows Media Multimedia Redirection (MMR), and USB Redirection.
Setting Up Desktop and Application Pools in View System Requirements for Unity Touch Horizon Client software and the mobile devices on which you install Horizon Client must meet certain version requirements to support Unity Touch. View desktop Horizon Client software Mobile device operating systems To support Unity Touch, the following software must be installed in the virtual machine that the end user will access: n You install the Unity Touch feature by installing View Agent 6.0 or later.
Chapter 13 Configuring Remote Desktop Features n Run the View Agent installer from the command line on the virtual machines NOTE Unity Touch assumes that shortcuts to applications are located in the Programs folder in the Start menu. If any shortcut is located outside of the Programs folder, attach the prefix Programs to the shortcut path. For example, Windows Update.lnk is located in the ProgramData\Microsoft\Windows\Start Menu folder.
Setting Up Desktop and Application Pools in View n (Optional) Create a default list of favorite applications by creating an administrative installation package from the View Agent installer. a From the command line, use the following format to create the administrative installation package. VMware-viewagent-x86_64-y.y.y-xxxxxx.
Chapter 13 Configuring Remote Desktop Features The Flash URL redirection feature uses a JavaScript that is embedded inside an HTML Web page by the Web page administrator. Whenever a remote desktop user clicks on the designated URL link from within a Web page, the JavaScript intercepts and redirects the SWF file from the remote desktop session to the client endpoint. The endpoint then opens a local Flash Projector outside of the remote desktop session and plays the media stream locally.
Setting Up Desktop and Application Pools in View Horizon Client software The following Horizon Client releases support multicast and unicast: n Horizon Client 2.2 for Linux or a later release n Horizon Client 2.2 for Windows or a later release The following Horizon Client releases support multicast only (they do not support unicast): Horizon Client computer or client access device n Horizon Client 2.0 or 2.1 for Linux n Horizon Client 5.
Chapter 13 Configuring Remote Desktop Features Set Up the Web Pages That Provide Multicast or Unicast Streams To allow Flash URL redirection to take place, you must embed a JavaScript command in the MIME HTML (MHTML) Web pages that provide links to the multicast or unicast streams. Users display these Web pages in the browsers on their remote desktops to access the video streams.
Setting Up Desktop and Application Pools in View Procedure u Install Adobe Flash Player on your client devices. Operating System Action Windows Install Adobe Flash Player 10.1 or later for Internet Explorer. Linux a Install the libexpat.so.0 file, or verify that this file is already installed. Ensure that the file is installed in the /usr/lib or /usr/local/lib directory. b Install the libflashplayer.so file, or verify that this file is already installed.
Chapter 13 Configuring Remote Desktop Features When a conferencing or video application is launched, it displays and uses these VMware virtual devices, which handle the audio-video redirection from the locally-connected devices on the client. The VMware Virtual Webcam and Microphone appear in the Device Manager on the desktop operating system. NOTE Real-Time Audio-Video also installs an earlier version of the VMware Virtual Webcam.
Setting Up Desktop and Application Pools in View Horizon Client computer or client access device Display protocol for View n All operating systems that run Horizon Client for Windows. n All operating systems that run Horizon Client for Linux on x86 devices. This feature is not supported on ARM processors. n Mac OS X Mountain Lion (10.8) and later. It is disabled on all earlier Mac OS X operating systems.
Chapter 13 Configuring Remote Desktop Features Selecting Preferred Webcams and Microphones If a client computer has more than one webcam and microphone, you can configure a preferred webcam and default microphone that Real-Time Audio-Video will redirect to the desktop. These devices can be built in or connected to the local client computer. On a Windows client computer, you select a preferred webcam by setting a registry key value.
Setting Up Desktop and Application Pools in View Procedure 1 Attach the webcam you want to use. 2 Start a call and then stop a call. This process creates a log file. 3 Open the debug log file with a text editor. Operating System Log File Location Windows XP C:\Documents and Settings\username\Local Settings\Application Data\VMware\VDM\Logs\debug-20YY-MM-DDXXXXXX.txt Windows 7 or Windows 8 C:\Users\%username %\AppData\Local\VMware\VDM\Logs\debug-20YY-MM-DD-XXXXXX.
Chapter 13 Configuring Remote Desktop Features This procedure describes how to choose a microphone from the user interface of the client system. Administrators can also configure a preferred microphone by using the Mac OS X defaults system. See “Configure a Preferred Webcam or Microphone on a Mac OS X Client System,” on page 146. IMPORTANT If you are using a USB microphone, do not connect it from the Connection > USB menu in Horizon Client.
Setting Up Desktop and Application Pools in View Table 13‑1. Command Syntax for Real-Time Audio-Video Configuration (Continued) Command Description defaults write com.vmware.rtav IsDisabled value Determines whether Real-Time Audio-Video is enabled or disabled. Real-Time Audio-Video is enabled by default. (This value is not in effect.) To disable Real-Time Audio-Video on the client, set the value to true. defaults read com.vmware.rtav Displays Real-Time Audio-Video configuration settings.
Chapter 13 Configuring Remote Desktop Features 2 Find log entries for the webcam or microphone in the Real-Time Audio-Video log file. a In a text editor, open the Real-Time Audio-Video log file. The Real-Time Audio-Video log file is named ~/Library/Logs/VMware/vmware-RTAV-pid.log, where pid is the process ID of the current session. b Search the Real-Time Audio-Video log file for entries that identify the attached webcams or microphones.
Setting Up Desktop and Application Pools in View The next time you connect to a remote desktop and start a new call, the desktop uses the preferred webcam or microphone that you configured, if it is available. If the preferred webcam or microphone is not available, the remote desktop can use another available webcam or microphone. Select a Default Microphone on a Linux Client System If you have multiple microphones on your client system, only one of them is used on your View desktop.
Chapter 13 Configuring Remote Desktop Features n Verify that you have a USB microphone or another type of microphone installed and operational on your client system. n Verify that you are using the PCoIP display protocol for your remote desktop. Procedure 1 Launch the client, and start a webcam or microphone application to trigger an enumeration of camera devices or audio devices to the client log. a Attach the webcam or audio device you want to use.
Setting Up Desktop and Application Pools in View 2 Find log entries for the webcam or microphone. a Open the debug log file with a text editor. The log file with real-time audio-video log messages is located at /tmp/vmware-/vmwareRTAV-.log. The client log is located at /tmp/vmware-/vmware-view-.log. b Search the log file to find the log file entries that reference the attached webcams and microphones.
Chapter 13 Configuring Remote Desktop Features 3 Copy the description of the device and use it to set the appropriate property in the /etc/vmware/config file. ® For a webcam example, copy Microsoft LifeCam HD-6000 for Notebooks to specify the Microsoft webcam as the preferred webcam and set the property as follows: ® rtav.srcWCamId="Microsoft LifeCam HD-6000 for Notebooks" For this example you could also set the property to rtav.srcWCamId="Microsoft".
Setting Up Desktop and Application Pools in View Procedure 1 Download the View GPO Bundle .zip file from the VMware Horizon (with View) download site at http://www.vmware.com/go/downloadview. The file is named VMware-Horizon-View-Extras-Bundle-x.x.x-yyyyyyy.zip, where x.x.x is the version and yyyyyyy is the build number. All ADM and ADMX files that provide group policy settings for View are available in this file. 2 Unzip the VMware-Horizon-View-Extras-Bundle-x.x.x-yyyyyyy.
Chapter 13 Configuring Remote Desktop Features Group Policy Setting Description Disable RTAV When you enable this setting, the Real-Time Audio-Video feature is disabled. When this setting is not configured or disabled, Real-Time Audio-Video is enabled. This setting is located in the View RTAV Configuration folder. Max frames per second Determines the maximum rate per second at which the webcam can capture frames.
Setting Up Desktop and Application Pools in View Table 13‑2. Sample Bandwidth Results for Sending Real-Time Audio-Video Data from Horizon Client to View Agent Image Resolution (Width x Height) Bandwidth Used (Kbps) 160 x 120 225 320 x 240 320 640 x 480 600 Configuring Scanner Redirection By using scanner redirection, View users can scan information in their remote desktops and applications with scanning and imaging devices that are connected locally to their client computers.
Chapter 13 Configuring Remote Desktop Features n Windows Server 2012 R2 configured as an RDS host IMPORTANT The Desktop Experience feature must be installed on Windows Server guest operating systems, whether they are configured as desktops or as RDS hosts. The scanner device drivers do not have to be installed on the desktop operating system where View Agent is installed. Horizon Client software Horizon Client 3.
Setting Up Desktop and Application Pools in View n When you operate a TWAIN scanner, the TWAIN Scanner Redirection for VMware Horizon menu provides additional options for selecting regions of an image, scanning in color, black and white, or grayscale, and choosing other common functions.
Chapter 13 Configuring Remote Desktop Features Procedure 1 Download the View GPO Bundle .zip file from the VMware Horizon (with View) download site at http://www.vmware.com/go/downloadview. The file is named VMware-Horizon-View-Extras-Bundle-x.x.x-yyyyyyy.zip, where x.x.x is the version and yyyyyyy is the build number. All ADM and ADMX files that provide group policy settings for View are available in this file. 2 Unzip the VMware-Horizon-View-Extras-Bundle-x.x.x-yyyyyyy.
Setting Up Desktop and Application Pools in View Group Policy Setting Description Hide Webcam Prevents webcams from appearing in the scanner selection menu in the VMware Horizon Scanner Redirection Preferences dialog box. This setting is available as a Computer Configuration and User Configuration policy. By default, webcams can be redirected to desktops and applications. Users can select webcams and use them as virtual scanners to capture images.
Chapter 13 Configuring Remote Desktop Features Enabling Multimedia Redirection in View You can take steps to ensure that MMR is accessible only to Horizon Client systems that have sufficient resources to handle local multimedia decoding and that are connected to View on a secure network. By default, the global policy in View Administrator, Multimedia redirection (MMR) is set to Deny. To use MMR, you must explicitly set this value to Allow.
Setting Up Desktop and Application Pools in View Multimedia Redirection Support on Desktop Operating Systems In Horizon 6.0.2 and later, the Windows Media Multimedia Redirection (MMR) and Wyse MMR components are installed with View Agent. The Wyse MMR component operates on Windows XP and Windows Vista desktops. In Horizon 6.0.1 and earlier, the Win7 Multimedia Redirection (MMR) and Wyse MMR components are installed with View Agent.
Chapter 13 Configuring Remote Desktop Features Ensure That Clients Can Initiate Windows 7 MMR In Horizon 6.0.1 and earlier, Horizon Client provides the Windows 7 MMR feature for Windows 7 desktops and clients. You can take steps to provide enough time for clients to initiate Windows 7 MMR. Windows 7 MMR uses a handshake between the Horizon Client system and the desktop to validate requests for multimedia redirection.
Setting Up Desktop and Application Pools in View 162 VMware, Inc.
Using USB Devices with Remote Desktops 14 Administrators can configure the ability to use USB devices, such as thumb flash drives, cameras, VoIP (voice-over-IP) devices, and printers, from a remote desktop. This feature is called USB redirection, and it supports using either the RDP or the PCoIP display protocol. A remote desktop can accommodate up to 32 USB devices. When you use this feature, most USB devices that are attached to the local client system become available in the remote desktop.
Setting Up Desktop and Application Pools in View Limitations Regarding USB Device Types Although View does not explicitly prevent any devices from working in a remote desktop, due to factors such as network latency and bandwidth, some devices work better than others. By default, some devices are automatically filtered, or blocked, from being used. In Horizon 6.0.1, together with Horizon Client 3.1 or later, you can plug USB 3.0 devices into USB 3.0 ports on the client machine. USB 3.
Chapter 14 Using USB Devices with Remote Desktops Overview of Setting Up USB Redirection To set up your deployment so that end users can connect removable devices, such as USB flash drives, cameras, and headsets, you must install certain components on both the remote desktop and the client device, and you must verify that the global setting for USB devices is enabled in View Administrator. This checklist includes both required and optional tasks for setting up USB redirection in your enterprise.
Setting Up Desktop and Application Pools in View 2 If the client system is outside the corporate network, the client can connect through a View security server. A security server resides within a DMZ and acts as a proxy host for connections inside your trusted network. 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.
Chapter 14 Using USB Devices with Remote Desktops On Windows clients, as an alternative to using settings that automatically connect all but excluded devices, you can edit a configuration file on the client that sets Horizon Client to reconnect only a specific device or devices, such as smart phones and tablets, to the remote desktop. For instructions, see Using VMware Horizon Client for Windows.
Setting Up Desktop and Application Pools in View When you configure policies for splitting and filtering out USB devices, some values you set require the VID (vendor ID) and PID (product ID) for the USB device. To find the VID and PID, you can search on the Internet for the product name combined with vid and pid. Alternatively, you can look in the client-side log file after you plug in the USB device to the local system when Horizon Client is running.
Chapter 14 Using USB Devices with Remote Desktops If you upgrade Horizon Client, any existing registry settings for USB redirection, such as HardwareIdFilters, remain valid until you define USB policies for Horizon Client. On client devices that do not support client-side USB policies, you can use the USB policies for View Agent to control which USB devices are allowed to be forwarded from the client to a desktop.
Setting Up Desktop and Application Pools in View Manual Device Splitting You can use the Split Vid/Pid Device policy to specify the vendor and product IDs of a composite USB device that you want to split. You can also specify the interfaces of the components of a composite USB device that you want to exclude from redirection. View does not apply any filter policy settings to components that you exclude in this way.
Chapter 14 Using USB Devices with Remote Desktops n For View Agent, se the Exclude VidPid From Split policy to o:vid-xxx_pid-yyyy, where xxx and yyyy are the appropriate IDs. Allow automatic device splitting for desktops and specify policies for splitting specific devices on client computers: n For View Agent, set the Allow Auto Device Splitting policy to Allow - Override Client Setting.
Setting Up Desktop and Application Pools in View Interaction of Client-Interpreted USB Settings The following table shows the modifiers that specify how Horizon Client handles a View Agent filter policy setting for a client-interpreted setting. Table 14‑8. Filter Modifiers for Client-Interpreted Settings Modifier Description Default (d in the registry setting) If a Horizon Client filter policy setting does not exist, Horizon Client uses the View Agent filter policy setting.
Chapter 14 Using USB Devices with Remote Desktops 4 Include Vid/Pid Device 5 Exclude Device Family 6 Include Device Family 7 Allow Audio Input Devices, Allow Audio Output Devices, Allow HIDBootable, Allow HID (Non Bootable and Not Mouse Keyboard), Allow Keyboard and Mouse Devices, Allow Smart Cards, and Allow Video Devices 8 Combined effective Exclude All Devices policy evaluated to exclude or include all USB devices You can set Exclude Path and Include Path filter policy settings only for Horizo
Setting Up Desktop and Application Pools in View n For all users in a desktop pool, block audio and video devices to ensure that these devices will always be available for the Real-Time Audio-Video feature. Use an agent-side setting:: Exclude Device Family: o:video;audio Note that another strategy would be to exclude specific devices by vendor and product ID.
Chapter 14 Using USB Devices with Remote Desktops Table 14‑10. USB Device Families (Continued) Device Family Name Description wireless Wireless networking adapters. wusb Wireless USB devices. USB Settings in the View Agent Configuration ADM Template You can define USB policy settings for both View Agent and Horizon Client.
Setting Up Desktop and Application Pools in View Table 14‑11. View Agent Configuration Template: Device-Splitting Settings Setting Properties Allow Auto Device Splitting Property: AllowAutoDeviceSplitting Allows the automatic splitting of composite USB devices. Exclude Vid/Pid Device From Split Property: SplitExcludeVidPid Excludes a composite USB device specified by vendor and product IDs from splitting. The format of the setting is {m|o}:vid-xxx1_pid-yyy2[;vid-xxx2_pidyyy2]...
Chapter 14 Using USB Devices with Remote Desktops Table 14‑12. View Agent Configuration Template: Agent-Enforced Settings Setting Properties Exclude All Devices Property: ExcludeAllDevices Excludes all USB devices from being forwarded. If set to true, you can use other policy settings to allow specific devices or families of devices to be forwarded. If set to false, you can use other policy settings to prevent specific devices or families of devices from being forwarded.
Setting Up Desktop and Application Pools in View Table 14‑13. View Agent Configuration Template: Client-Interpreted Settings (Continued) Setting Properties Allow Other Input Devices Allows input devices other than hid-bootable devices or keyboards with integrated pointing devices to be forwarded. The default value is undefined. Allow Keyboard and Mouse Devices Property: AllowKeyboardMouse Allows keyboards with integrated pointing devices (such as a mouse, trackball, or touch pad) to be forwarded.
Chapter 14 Using USB Devices with Remote Desktops n Network latency can cause slow device interaction or cause applications to appear frozen because they are designed to interact with local devices. Very large USB disk drives might take several minutes to appear in Windows Explorer. n USB flash cards formatted with the FAT32 file system are slow to load. See http://kb.vmware.com/kb/1022836. n A process or service on the local system opened the device before you connected to the remote desktop.
Setting Up Desktop and Application Pools in View 180 VMware, Inc.
Reducing and Managing Storage Requirements 15 Deploying desktops on virtual machines that are managed by vCenter Server provides all the storage efficiencies that were previously available only for virtualized servers. Using View Composer increases the storage savings because all virtual machines in a pool share a virtual disk with a base image.
Setting Up Desktop and Application Pools in View n Tiered storage, which allows you to distribute virtual disks in the View environment across highperformance storage and lower-cost storage tiers, to maximize performance and cost savings n Local storage on the ESXi host for the virtual machine swap files in the guest operating system Compatible vSphere 5.0 and 5.1 or Later Features With vSphere 5.
Chapter 15 Reducing and Managing Storage Requirements Each virtual machine maintains its policy regardless of its physical location in the cluster. If the policy becomes noncompliant because of a host, disk, or network failure, or workload changes, Virtual SAN reconfigures the data of the affected virtual machines and load-balances to meet the policies of each virtual machine.
Setting Up Desktop and Application Pools in View n Appropriate hardware. For example, VMware recommends a 10GB NIC and at least one SSD and one HDD for each capacity-contributing node. For specifics, see the VMware Compatibility Guide. n A cluster of at least three ESXi hosts. You need enough ESXi hosts to accommodate your setup. For more information, see the vSphere Configuration Maximums document, available from https://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html.
Chapter 15 Reducing and Managing Storage Requirements You can use either the vSphere Command-Line Interface (esxcli) or the vSphere Web Client to change the default storage policy profiles. Each virtual machine maintains its policy regardless of its physical location in the cluster.
Setting Up Desktop and Application Pools in View Virtual SAN Datastores That Aggregate Local Storage Disks from a vSphere Cluster Virtual SAN virtualizes the local physical storage disks available on ESXi hosts into a single datastore shared by all hosts in a vSphere cluster. A Virtual SAN datastore consists of solid-state drive (SSD) disks and hard disk drives (HDDs), also called data disks. SSD disks are used for read caching and write buffering. Data disks are used for persistent storage.
Chapter 15 Reducing and Managing Storage Requirements Sizing Guidelines for Linked-Clone Pools When you create or edit a linked-clone desktop pool, the Select Linked Clone Datastores page displays a table that provides storage-sizing guidelines. The table can help you to decide which datastores to select for the linked-clone disks. The guidelines calculate space needed for new linked clones.
Setting Up Desktop and Application Pools in View If you select a new datastore but keep the desktop pool the same size, or reduce the number of linked clones, the sizing guidelines show as 0. The values of 0 reflect that no new clones must be created on the selected datastore. Space requirements for the existing clones are already accounted for.
Chapter 15 Reducing and Managing Storage Requirements If you edit an existing pool or store replicas on a separate datastore, View uses a different sizing formula. See “Sizing Formulas for Creating Linked Clones When You Edit a Pool or Store Replicas on a Separate Datastore,” on page 189. Table 15‑2.
Setting Up Desktop and Application Pools in View Table 15‑4.
Chapter 15 Reducing and Managing Storage Requirements Table 15‑6. Storage Overcommit Levels Option Storage Overcommit Level None Storage is not overcommitted. Conservative 4 times the size of the datastore. This is the default level. Moderate 7 times the size of the datastore. Aggressive 15 times the size of the datastore. Storage overcommit levels provide a high-level guide for determining storage capacity. To determine the best level, monitor the growth of linked clones in your environment.
Setting Up Desktop and Application Pools in View 6 Option Description Moderate 7 times the size of the datastore. Aggressive 15 times the size of the datastore. Unbounded View does not limit the number of linked-clone machines that it creates based on the physical capacity of the datastore. Select this level only if you are certain that the datastore has enough storage capacity to accommodate all of the machines and their future growth. Click OK.
Chapter 15 Reducing and Managing Storage Requirements When the linked clone is powered off, View replaces the disposable-data disk with a copy of the original disk that View Composer created with the linked-clone pool. Linked clones can increase in size as users interact with their desktops. Using disposable-data disks can save storage space by slowing the growth of linked clones. The disposable-data disk is stored on the same datastore as the OS disk.
Setting Up Desktop and Application Pools in View If you intend to take advantage of the benefits of local storage, you must carefully consider the consequences of not having VMotion, HA, DRS, and other features available. If you manage local disk usage by controlling the number and disk growth of the virtual machines, if you use floating assignments and perform regular refresh and delete operations, you can successfully deploy linked clones to local datastores.
Chapter 15 Reducing and Managing Storage Requirements Availability Considerations for Storing Replicas on a Separate Datastore or Shared Datastores You can store View Composer replicas on a separate datastore or on the same datastores as linked-clone virtual machines. These configurations affect the availability of the pool in different ways. When you store replicas on the same datastores as linked clones, to enhance availability, View Composer creates a separate replica on each datastore.
Setting Up Desktop and Application Pools in View Procedure 1 2 In View Administrator, display the Advanced Storage Options page. Option Description New desktop pool Start the Add Desktop Pool wizard to begin creating an automated desktop pool. Follow the wizard configuration prompts until you reach the Advanced Storage page. Existing desktop pool Select the existing pool, click Edit, and click the Advanced Storage tab.
Chapter 15 Reducing and Managing Storage Requirements If a View Composer is refreshing, recomposing, or rebalancing linked clones, disk space reclamation does not take place on those linked clones. Disk space reclamation operates only on OS disks in linked clones. The feature does not affect View Composer persistent disks and does not operate on full-clone virtual machines. Native NFS snapshot technology (VAAI) is not supported in pools that contain virtual machines with spaceefficient disks.
Setting Up Desktop and Application Pools in View Using View Composer Array Integration with Native NFS Snapshot Technology (VAAI) If your deployment includes NAS devices that support the vStorage APIs for Array Integration (VAAI), you can enable the View Composer Array Integration (VCAI) feature on linked-clone pools. This feature uses native NFS snapshot technology to clone virtual machines.
Chapter 15 Reducing and Managing Storage Requirements Set Blackout Times for ESXi Operations on View Virtual Machines Regenerating digest files for View Storage Accelerator and reclaiming virtual machine disk space can use ESXi resources. To ensure that ESXi resources are dedicated to foreground tasks when necessary, you can prevent the ESXi hosts from performing these operations during specified periods of time on specified days.
Setting Up Desktop and Application Pools in View 200 VMware, Inc.
Configuring Policies for Desktop and Application Pools 16 You can configure policies to control the behavior of desktop and application pools, machines, and users. You use View Administrator to set policies for client sessions. You can use Active Directory group policy settings to control the behavior of View Agent, Horizon Client for Windows, and features that affect singleuser machines, RDS hosts, or the PCoIP display protocol.
Setting Up Desktop and Application Pools in View Configure Global Policy Settings You can configure global policies to control the behavior of all client sessions users. Prerequisites Familiarize yourself with the policy descriptions. See “View Policies,” on page 203. Procedure 1 In View Administrator, select Policies > Global Policies. 2 Click Edit policies in the View Policies pane. 3 Click OK to save your changes.
Chapter 16 Configuring Policies for Desktop and Application Pools View Policies You can configure View policies to affect all client sessions, or you can apply them to affect specific desktop pools or users. Table 16-1 describes each View policy setting. Table 16‑1. View Policies Policy Description Multimedia redirection (MMR) Determines whether MMR is enabled for client systems.
Setting Up Desktop and Application Pools in View Creating an OU for Remote Desktops You should create an organizational unit (OU) in Active Directory specifically for your remote desktops. To prevent group policy settings from being applied to other Windows servers or workstations in the same domain as your remote desktops, create a GPO for your View group policies and link it to the OU that contains your remote desktops.
Chapter 16 Configuring Policies for Desktop and Application Pools View ADM and ADMX Template Files The View ADM and ADMX template files provide group policy settings that let you control and optimize View components. Table 16‑2. View ADM and ADMX Template Files Template Name Template File Description View Agent Configuration vdm_agent.adm Contains policy settings related to the authentication and environmental components of View Agent. See “View Agent Configuration ADM Template Settings,” on page 206.
Setting Up Desktop and Application Pools in View View Agent Configuration ADM Template Settings The View Agent Configuration ADM template file (vdm_agent.adm) contains policy settings related to the authentication and environmental components of View Agent. This ADM file is available in a bundled .zip file named VMware-Horizon-View-Extras-Bundle-x.x.xyyyyyyy.zip, which you can download from the VMware Horizon (with View) download site at http://www.vmware.com/go/downloadview.
Chapter 16 Configuring Policies for Desktop and Application Pools Table 16‑3. View Agent Configuration Template Settings (Continued) Setting Computer Connect using DNS Name X Determines whether View Connection Server uses the DNS name instead of the IP address of the host when connecting. This setting is typically enabled in a NAT or firewall situation when Horizon Client or View Connection Server cannot use the remote desktop IP address directly. This setting is disabled by default.
Setting Up Desktop and Application Pools in View Table 16‑3. View Agent Configuration Template Settings (Continued) Setting Computer User Properties Force MMR to use software overlay X Determines whether the multimedia redirection (MMR) feature uses a software overlay instead of a hardware overlay. MMR uses video display hardware with overlay support for better performance.
Chapter 16 Configuring Policies for Desktop and Application Pools Table 16‑4. Client System Information (Continued) Supported Client Systems Registry Key Description Supported Desktops ViewClient_Machine_Dom ain The domain of the client system. VDI (single-user machine) RDS Windows, Metro ViewClient_LoggedOn_Us ername The user name that was used to log in to the client system.
Setting Up Desktop and Application Pools in View Table 16‑4. Client System Information (Continued) Supported Client Systems Registry Key Description Supported Desktops ViewClient_Broker_User Name Username used to authenticate to View Connection Server. VDI (single-user machine) RDS Value is sent directly from View Connection Server, not gathered by Horizon Client. ViewClient_Client_ID Specifies the Unique Client HardwareId used as a link to the license key.
Chapter 16 Configuring Policies for Desktop and Application Pools Running Commands on View Desktops You can use the View Agent CommandsToRunOnConnect, CommandsToRunOnReconnect, and CommandsToRunOnDisconnect group policy settings to run commands and command scripts on View desktops when users connect, reconnect, and disconnect. To run a command or a command script, add the command name or the file path of the script to the group policy setting's list of commands. For example: date C:\Scripts\myscript.
Setting Up Desktop and Application Pools in View View PCoIP General Session Variables The View PCoIP Session Variables ADM template file contains group policy settings that configure general session characteristics such as PCoIP image quality, USB devices, and network ports. Table 16‑5. View PCoIP General Session Variables 212 Setting Description Configure clipboard redirection Determines the direction in which clipboard redirection is allowed.
Chapter 16 Configuring Policies for Desktop and Application Pools Table 16‑5. View PCoIP General Session Variables (Continued) Setting Description Configure PCoIP event log verbosity Sets the PCoIP event log verbosity. The values range from 0 (least verbose) to 3 (most verbose). When this setting is enabled, you can set the verbosity level from 0 to 3. When the setting is not configured or disabled, the default event log verbosity level is 2.
Setting Up Desktop and Application Pools in View Table 16‑5. View PCoIP General Session Variables (Continued) 214 Setting Description Configure PCoIP session encryption algorithms Controls the encryption algorithms advertised by the PCoIP endpoint during session negotiation. Checking one of the check boxes disables the associated encryption algorithm. You must enable at least one algorithm. This setting applies to both agent and client.
Chapter 16 Configuring Policies for Desktop and Application Pools Table 16‑5. View PCoIP General Session Variables (Continued) Setting Description Configure PCoIP USB allowed and unallowed device rules Specifies the USB devices that are authorized and not authorized for PCoIP sessions that use a zero client that runs Teradici firmware. USB devices that are used in PCoIP sessions must appear in the USB authorization table.
Setting Up Desktop and Application Pools in View Table 16‑5. View PCoIP General Session Variables (Continued) Setting Description Configure PCoIP virtual channels Specifies the virtual channels that can and cannot operate over PCoIP sessions. This setting also determines whether to disable clipboard processing on the PCoIP host. Virtual channels that are used in PCoIP sessions must appear on the virtual channel authorization list.
Chapter 16 Configuring Policies for Desktop and Application Pools Table 16‑5. View PCoIP General Session Variables (Continued) Setting Description Configure the TCP port to which the PCoIP host binds and listens Specifies the TCP agent port bound to by software PCoIP hosts. The TCP port value specifies the base TCP port that the agent attempts to bind to. The TCP port range value determines how many additional ports to try if the base port is not available. The port range must be between 1 and 10.
Setting Up Desktop and Application Pools in View Table 16‑5. View PCoIP General Session Variables (Continued) 218 Setting Description Enable access to a PCoIP session from a vSphere console Determines whether to allow a vSphere Client console to display an active PCoIP session and send input to the desktop. By default, when a client is attached through PCoIP, the vSphere Client console screen is blank and the console cannot send input.
Chapter 16 Configuring Policies for Desktop and Application Pools View PCoIP Session Bandwidth Variables The View PCoIP Session Variables ADM template file contains group policy settings that configure PCoIP session bandwidth characteristics. Table 16‑6. View PCoIP Session Bandwidth Variables Setting Description Configure the maximum PCoIP session bandwidth Specifies the maximum bandwidth, in kilobits per second, in a PCoIP session.
Setting Up Desktop and Application Pools in View Table 16‑6. View PCoIP Session Bandwidth Variables (Continued) 220 Setting Description Configure the PCoIP session MTU Specifies the Maximum Transmission Unit (MTU) size for UDP packets for a PCoIP session. The MTU size includes IP and UDP packet headers. TCP uses the standard MTU discovery mechanism to set MTU and is not affected by this setting. The maximum MTU size is 1500 bytes. The minimum MTU size is 500 bytes. The default value is 1300 bytes.
Chapter 16 Configuring Policies for Desktop and Application Pools View PCoIP Session Variables for the Keyboard The View PCoIP Session Variables ADM template file contains group policy settings that configure PCoIP session characteristics that affect the use of the keyboard. Table 16‑7.
Setting Up Desktop and Application Pools in View You can turn on the build-to-lossless feature by disabling the Turn off Build-to-Lossless feature group policy setting. See “View PCoIP Session Bandwidth Variables,” on page 219. Using Remote Desktop Services Group Policies You can use Remote Desktop Services (RDS) group policies to control the configuration and performance of RDS hosts and RDS desktop and application sessions.
Chapter 16 Configuring Policies for Desktop and Application Pools RDS Application Compatibility Settings The RDS Application Compatibility group policy settings control Windows installer compatibility, remote desktop IP virtualization, network adapter selection, and the use of the RDS host IP address. Table 16‑8.
Setting Up Desktop and Application Pools in View RDS Connections Settings The RDS Connections group policy setting lets you disable Fair Share CPU Scheduling. Table 16‑9. RDS Connections Group Policy Settings Setting Description Turn off Fair Share CPU Scheduling Fair Share CPU Scheduling dynamically distributes processor time across all Remote Desktop Services sessions on the same RD Session Host server, based on the number of sessions and the demand for processor time within each session.
Chapter 16 Configuring Policies for Desktop and Application Pools RDS Licensing Settings The RDS Licensing group policy settings control the order in which RDS license servers are located, whether problem notifications are displayed, and whether Per User or Per Device licensing is used for RDS Client Access Licenses (CALs). Table 16‑11.
Setting Up Desktop and Application Pools in View Table 16‑11. RDS Licensing Group Policy Settings (Continued) Setting Description If you disable or do not configure this policy setting, the licensing mode that is specified during the installation of Remote Desktop Session Host role service or specified in the Remote Desktop Session Host Configuration tool is used. 226 VMware, Inc.
Chapter 16 Configuring Policies for Desktop and Application Pools RDS Profiles Settings The RDS Profiles group policy settings control roaming profile and home directory settings for Remote Desktop Services sessions. Table 16‑12. RDS Profiles Group Policy Settings Setting Description Limit the size of the entire roaming user profile cache This policy setting allows you to limit the size of the entire roaming user profile cache on the local drive.
Setting Up Desktop and Application Pools in View Table 16‑12. RDS Profiles Group Policy Settings (Continued) Setting Description Use mandatory profiles on the RD Session Host server This policy setting allows you to specify whether Remote Desktop Services uses a mandatory profile for all users connecting remotely to the RD Session Host server.
Chapter 16 Configuring Policies for Desktop and Application Pools RDS Remote Session Environment Settings he RDS Remote Session Environment group policy settings control configuration of the user interface in Remote Desktop Services sessions. Table 16‑13. RDS Remote Session Environment Group Policy Settings Setting Description Remove Windows Security item from Start menu Specifies whether to remove the Windows Security item from the Settings menu on Remote Desktop clients.
Setting Up Desktop and Application Pools in View RDS Temporary Folders Settings The RDS Connections group policy settings control the creation and deletion of temporary folders for Remote Desktop Services sessions. Table 16‑15. RDS Temporary Folders Group Policy Settings Setting Description Do not delete temp folder upon exit Specifies whether Remote Desktop Services retains a user's per-session temporary folders at logoff.
Chapter 16 Configuring Policies for Desktop and Application Pools In Horizon 6.0.1 and later, location-based printing is supported on the following remote desktops and applications: n Desktops that are deployed on single-user machines, including Windows Desktop and Windows Server 2008 R2 machines n Desktops that are deployed on RDS hosts, where the RDS hosts are virtual machines n Hosted Apps n Hosted Apps that are launched from Horizon Client inside remote desktops In Horizon 6.
Setting Up Desktop and Application Pools in View Register the Location-Based Printing Group Policy DLL File Before you can configure the group policy setting for location-based printing, you must register the DLL file TPVMGPoACmap.dll. In Horizon 6.0.1 or later, 32-bit and 64-bit versions of TPVMGPoACmap.dll are available in a bundled .zip file named VMware-Horizon-View-Extras-Bundle-x.x.x-yyyyyyy.zip, where x.x.x is the version and yyyyyyy is the build number.
Chapter 16 Configuring Policies for Desktop and Application Pools Procedure 1 On the Active Directory server, edit the GPO. AD Version Navigation Path Windows 2003 a b c d Windows 2008 a b Select Start > All Programs > Administrative Tools > Active Directory Users and Computers. Right-click the OU that contains your View desktops and select Properties. On the Group Policy tab, click Open to open the Group Policy Management plug-in.
Setting Up Desktop and Application Pools in View Table 16‑16. Translation Table Columns and Values Column Description IP Range A translation rule that specifies a range of IP addresses for client systems. To specify IP addresses in a specific range, use the following notation: ip_address-ip_address For example: 10.112.116.0-10.112.119.255 To specify all of the IP addresses in a specific subnet, use the following notation: ip_address/subnet_mask_bits For example: 10.112.4.
Chapter 16 Configuring Policies for Desktop and Application Pools Table 16‑17. Location-Based Printing Group Policy Setting Example IP Range Client Name Mac Address User/ Group Printer Name Printer Driver * * * * PRINTER-1-CLR HP Color LaserJet 4700 PS IP_10.114.24.1 10.112.116.140-10.1 12.116.145 * * * PRINTER-2-CLR HP Color LaserJet 4700 PS IP_10.114.24.
Setting Up Desktop and Application Pools in View What to do next Create GPOs for View group policies. Create GPOs for View Group Policies Create GPOs to contain group policies for View components and location-based printing and link them to the OU for your View machines. Prerequisites n Create an OU for your View machines. n Verify that the Group Policy Management feature is available on your Active Directory server.
Chapter 16 Configuring Policies for Desktop and Application Pools The steps for opening the Group Policy Management Console differ in the Windows 2012, Windows 2008, and Windows 2003 Active Directory versions. See “Create GPOs for View Group Policies,” on page 236. Procedure 1 Download the View GPO Bundle .zip file from the VMware Horizon (with View) download site at http://www.vmware.com/go/downloadview. The file is named VMware-Horizon-View-Extras-Bundle-x.x.x-yyyyyyy.zip, where x.x.
Setting Up Desktop and Application Pools in View 6 7 238 Select Enabled and then select a loopback processing mode from the Mode drop-down menu. Option Action Merge The user policy settings applied are the combination of those included in both the computer and user GPOs. Where conflicts exist, the computer GPOs take precedence. Replace The user policy is defined entirely from the GPOs associated with the computer. Any GPOs associated with the user are ignored. Click OK to save your changes.
Configuring User Profiles with View Persona Management 17 With View Persona Management, you can configure user profiles that are dynamically synchronized with a remote profile repository. This feature gives users access to a personalized desktop experience whenever they log in to a desktop. View Persona Management expands the functionality and improves the performance of Windows roaming profiles, but does not require Windows roaming profiles to operate.
Setting Up Desktop and Application Pools in View A user profile comprises a variety of user-generated information: n User-specific data and desktop settings n Application data and settings n Windows registry entries configured by user applications Also, if you provision desktops with ThinApp applications, the ThinApp sandbox data can be stored in the user profile and roamed with the user. View Persona Management minimizes the time it takes to log in to and log off of desktops.
Chapter 17 Configuring User Profiles with View Persona Management Users of standalone laptops can disconnect from the network. When a user reconnects, View Persona Management uploads the latest changes in the user's local profile to the remote profile repository. NOTE Before a user can go offline, the user profile must be completely downloaded to the local system.
Setting Up Desktop and Application Pools in View Table 17‑1. User Profile Migration Scenarios If This Is Your Original Deployment... And This Is Your Destination Deployment... Windows XP physical computers Windows 7 View desktops or Windows 8 View desktops Perform These Tasks: 1 2 3 Windows XP physical computers or virtual machines that use a roaming user profile solution.
Chapter 17 Configuring User Profiles with View Persona Management Table 17‑1. User Profile Migration Scenarios (Continued) If This Is Your Original Deployment... And This Is Your Destination Deployment... Perform These Tasks: Windows XP physical computers or virtual machines. The legacy systems cannot have View Agent 5.x installed. Windows XP View desktops 1 2 3 4 Windows 7 or Windows 8 physical computers or virtual machines. The legacy systems cannot have View Agent 5.x installed.
Setting Up Desktop and Application Pools in View Configuring a View Persona Management Deployment To configure View Persona Management, you set up a remote repository that stores user profiles, install View Agent with the View Persona Management setup option on virtual machines that deliver remote desktop sessions, add and configure View Persona Management group policy settings, and deploy desktop pools. You can also configure View Persona Management for a non-View deployment.
Chapter 17 Configuring User Profiles with View Persona Management Prerequisites n Familiarize yourself with the minimum access permissions that are required to configure a shared folder. See “Setting Access Permissions on Shared Folders for View Persona Management,” on page 245. n Familiarize yourself with the guidelines for creating a user profile repository.
Setting Up Desktop and Application Pools in View Table 17‑3. Share Level (SMB) Permissions Required for User Profile Repository and Redirected Folder Share User Account Default Permissions Minimum Permissions Required Everyone Read only No permissions Security group of users needing to put data on share N/A Full Control For information about roaming user profiles security, see the Microsoft TechNet topic, Security Recommendations for Roaming User Profiles Shared Folders. http://technet.microsoft.
Chapter 17 Configuring User Profiles with View Persona Management For a manual pool, you must install View Agent with the View Persona Management setup option on each virtual machine that is used as a desktop in the pool. Use Active Directory to configure View Persona Management group policies for a manual pool. The alternative is to add the ADM Template file and configure group policies on each individual machine.
Setting Up Desktop and Application Pools in View You can download the UPHClean service at the following location: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=6676. The UPHClean service is included with Windows 7 and Windows Vista operating systems. You do not have to install the service on these operating systems.
Chapter 17 Configuring User Profiles with View Persona Management What to do next Add the View Persona Management ADM Template file to your Active Directory or local group policy configuration. Add the View Persona Management ADM Template File The View Persona Management Administrative (ADM) Template file contains group policy settings that allow you to configure View Persona Management.
Setting Up Desktop and Application Pools in View 5 In the Local Computer Policy window, navigate to Computer Configuration and right-click Administrative Templates. NOTE Do not select Administrative Templates under User Configuration. 6 Click Add/Remove Templates and click Add. 7 Browse to the directory that contains the ViewPM.adm file. 8 Select the ViewPM.adm file and click Add. 9 Close the Add/Remove Templates window.
Chapter 17 Configuring User Profiles with View Persona Management 8 Click Close to apply the policy settings in the ADM Template file to the GPO. The name of the template appears in the left pane under Administrative Templates. What to do next Configure the View Persona Management group policy settings on your Active Directory server.
Setting Up Desktop and Application Pools in View 5 Type the profile upload interval, in minutes, and click OK. The profile upload interval determines how often View Persona Management copies user profile changes to the remote repository. The default upload interval is 10 minutes. 6 Double-click Persona repository location and click Enabled. If you have an existing Windows roaming profiles deployment, you can use an Active Directory user profile path for the remote profile repository.
Chapter 17 Configuring User Profiles with View Persona Management NOTE After you deploy View Persona Management on your View desktop pools, if you remove the View Persona Management setup option on the View machines, or uninstall View Agent altogether, the local user profiles are removed from the machines of users who are not currently logged in. For users who are currently logged in, the user profiles are downloaded from the remote profile repository during the uninstall process.
Setting Up Desktop and Application Pools in View If %username% is the last subfolder in the path, the user's name appears as the folder name. For example, instead of seeing a My Videos folder on the desktop, the user JDoe sees a folder named JDoe and cannot easily identify the folder. Using the Windows Event Log to Monitor the View Persona Management Deployment To help you manage your deployment, View Persona Management provides improved log messages and profile size and file and folder count tracking.
Chapter 17 Configuring User Profiles with View Persona Management As a best practice, disable the Windows Offline Files feature before you begin using View Persona Management. If you encounter issues with View Persona Management because Windows Client-Side Caching is in effect on your desktops, you can resolve these issues by synchronizing the profile data that currently resides in the local Client-Side Caching database and disabling the Windows Offline Files feature.
Setting Up Desktop and Application Pools in View As a best practice, notify your users to make sure that their user profiles are completely downloaded before they disconnect from the network. Tell users to wait for the Background download complete notice to appear on their laptop screens before they disconnect. To allow the Background download complete notice to be displayed on user laptops, configure the View Persona Management group policy setting, Show critical errors to users via tray icon alerts.
Chapter 17 Configuring User Profiles with View Persona Management The group policy settings are contained in these folders: n Roaming & Synchronization n Folder Redirection n Desktop UI n Logging Roaming and Synchronization Group Policy Settings The roaming and synchronization group policy settings turn View Persona Management on and off, set the location of the remote profile repository, determine which folders and files belong to the user profile, and control how to synchronize folders and files.
Setting Up Desktop and Application Pools in View Group Policy Setting Description Roam local settings folders Roams the local settings folders with the rest of each user profile. Files and folders to preload Specifies a list of files and folders that are downloaded to the local user profile when the user logs in. Changes in the files are copied to the remote repository as they occur. In some situations, you might want to preload specific files and folders into the locally stored user profile.
Chapter 17 Configuring User Profiles with View Persona Management Group Policy Setting Description Folders to background download The selected folders are downloaded in the background after a user logs in to the desktop. In certain cases, you can optimize View Persona Management by downloading the contents of specific folders in the background. With this setting, users do not have to wait for large files to download when they start an application.
Setting Up Desktop and Application Pools in View n If a folder redirection setting is disabled or not configured, the folder is stored on the local View desktop and managed according to the View Persona Management group policy settings. n If View Persona Management and Windows roaming profiles are configured to redirect the same folder, View Persona Management's folder redirection takes precedence over Windows roaming profiles.
Chapter 17 Configuring User Profiles with View Persona Management n Printer Neighborhood n Recent Items n Save Games n Searches n Start Menu n Startup Items n Templates n Temporary Internet Files Certain folders are available only in Windows Vista and later operating systems. Table 17‑5.
Setting Up Desktop and Application Pools in View 3 For each user folder, revert ownership from the administrator to the corresponding user. icacls "\\file-server\persona-share\*" /setowner "domain\folder-owner" /T /C /L /Q For example: icacls "\\myserver-123abc\folders\*" /setowner "mycompanydomain\user1" /T /C /L /Q Desktop UI Group Policy Settings The desktop UI group policy settings control View Persona Management settings that users see on their desktops.
Chapter 17 Configuring User Profiles with View Persona Management Group Policy Setting Description Debug flags Determines the types of debug messages to log. View Persona Management handles debug messages in the same way that it handles log messages. When this setting is enabled, you can select any or all debug message types to generate: n Debug error messages n Debug information messages n Debug port messages By default, no debug messages are generated.
Setting Up Desktop and Application Pools in View 264 VMware, Inc.
Troubleshooting Machines and Desktop Pools 18 You can use a variety of procedures to diagnose and fix problems that you encounter when you create and use machines and desktop pools. Users might experience difficulty when they use Horizon Client to access desktops and applications. You can use troubleshooting procedures to investigate the causes of such problems and attempt to correct them yourself, or you can obtain assistance from VMware Technical Support.
Setting Up Desktop and Application Pools in View What to do next The action that you should take depends on the problem that View Administrator reports for a machine. n If a linked-clone machine is in an error state, the View automatic recovery mechanism attempts to power on, or shut down and restart, the linked clone. If repeated recovery attempts fail, the linked clone is deleted. In certain situations, a linked clone might be repeatedly deleted and recreated.
Chapter 18 Troubleshooting Machines and Desktop Pools Cause The most likely cause of this problem is that you have insufficient permissions to access the customization specifications, or to create a pool. Another possible cause is that the customization specification has been renamed or deleted. Solution n Verify that you have sufficient permissions to access the customization specifications, and to create a pool.
Setting Up Desktop and Application Pools in View Solution n Verify that the template is accessible. n Verify that the correct name and folder are specified for the template. n If a virtual machine image has been moved between ESX/ESXi hosts, move the virtual machine to the correct vCenter folder. n If a virtual machine image has been deleted, delete the entry for the virtual machine in View Administrator and recreate or restore the image.
Chapter 18 Troubleshooting Machines and Desktop Pools Solution n Verify that you have sufficient permissions to access the selected datastore. n Verify whether the disk on which the datastore is configured is full. n If the disk is full or the space is reserved, free up space on the disk, rebalance the available datastores, or migrate the datastore to a larger disk.
Setting Up Desktop and Application Pools in View Removing Orphaned or Deleted Linked Clones Under certain conditions, linked-clone data in View, View Composer, and vCenter Server might get out of synchronization, and you might be unable to provision or delete linked-clone machines. Problem n You cannot provision a linked-clone desktop pool.
Chapter 18 Troubleshooting Machines and Desktop Pools 2 From a Windows command prompt on the View Composer computer, run the SviConfig RemoveSviClone command in the following form: sviconfig -operation=removesviclone -VmName=virtual machine name [-AdminUser=local administrator username] -AdminPassword=local administrator password [-ServerUrl=View Composer server URL] For example: sviconfig -operation=removesviclone -vmname=MyLinkedClone -adminuser=Admin -adminpassword=Pass -serverurl=ViewComposerURL T
Setting Up Desktop and Application Pools in View Troubleshooting QuickPrep Customization Problems A View Composer QuickPrep customization script can fail for a variety of reasons. Problem A QuickPrep post-synchronization or power-off script does not execute. In some cases, a script might complete successfully on some linked clones, but fail on others.
Chapter 18 Troubleshooting Machines and Desktop Pools Finding and Unprotecting Unused View Composer Replicas Under certain conditions, View Composer replicas might remain in vCenter Server when they no longer have any linked clones associated with them. Problem An unused replica remains in a vCenter Server folder. You are unable to remove the replica by using vSphere Client.
Setting Up Desktop and Application Pools in View 2 From a Windows command prompt on the View Composer computer, run the SviConfig FindUnusedReplica command in the following form: sviconfig -operation=findunusedreplica -DsnName=name of the DSN -Username=Database administrator username -Password=Database administrator password [-ReplicaFolder=Replica folder name] [-UnusedReplicaFolder=Unused replica folder name.
Chapter 18 Troubleshooting Machines and Desktop Pools View Composer Provisioning Errors If an error occurs when View Composer provisions or recomposes linked-clone machines, an error code indicates the cause of the failure. The error code appears in the machine-status column in View Administrator. Table 18-1 describes the View Composer provisioning error codes. This table lists errors that are associated with View Composer and QuickPrep customization.
Setting Up Desktop and Application Pools in View Table 18‑1. View Composer Provisioning Errors (Continued) Error Description 17 The View Composer agent did not start. The agent timed out while waiting for Sysprep to start. 18 The View Composer agent failed to join the linked-clone virtual machine to a domain during customization. 19 The View Composer agent failed to execute a post-synchronization script. 20 The View Composer agent failed to handle a machine password synchronization event.
Chapter 18 Troubleshooting Machines and Desktop Pools n At a command prompt on the machine, verify that TCP port 4001, which View Agent uses to establish JMS communication with the View Connection Server host, is working by typing the telnet command. telnet CS_FQDN 4001 If the telnet connection is established, network connectivity for JMS is working.
Setting Up Desktop and Application Pools in View Solution n n Check that the following network ports are opened on the firewall for the security server or View Connection Server host. Port Description TCP 4172 From Horizon Client to the security server or View Connection Server host. UDP 4172 Between Horizon Client and the security server or View Connection Server host, in both directions. TCP 4172 From the security server or View Connection Server host to the View desktop.
Chapter 18 Troubleshooting Machines and Desktop Pools Connection Problems Between Machines and View Connection Server Instances You might experience connection problems between machines and View Connection Server instances. Problem If connectivity between a machine and a View Connection Server instance fails, you see one of the following messages in the event database.
Setting Up Desktop and Application Pools in View Connection Problems Due to Incorrect Assignment of IP Addresses to Cloned Machines You might not be able to connect to cloned machines if they have static IP addresses. Problem You cannot use Horizon Client to connect to cloned machines. Cause Cloned machines are incorrectly configured to use a static IP address instead of using DHCP to obtain their IP addresses.
Chapter 18 Troubleshooting Machines and Desktop Pools n Some audio devices might require changes to policy settings or to registry settings. See http://kb.vmware.com/kb/1023868. n Network latency can cause slow device interaction or cause applications to appear frozen because they are designed to interact with local devices. Very large USB disk drives might take several minutes to appear in Windows Explorer. n USB flash cards formatted with the FAT32 file system are slow to load. See http://kb.vmware.
Setting Up Desktop and Application Pools in View To ensure that the GINA is chained properly, you must configure the WinLogon GINA to be the View GINA and make sure that the vdmGinaChainDLL is created and contains the third-party GINAs. If you did not install any software that chains to a different GINA, the default is msgina.dll, which is located at %systemroot%\system32\msgina.dll on the virtual machine. Solution 1 Log in to the parent virtual machine, template virtual machine, or View machine.
Chapter 18 Troubleshooting Machines and Desktop Pools Further Troubleshooting Information You can find further troubleshooting information in VMware Knowledge Base articles. The VMware Knowledge Base (KB) is continually updated with new troubleshooting information for VMware products. For more information about troubleshooting View, see the KB articles that are available on the VMware KB Web site: http://kb.vmware.com/selfservice/microsites/microsite.do VMware, Inc.
Setting Up Desktop and Application Pools in View 284 VMware, Inc.
Index Numerics 3D renderer best practices 122 configuring 120 options 121 A access permissions, shared folders for Persona Management 245 Active Directory troubleshooting linked clones failing to join the domain 274 using existing computer accounts for linked clones 75 ADM Template file adding to a local system 249 adding to Active Directory 250 installing 249 ADM template file Real-Time Audio-Video 151 scanner redirection 156 ADM template files PCoIP Session Variables 211 PCoIP session bandwidth settings
Setting Up Desktop and Application Pools in View connections, troubleshooting 276 custom setup options installing View Agent on an RDS host 88 View Agent 17, 27 customization specifications creating 52 recomposing linked-clone machines 74 customization scripts increasing QuickPrep timeout limits 50 using QuickPrep for linked-clone machines 72, 73 customizing machines, maintenance mode 109 D datastores local storage 193 sizing linked-clone pools 186 storage sizing table 187 storing linked clones and replic
Index G GINA chaining 3rd-party software dlls 281 View Agent dll 281 global policies, configuring 202 GPOs creating for desktops 236 creating for View component policies 203 gpuvm utility, examining GPU resources 123 graphics, 3D renderer 120 group policies ADM template files 205 applying to GPOs 236 examples 235 Remote Desktop Services 222 View Agent configuration 206 View components 204 group policies for desktop pools 201 group policy settings adding RDS ADMX files 222 adding to a local system 249 addin
Setting Up Desktop and Application Pools in View Linux Thin clients, setting up for Flash URL Redirection 139 local datastore, linked-clone swap files 45, 49 location-based printing configuring 230 group policy 230, 232, 233 registry key 230 TPVMGPoACmap.
Index keyboard settings 221 session bandwidth settings 219 PCoIP Smartcard, View Agent custom option 17, 27 pcoip.
Setting Up Desktop and Application Pools in View Real-Time Audio-Video, configuration choices 141 rebalance feature 185 rebalancing linked-clone machines, setting minimum ready machines 75 recomposing machines, setting minimum ready machines 75 recomposing linked-clone machines, Sysprep 74 refresh, setting minimum ready machines 75 registry backup (RegIdleBackup), disabling 43 regulatory compliance 14 remote repository, configuring 244 Remote Desktop connections disabling RDP 124 enabling 23 Remote Desktop
Index Unity Touch configuring 133 system requirements 134 Unity Touch feature 134 unmanaged machines defined 15 installing View Agent 15 preparing for desktop delivery 15 Update Service, disabling 42 UPHClean service, using with Persona Management 247 USB device families 174 USB device filtersUSB device filters 171 USB devices support for 164 using with View desktops 163, 165 USB redirection automatic connections 166 configuring in View Agent 17, 27 controlling using policies 168, 175 disabling 167 ports f
Setting Up Desktop and Application Pools in View vSphere 181 W Web pages, providing multicast streams 139 webcam 143, 146, 148 webcams, selecting preferred 143 Windows 7 3D rendering 120 benefits of disabling services 38 customization specifications 52 disabling hibernation 48 disabling customer experience improvement program 37 disabling defragmentation for linked clones 41 disabling Microsoft Feeds Synchronization 44 disabling prefetch and superfetch 43 disabling registry backup 43 disabling System Rest
