Setting Up Desktop and Application Pools in View
Table Of Contents
- Setting Up Desktop and Application Pools in View
- Contents
- Setting Up Desktop and Application Pools in View
- Introduction to Desktop and Application Pools
- Preparing Unmanaged Machines
- Creating and Preparing Virtual Machines
- Creating Virtual Machines for Remote Desktop Deployment
- Create a Virtual Machine for Remote Desktop Deployment
- Install a Guest Operating System
- Prepare a Guest Operating System for Remote Desktop Deployment
- Prepare Windows Server Operating Systems for Desktop Use
- Install Desktop Experience on Windows Server 2008 R2
- Install Desktop Experience on Windows Server 2012 or 2012 R2
- Configure the Windows Firewall Service to Restart After Failures
- Install View Agent on a Virtual Machine
- Install View Agent Silently
- Configure a Virtual Machine with Multiple NICs for View Agent
- Optimize Guest Operating System Performance for All Windows Versions
- Optimize Windows 7 and Windows 8 Guest Operating System Performance
- Optimizing Windows 7 and Windows 8 for Linked-Clone Virtual Machines
- Benefits of Disabling Windows 7 and Windows 8 Services and Tasks
- Overview of Windows 7 and Windows 8 Services and Tasks That Cause Linked-Clone Growth
- Disable Scheduled Disk Defragmentation on Windows 7 and Windows 8 Parent Virtual Machines
- Disable the Windows Update Service on Windows 7 and Windows 8 Virtual Machines
- Disable the Diagnostic Policy Service on Windows 7 and Windows 8 Virtual Machines
- Disable the Prefetch and Superfetch Features on Windows 7 and Windows 8 Virtual Machines
- Disable Windows Registry Backup on Windows 7 and Windows 8 Virtual Machines
- Disable the System Restore on Windows 7 and Windows 8 Virtual Machines
- Disable Windows Defender on Windows 7 and Windows 8 Virtual Machines
- Disable Microsoft Feeds Synchronization on Windows 7 and Windows 8 Virtual Machines
- Preparing Virtual Machines for View Composer
- Prepare a Parent Virtual Machine
- Activating Windows on Linked-Clone Virtual Machines
- Disable Windows Hibernation in the Parent Virtual Machine
- Configure a Parent Virtual Machine to Use Local Storage
- Keep a Record of the Parent Virtual Machine's Paging-File Size
- Increase the Timeout Limit of QuickPrep Customization Scripts
- Creating Virtual Machine Templates
- Creating Customization Specifications
- Creating Virtual Machines for Remote Desktop Deployment
- Creating Automated Desktop Pools That Contain Full Virtual Machines
- Creating Linked-Clone Desktop Pools
- Linked-Clone Desktop Pools
- Worksheet for Creating a Linked-Clone Desktop Pool
- Create a Linked-Clone Desktop Pool
- Desktop Pool Settings for Linked-Clone Desktop Pools
- View Composer Support for Linked-Clone SIDs and Third-Party Applications
- Keeping Linked-Clone Machines Provisioned and Ready During View Composer Operations
- Use Existing Active Directory Computer Accounts for Linked Clones
- Creating Manual Desktop Pools
- Setting Up Remote Desktop Services Hosts
- Remote Desktop Services Hosts
- Install Remote Desktop Services on Windows Server 2008 R2
- Install Remote Desktop Services on Windows Server 2012 or 2012 R2
- Install Desktop Experience on Windows Server 2008 R2
- Install Desktop Experience on Windows Server 2012 or 2012 R2
- Restrict Users to a Single Session
- Install View Agent on a Remote Desktop Services Host
- Enable Time Zone Redirection for RDS Desktop and Application Sessions
- Enable Windows Basic Theme for Applications
- Configure Group Policy to Start Runonce.exe
- RDS Host Performance Options
- Creating Farms
- Creating Application Pools
- Creating RDS Desktop Pools
- Provisioning Desktop Pools
- User Assignment in Desktop Pools
- Naming Machines Manually or Providing a Naming Pattern
- Manually Customizing Machines
- Desktop Pool Settings for All Desktop Pool Types
- Adobe Flash Quality and Throttling
- Setting Power Policies for Desktop Pools
- Power Policies for Desktop Pools
- Configure Dedicated Machines To Be Suspended After Users Disconnect
- How Power Policies Affect Automated Desktop Pools
- Power Policy Examples for Automated Pools with Floating Assignments
- Power Policy Example for Automated Pools with Dedicated Assignments
- Preventing View Power Policy Conflicts
- Configuring 3D Rendering for Desktops
- Prevent Access to View Desktops Through RDP
- Deploying Large Desktop Pools
- Entitling Users and Groups
- Configuring Remote Desktop Features
- Configuring Unity Touch
- Configuring Flash URL Redirection for Multicast or Unicast Streaming
- Configuring Real-Time Audio-Video
- Configuration Choices for Real-Time Audio-Video
- System Requirements for Real-Time Audio-Video
- Ensuring That Real-Time Audio-Video Is Used Instead of USB Redirection
- Selecting Preferred Webcams and Microphones
- Select a Default Microphone on a Windows Client System
- Select a Preferred Webcam on a Windows Client System
- Select a Default Microphone on a Mac OS X Client System
- Configuring Real-Time Audio-Video on a Mac OS X Client
- Configure a Preferred Webcam or Microphone on a Mac OS X Client System
- Select a Default Microphone on a Linux Client System
- Select a Preferred Webcam or Microphone on a Linux Client System
- Configuring Real-Time Audio-Video Group Policy Settings
- Real-Time Audio-Video Bandwidth
- Configuring Scanner Redirection
- Configuring Serial Port Redirection
- Managing Access to Windows Media Multimedia Redirection (MMR)
- Managing Access to Client Drive Redirection
- Using USB Devices with Remote Desktops and Applications
- Limitations Regarding USB Device Types
- Overview of Setting Up USB Redirection
- Network Traffic and USB Redirection
- Automatic Connections to USB Devices
- Deploying USB Devices in a Secure View Environment
- Using Log Files for Troubleshooting and to Determine USB Device IDs
- Using Policies to Control USB Redirection
- Troubleshooting USB Redirection Problems
- Reducing and Managing Storage Requirements
- Managing Storage with vSphere
- Reducing Storage Requirements with View Composer
- Storage Sizing for Linked-Clone Desktop Pools
- Storage Overcommit for Linked-Clone Virtual Machines
- Linked-Clone Data Disks
- Storing Linked Clones on Local Datastores
- Storing View Composer Replicas and Linked Clones on Separate Datastores
- Configure View Storage Accelerator for Desktop Pools
- Reclaim Disk Space on Linked-Clone Virtual Machines
- Using View Composer Array Integration with Native NFS Snapshot Technology (VAAI)
- Set Blackout Times for ESXi Operations on View Virtual Machines
- Configuring Policies for Desktop and Application Pools
- Setting Policies in View Administrator
- Using Active Directory Group Policies
- Using View Group Policy Administrative Template Files
- View ADM and ADMX Template Files
- View Agent Configuration ADM Template Settings
- View PCoIP Session Variables ADM Template Settings
- Using Remote Desktop Services Group Policies
- Add the Remote Desktop Services ADMX Files to Active Directory
- RDS Application Compatibility Settings
- RDS Connections Settings
- RDS Device and Resource Redirection Settings
- RDS Licensing Settings
- RDS Profiles Settings
- RDS Remote Session Environment Settings
- RDS Security Settings
- RDS Temporary Folders Settings
- Setting Up Location-Based Printing
- Active Directory Group Policy Example
- Configuring User Profiles with View Persona Management
- Providing User Personas in View
- Using View Persona Management with Standalone Systems
- Migrating User Profiles with View Persona Management
- Persona Management and Windows Roaming Profiles
- Configuring a View Persona Management Deployment
- Overview of Setting Up a View Persona Management Deployment
- Configure a User Profile Repository
- Install View Agent with the View Persona Management Option
- Install Standalone View Persona Management
- Add the View Persona Management ADM Template File
- Configure View Persona Management Policies
- Create Desktop Pools That Use Persona Management
- Best Practices for Configuring a View Persona Management Deployment
- View Persona Management Group Policy Settings
- Troubleshooting Machines and Desktop Pools
- Display Problem Machines
- Send Messages to Desktop Users
- Troubleshooting Desktop Pool Creation Problems
- Pool Creation Fails if Customization Specifications Cannot Be Found
- Pool Creation Fails Because of a Permissions Problem
- Pool Provisioning Fails Due to a Configuration Problem
- Pool Provisioning Fails Due to a View Connection Server Instance Being Unable to Connect to vCenter
- Pool Provisioning Fails Due to Datastore Problems
- Pool Provisioning Fails Due to vCenter Server Being Overloaded
- Virtual Machines Are Stuck in the Provisioning State
- Virtual Machines Are Stuck in the Customizing State
- Removing Orphaned or Deleted Linked Clones
- Troubleshooting Machines That Are Repeatedly Deleted and Recreated
- Troubleshooting QuickPrep Customization Problems
- Finding and Unprotecting Unused View Composer Replicas
- View Composer Provisioning Errors
- Troubleshooting Network Connection Problems
- Troubleshooting USB Redirection Problems
- Manage Machines and Policies for Unentitled Users
- Resolving Database Inconsistencies with the ViewDbChk Command
- Further Troubleshooting Information
- Index
When to Choose the Automatic Option
The Automatic option is the best choice for many View deployments that require 3D rendering. vSGA
(Virtual Shared Graphics Acceleration)-enabled virtual machines can dynamically switch between software
and hardware 3D rendering, without your having to reconfigure. This option ensures that some type of 3D
rendering takes place even when GPU resources are completely reserved. In a mixed cluster of ESXi 5.1 and
ESXi 5.0 hosts, this option ensures that a virtual machine is powered on successfully and uses 3D rendering
even if, for example, vMotion moved the virtual machine to an ESXi 5.0 host.
The only drawback with the Automatic option is that you cannot easily tell whether a virtual machine is
using hardware or software 3D rendering.
When to Choose the Hardware Option
The Hardware option guarantees that every virtual machine in the pool uses hardware 3D rendering,
provided that GPU resources are available on the ESXi hosts. This option might be the best choice when all
your users run graphically intensive applications. You can use this option when configuring vSGA (Virtual
Shared Graphics Acceleration).
With the Hardware option, you must strictly control your vSphere environment. All ESXi hosts must be
version 5.1 or later and must have GPU graphics cards installed.
When all GPU resources on an ESXi host are reserved, View cannot power on a virtual machine for the next
user who tries to log in to a desktop. You must manage the allocation of GPU resources and the use of
vMotion to ensure that resources are available for your desktops.
When to Choose the Option to Manage Using vSphere Client
When you select the Manage using vSphere Client option, you can use vSphere Web Client to configure
individual virtual machines with different options and VRAM values.
n
For vSGA (Virtual Shared Graphics Acceleration), you can support a mixed configuration of 3D
rendering and VRAM sizes for virtual machines in a pool.
n
For vDGA (Virtual Dedicated Graphics Acceleration), each virtual machine must be individually
configured to share a specific PCI device with the ESXi host and all memory must be reserved.
All ESXi hosts must be version 5.5 or later and must have GPU graphics cards installed.
You might also choose this option if you want to explicitly manage graphics settings of clones and linked
clones by having the clones inherit settings from the parent virtual machine.
When to Choose the NVIDIA GRID vGPU Option
With the NVIDIA GRID vGPU option, you can achieve a higher consolidation ratio of virtual machines on
an NVIDIA GRID vGPU-enabled ESXi host than is possible by using vSGA or vDGA, while maintaining the
same performance level. As with vDGA (Dedicated Virtual Graphics), the ESXi and virtual machine also use
GPU pass-through for NVIDIA GRID vGPU.
NOTE To improve virtual machine consolidation ratios, you can set the ESXi host to use consolidation
mode. Edit the /etc/vmware/config file on the ESXi host and add the following entry:
vGPU.consolidation = "true"
By default, the ESXi host assigns virtual machines to the physical GPU with the fewest virtual machines
already assigned. This is called performance mode. If you would rather have the ESXi host assign virtual
machines to the same physical GPU until the maximum number of virtual machines is reached before
placing virtual machines on the next physical GPU, you can use consolidation mode.
Chapter 11 Provisioning Desktop Pools
VMware, Inc. 131