VMwar View Instructor Slides

VMware View 5
Essentials Training
VMware View 5 Essentials Training
Instructor: Brian Knudtson
Getting Started with
VMware View 5
Essentials Training
Getting Started with VMware View Administration Training
www.knudt.net/vblog and twitter.com/bknudtson
Certifications
VMware: VCP, VCAP-DCA, VCAP-DCD, VTSP, VCA-DT, VCP-DT
Microsoft: MCITP 2008-Enterprise Administration
HP: Master ASE-High Availability and Clustering Solutions
Qualifications
Started working with VMware technologies in 2004 (ESX 2.5)
Started first virtual desktop project as a customer before VDI
was a buzz word
First project with a partner was implementing VMware VDM
Additional accomplishments
VMware vExpert
VMware Partner Technical Advisory Board
About Brian Knudtson
14 Years of experience in IT with the last 6 years
focused on Server Virtualization
Certifications
VMware: VCDX3/4 #53, VCP3/4, VCA-DT, VCP-DT, VCAP-DCD
Microsoft: MCSE NT4-2003
Cisco: CCNA, UCS Support/Design
Currently working at ENS Inc. in Sacramento, CA as a Director
of Cloud and Commercial Services
Have been on both the customer side and consulting side of IT
so I know what its like to be in both places
Have a passion for continuous improvement and education both
personally and professionally
About Lane Leverett
Provide you the knowledge to successfully implement a VMware
View 5 infrastructure
Provide some basic guidance for managing a VMware View 5
infrastructure
Similar approach to a VMware View 5 implementation project
Prepare you for some of the topics covered on the VMware
Certified Associate Desktop (VCA-DT) certification
Put all topics into the context of a real-world scenario
Provide links to additional resources to enhance the knowledge
you gain from this series and your real-world experience
Series Purpose
Major shift in the way desktops are managed
Supports a flexible, self-serviced and automated infrastructure
for managing individual desktops centralized in the data center
Yes, you could call it a desktop cloud (DaaS)
Server-based computing
Desktops are primarily stored and executed in the data
center
Consistent user experience across devices and locations
Abstraction and separation of the hardware, operating system,
application, user identity and user data layers
Virtual Desktop Infrastructure (VDI)
Basic understanding of virtual machines and vSphere
Active Directory
Basic understanding of networking
Windows desktop management
Expected Pre-existing Knowledge
View Components and Licensing
Installation of View
Configuring and Maintaining Desktop Pools
User Profiles and Data
Printing
ThinApp Packages and Deployment
Monitoring and Troubleshooting View
An Overview of the Course Topics
Lessons can be viewed in any order
Watch them straight through to learn from the ground up
Jump directly to the topics youd like to know more about
Lessons generally build on one another
Course Scenario is provided for real-world examples
Labs conducted in this fictitious environment
Consider your own environment in each lesson
If you have questions or need clarifications
Review the supporting resources
Engage the community
Provide feedback
Just ask
Lets Get Started
Course Scenario
Course Scenario
Apply book knowledge to a real world situations and problems
Consistent examples
Provides purpose and structure for the walkthroughs
Advantage of a Course Scenario
Course Scenario
Company name: Home & Family Insurance
Full service insurance company
Main corporate headquarters
Many independent insurance agents throughout the country
Our scenario will specifically address call center, accounting
and agent desktops
The data center in a colocation facility located 10 miles from
headquarters
100MB MAN connection between the two sites
Our Scenario
Course Scenario
Scenario Challenge
IT replaces one quarter of all desktops every year and has
decided to implement a virtual desktop infrastructure (VDI)
to reduce OpEx costs and centralize equipment and data.
Support for employee-owned assets and work from home
models are policies being considered for corporate adoption.
Independent insurance agents, though not employees,
require access to internal systems in a consistent, reliable
and secure manner.
Bandwidth for the agents varies greatly throughout the
country.
Our Scenario (cont.)
Lab Setup
Lab Setup
Follow along with the demonstrations
Exercise parts of View not possible in Production
Break things for troubleshooting practice
Build out various uncommon use cases
Advantages of a Lab
Lab Setup
Two HP ML150 G6
1x quad-core 2.0 Ghz Intel Nehalam
8GB RAM
3 NICs
Iomega IX4-200d
4x 1TB drives
2TB usable
Using both iSCSI and NFS
Netgear GS724T 1Gb switch
Static IP on DSL router
My Lab Hardware
Lab Setup
Windows 2008 R2 Active Directory, DNS & DHCP (DC01)
Windows 2008 R2 vCenter 5.0 (VC01)
ESXi 5.0 (ESX01 & ESX02)
Windows XP client workstation (XP01)
Windows 7 client workstation (BrianDT)
Existing Infrastructure
Lab Setup
ViewConn01 View Connection Server (Windows 2008 R2)
ViewSec01 View Security Server (Windows 2008 R2)
ViewTransfer01 View Transfer Server (Windows 2008 R2)
ViewXPParent01 Parent VM for desktop pools (Windows XP)
ThinApp01 ThinApp Packager (Windows XP)
Additional VMs Well Use
Lab Setup
Active Directory
Lab Setup
My Favorite Supporting Resources
1. Home Lab Resources
http://www.techhead.co.uk/vmware-esxi-home-lab-why-
what-and-how-considerations-when-building-your-own-
home-lab
http://www.vmwarevideos.com/video-my-home-vmware-
vsphere-lab
http://searchvmware.techtarget.com/feature/FAQ-Building-a-
VMware-home-lab
http://vsphere-land.com/vsphere-links/home-lab-links.html
Instructor: Lane Leverett
View Components and
Licensing
In This Lesson:
View Components
Management Servers
Composer
Agent
Clients
User Experience
ThinApp
View Licensing
View Manager
Connection Server
Replica Server
Transfer Server
Security Server
View Manager
First server in View Infrastructure
LDAP/ADAM Database
Web-based View Administrator
Web-based View Portal
Broker functionality
Authenticates client via Active Directory
Associates client to virtual desktop
Manages the lifecycle of virtual desktop pools
Assigns applications to desktops/pools from ThinApp repository
Enables single sign-on
View Connection Server
Additional View Manager instances
Automatically begins LDAP replication
All nodes setup in multi-master configuration
View Replica Server
Main connection point for Local Mode desktops
Data transfer point during check in and check out processes
Synchronizes changes from the checked out desktop
Distributes changes to the checked out desktop
View Transfer Server
SSL tunnel connection between Internet-based clients and an
internal View Connection Server
Usually exists in the DMZ
Directly mapped to a specific View Connection Server
SSL tunnel connection between Internet-based clients and the
users desktop
View Security Server
View Composer
Installed on vCenter Server
Linked Clone functionality
Delta disk linked to read-only parent VM disk
Based on parent VM snapshot
Advantages
Reduced storage requirements
Quicker pool deployment
Easier update and patch deployment
Easier recovery from system error
More consistent desktop environments
View Composer
View Agent
Installed on virtual desktop, physical desktop, blade PC or
Terminal Server that is used as a View desktop
Installed in parent VM or template for creation of automated
pools
Works with View Connection Server to determine availability of
desktop source
Enables single sign-on through View Connection Server
Communicates directly with View Client for features like printing
and USB redirection
View Agent
vShield Endpoint
Offload antivirus and anti-malware from individual virtual
machines
Single virtual appliance per host monitors via API
Advantages
Improve VM performance
Prevent antivirus storms
Update signatures and software once per host
vShield Endpoint
View Client
Software that enables client access to a View desktop
Versions
Windows
Mac OSX
iPad Client
Android Client
Linux Open Client
Thin Client
View Client
Special version of View Client for Windows
Download and local execution of virtual desktop
Synchronizes with View Transfer Server whenever possible
Local Mode
Client placed in public location
Desktops entitled based on device rather than user
Common, automatic login
Application-level authentication required
Kiosk Mode
User Experience
Persistent and Non-persistent Disks
Persona Management
Protocols
Terradici PCoIP
Microsoft RDP
Default can be set per pool
End user can choose, unless option is disabled
Multi-monitor display
Print
Continuity Services
Multimedia Services
USB Redirection
User Experience
ThinApp
Application virtualization
Decouples application from operating system
Places the registry and files into a virtual bubble
Application is executed using local resources, but isolated from
the local registry and file system
Changes to the registry and file system within the bubble are
written to a sandbox specific to that user
Package is a self contained executable
Agentless
ThinApp
View Bundles/Upgrades
View Licensing
vSphere
Desktop
View
Enterprise
Bundle
View Premier
Bundle
View Premier
Upgrade
vSphere Desktop

vCenter Desktop

View Manager

View Composer

Persona Management

Local Mode

vShield Endpoint

ThinApp

View Add-on
View Licensing
View
Enterprise
add-on
View
Enterprise
Add-on to
bundle
upgrade
View Premier
Add-On
View Premier
Add-on to
bundle
upgrade
vSphere Desktop

vCenter Desktop

View Manager

View Composer

Persona Management

Local Mode

vShield Endpoint

ThinApp

View Premier
One Virtualization Packager license key (except 10 packs)
One VMware Workstation license key (except 10 packs)
Clients equal to the number of concurrent View licenses
ThinApp Suite
One Virtualization Packager license key
One VMware Workstation license key
50 client licenses
ThinApp Client License
ThinApp Licensing
What We Covered
View Components
Management Servers
Composer
Agent
Clients
User Experience
ThinApp
View Licensing

Installing View 5
Installing View 5
In This Lesson:
System Requirements
Active Directory Requirements
Client Devices
Delegated Authority
Installation Walkthrough
Installing View 5
Windows Server 2003 R2 SP2 (32-bit)
Windows Server 2008 R2 (none or SP1) (64-bit)
Required for PCoIP Secure Gateway
2GB RAM for 32-bit, 6GB RAM recommended for >50 desktops
4GB RAM for 64-bit, 10GB RAM recommended for >50 desktops
Pentium IV 2GHz processor (quad processor recommended)
Virtualization software
vSphere 4.0 Update 3 or later, or vSphere 4.1 Update 1 or
later
vSphere 5.0 or later
Replicated sets should connect over a high performance LAN
Connection Server System Requirements
Installing View 5
Managed by the same vCenter Server as local mode desktops
Static IP address
LSI Logic Parallel SCSI controller
Cannot co-exist with other View Manager roles
Repository disk must have enough space to store Composer
base images
ESX(i) server hosting the Transfer Server must have access to
datastore with desktop disks
DRS for Transfer Server is set to Manual when added to View
Manager
Transfer Server System Requirements
Installing View 5
Must be installed on vCenter Server
vCenter Server 5.0 and later or vSphere 4.1 Update 1 and later
Windows Server 2008 R2 64-bit
Windows Server 2008 SP2 64-bit
Windows Server 2003 R2 SP2 64-bit
vCenter Server 4.0 Update 3 and later
Composer System Requirements
Installing View 5
Can be installed in the same SQL Server instance as vCenter DB
Composer Database Requirements
Database vCenter 5.0
and later
vCenter Server
4.1 U1 and
later
vCenter Server
4.0 U3 and
later
SQL 2005
Express
No Yes Yes
2005 SP3
and later
32/64bit
Yes Yes Yes
SQL 2008 R2
Express
Yes No No
SQL 2008 SP1
and later
32/64bit
Yes Yes Yes
Oracle 10g R2 Yes Yes Yes
Oracle 11g R2,
with Oracle
11.2.0.1 Patch 5
Yes Yes Yes
Installing View 5
The following features are only available for linked clone pools
configured with vSphere mode on ESX(i) 4 or later hosts
Utilization of local datastores
Disposable data disks
Separation of disks across datastores
Parent virtual machines with hardware version 7
Using Sysprep for linked clones (only on vSphere 4.1)
Composer Feature Requirements
Installing View 5
Windows 7 Enterprise or Professional (32-or 64-bit)
Windows Vista Business or Enterprise SP1 or SP2 (32-bit)
Windows XP Professional SP3 (32-bit)
Windows 2008 R2 Terminal Server Standard (64-bit)
Windows 2008 Terminal Server Standard SP2 (64-bit)
Windows 2003 R2 Terminal Server Standard SP2 (32-bit)
Windows 2003 Terminal Server Standard SP2 (32-bit)
Agent System Requirements
Installing View 5
Windows 7 Home, Enterprise, Professional or Ultimate (32-or
64-bit)
Windows Vista Home, Enterprise, Business or Ultimate SP1 or
SP2 (32-bit)
Windows XP Home and Professional SP3 (32-bit)
Mac OS X Leopard 10.5
Mac OS X Snow Leopard 10.6
Client with Local Mode is only supported on physical Windows
systems
Thin client devices based on the Thin Client Compatibility Guide
Client System Requirements
Installing View 5
Checking out a desktop with Virtual Hardware version 8 is not
supported
Hardware must be capable of storing and running both the
native Windows OS and the virtual machine at the same time
To run Windows Aero within Windows 7 virtual desktops
Intel Dual Core
AMD Athlon4200+ and above
nVidiaGeForce8800GT and above or ATI Radeon HD 2600
and above
To run a 64-bit virtual desktops
Intel Pentium 4 and Core 2, and Core i7 processors with
EM64T and Intel Virtualization Technology
Most AMD64 processors (except the earliest revision C
Opteron processors)
Client with Local Mode Hardware Requirements
Installing View 5
PCoIP
Dual virtual CPUs for 720p/1080p video
Dual virtual CPUs for full screen 480p video on Windows 7
Recommended guest RAM:
768MB or more for Windows XP
1GB or more for Windows 7
SSE2 extensions on client processor
If running 3D applications, like Aero, the Windows 7 virtual
machine must run virtual hardware version 8 (vSphere 5 only)
RDP
Version 6.x (included in Windows Vista and 7)
Protocol Specific Requirements
Installing View 5
Multimedia Redirection (MMR)
Client must be Windows XP, XP Embedded, or Vista
Windows Media Player 10
Only supports MPEG2, MPEG4 Part 2, WMV7-9, WMA, AVI,
MP3 and WAV
Adobe Flash Control
Versions 9 or 10
Internet Explorer
Not available for full screen mode
Smart Card
Drivers installed on both client and VM
1024-bit or 2048-bit key size
PKCS#11 or Microsoft CryptoAPI
Feature Specific Requirements
Installing View 5
Place View desktops in the same domain as the Connection
server or a domain with two-way trust
Security server does not directly authenticate users and can be
outside Active Directory trust zone
Create a new OU for the View desktops
Create dedicated OUs and groups for kiosk mode clients
Create groups based on pool and application access
At least one service account needed for View to access vCenter
and for View Composer to add computer accounts to AD
Details in View Installation Guide
Users must get added to the Remote Desktop Users group
View Group Policy Administrative Templates
Active Directory Requirements
Installing View 5
Thin Client
Zero Client
Repurposed PC
BYOPC
Client Devices
Installing View 5
Role-based Authorization within View Administrator
A role is a collection of privileges
Grant AD users or groups one or more administrative roles
Pools are arranged into folders
AD users or groups are granted roles on specific folders
Delegated Authority
Installing View 5
1. Install Connection Server
2. Install Composer
3. Configure Connection Server and Composer
4. Install Replica Server
5. Install and Configure Security Server
6. Install and Configure Transfer Server
7. Configure role-based authorizations
Installation Process
Installing View 5
What We Covered
System Requirements
Security Requirements
Client Devices
Delegated Authority
Installation Walkthrough

Configuring Virtual
Desktops
Configuring Virtual Desktops
In This Lesson:
Best Practices for Parent VM
Types of View Desktops
Pool Configuration Options
Understanding Linked Clones
Pool Sizing
Pool Creation Walkthrough
Goal is to reduce CPU, RAM, disk and network load
Remove/disable unnecessary items
Services
Scheduled Tasks
Indexing
Least Common Denominator
Eliminate visual effects
Partition alignment
Lots of image optimization guides available
Test, test, test
Parent Image Best Practices
Individual desktop
Pool
Floating
Dedicated
Automated
Manual
Linked Clone
Full Clone
Terminal Server
View Desktop Types
Pool and VM naming
Pool settings
Disk settings
Pool sizing
Template or parent image
Placement within virtual infrastructure
Connection Server restrictions (tags)
Guest customization
Entitle users/groups
Configuring View Desktop Pools
Parent VM with at least one snapshot
Replica
Thin provisioned full clone of snapshot
Choose one per pool or one per datastore
Individual VMs
Comprised of delta disk, persistent disk and disposable disk
Quickprep
Quicker alternative to Sysprep
Storage Overcommitment
None, Conservative, Moderate, Aggressive
Composer operations
Refresh, Recompose, Rebalance
Composer Linked Clones
Preserves user data during Composer operations
Contains user profile and My Documents
Can detach disk from View desktop
Must be reattached to desktop with same OS
Persistent Disk
Slows the growth of linked clone
Contains paging file and temp files
Files thrown away when desktop is powered off
Stored on same datastore as the linked clone disk
Disposable Data Disk
Minimum number of desktops
View ensures at least this number will be deployed
Number of spare (powered on) desktops
Number of desktops that will be ready for immediate
connections
Maximum number of desktops
May need to be greater than the number of licenses
Power state of unused desktops based on pool power policy and
number of spare desktops
Pool Sizing
Pool Provisioning Settings
Min: 10
Max: 100
Spare: 5
Power policy: Suspend
0 users: 10 deployed, 5 powered on
Pool Sizing Example
What We Covered
Best Practices for Parent VM
Types of View Desktops
Pool Configuration Options
Understanding Linked Clones
Pool Creation Walkthrough

Maintaining Desktop
Pools
Maintaining Desktop Pools
In This Lesson:
User Entitlements
Composer Operations
Editing Pools
Managing User Sessions
Desktop Pool Management Demonstration
A user must be entitled before accessing a desktop in a pool
Access can be granted individually or by group
Restricted entitlements limit pool access to specific Connection
Servers
Create tags on Connection Servers
Assign tags to a pool to limit Connection Server access
User Entitlements
Refresh
Returns virtual desktop to original state
All changes in the delta disk are eliminated
Disposable disk is deleted and recreated
Can be on demand, scheduled, on user logoff or when linked
clone reaches specified size
Can force users off with a message and timeout
Local mode desktops must be checked-in
Use cases:
Maintaining consistent automated floating pool
Eliminate changes that cause user problems
Easily return to clean state during application testing
Composer Operations
Recompose
Relink desktop to new parent snapshot
All changes in the delta and disposable disks and are
eliminated
Does not affect persistent disks
Cannot recompose from one OS to another (i.e. Windows XP
to Windows 7)
Can force users off with a message and timeout
Local mode desktops are updated only if they are checked in
Use Cases
Patching Windows or installed software
Quick deployment of configuration change
Easily revert change to older snapshot
Composer Operations
Rebalance
Evenly distributes linked clones across configured datastores
Better balance of IO and even utilization of space
Can be scheduled or on demand
Users need to be logged off
Also performs a refresh of the desktop
Use cases
Relevel datastores after adding a new datastore to pool
Readjust usage of datastores after changing over commitment
settings
Composer Operations
Adjust Pool Size
Add/Remove Desktops from Manual Pool
Enable/Disable Pool
Enable/Disable Provisioning
All pool settings can be modified except:
Pool Type
Pool ID
Usage of Persistent or Disposable disk
QuickPrep or Sysprep choice
Editing Pools
Disconnect Session
Disconnects user from session
Session remains active and user can reconnect
User is logged off if Automatically logoff after disconnect is
enabled
Logoff Session
Disconnects and logs user off session
Reset
Non-graceful power cycle of desktop
User will be disconnected
Send Message
Message is displayed on users desktop
What We Covered
User Entitlements
Composer Operations
Editing Pools
Desktop Pool Management Demonstration

In This Lesson:
Value of the User Profile
Contents of the User Profile
Options for Managing User Profiles
View Persona Management
Managing View Persona Management
View Persona Management Settings
Persistent Disk
Disposable Disk
Folder Redirection
Demonstrations
Maintains a users state and customizations across sessions
By default only exists on the local hard drive
Windows XP/2003: C:\Documents and Settings
Vista/7/2008: C:\Users
Created from the local Default User profile on first logon
If stored on a network drive, can provide consistent user
environment across multiple computers
My Documents
AppData
Desktop icons and placement
Desktop wallpaper
Windows Theme
Toolbar configuration
Custom dictionary
Startup applications
Recent Documents
Many Control Panel settings
NTUSER.DAT
Default User Profile
Mandatory Profile
Active Directory Roaming Profile
View Persistent Disk
Third-party Utilities (i.e. Liquidware Labs, AppSense, Unidesk,
RES, triCerat)
Only available for View virtual desktops
Native Windows profile format
Copies only critical files during login
Registry and Startup folder are default
Additional directories can be defined
Files are copied to desktop when accessed
Regularly syncs changes back to the network
On logoff, only modified files are copied to network file server
Faster login and logoff times than Active Directory Roaming
Profiles
Can work with Active Directory Roaming Profiles
Implemented as part of the View Agent
Managed via Group Policy
ADM template provided with View 5 Connection Server
(ViewPM.adm)
Can be applied via Active Directory or Local Group Policy
All settings part of Computer Configuration and should be
applied to the virtual desktop OU
Use Microsoft User Profile Hive Cleanup (UPHClean) service on
Windows XP
Manage User Persona
Used to turn on Persona Management
Also used to set the synchronization interval
Persona Repository Location
When disabled, uses the Active Directory Roaming Profile
path
Enable to specify an alternative UNC path
Use the Override Active Directory user profile path if it is
configured option to use this UNC path
Remove Local Persona at Logoff
Deletes local version of profile during logoff
Could lead to increased logoff times
Can choose to not delete the Local Settings
Roam Local Settings Folders
Includes the users Local Settings or AppData\Local in
persona
Useful for applications that store user-specific data in Local
Settings
Files and Folders to Preload
List of files and folders to be downloaded during login
The Startup folder is always preloaded
Paths are relative to the root of the local profile
Files and Folders to Preload (Exceptions)
Items within the preloaded paths that should not be
preloaded
Windows Roaming Profiles Synchronization
Files and folders to behave like standard AD Roaming
Profiles
Downloaded during login and uploaded only at logoff
Windows Roaming Profiles Synchronization (exceptions)
Items not to behave like standard AD Roaming Profiles
Files and Folders Excluded from Roaming
Files and folders that should be excluded from the persona
Always includes the user profiles temp folder, the ThinApp
cache folder, and the cache folders for web browsers
Files and Folders Excluded from Roaming (Exceptions)
Files and folders within the Files and Folders Excluded from
Roaming paths that should be included in the persona
Folders to Background Download
Folders that should begin downloading in the background
immediately after login
Stages files for use without slowing down login process
Folders to Background Download (Exceptions)
Files and folders within the Folders to Background Download
paths that should be downloaded on access
Hide Local Offline File Icon
Enabled by default
Disabling shows an offline icon when file isnt downloaded
Show Progress When Downloading Large Files
Shows a progress window when downloading a large file
from remote persona directory
Useful when users need feedback when launching large files
Minimum File Size to Show Progress Window
Sets the minimum size (in MB) a file should be to show the
download progress window
Enabled when Show Progress When Downloading Large Files
is enabled
Default value of 50MB
Show Critical Errors to Users via Tray Icon Alerts
Uses a system tray icon to display critical alerts
Disabled by default
User profile and data are redirected to this disk
Only available for dedicated pools
Not affected by Composer operations
Place all persistent disks on single datastore for easy replication
and/or backup
Detach from linked clone
Choose datastore to which the disk will be moved
Desktop is deleted
Reattach to another linked clone
Must be reattached to the same OS version
Can import from vCenter
Recreate desktop from persistent disk
Desktop is recreated in original pool
Persistent Disk
Windows paging file and temp files moved to secondary
nonpersistent vmdk
View can easily replace the disk with a clean copy
Slows the growth of the linked clone disk
Size it larger than the maximum sized Windows paging file
Stored on the same datastore as the OS disk (not configurable)
Disposable Disk
Folder appears local but actually resides on a network share
Reduces size of user profile
Active Directory Folder Redirection provides 13 different folders
that can be redirected in a Windows 2008 native AD
View Persona Management provides 22 different folders that can
be redirected
VMware recommends relying on View Persona Management on-
demand profile download instead of Folder Redirection
Folder Redirection
View Persistent Disk
View Disposable Disk
1. VMware View Persona Management Deployment Guide -
http://www.vmware.com/files/pdf/view/VMware-View-
Persona-Management-Deployment-Guide.pdf
2. VMware View 5.0 Administration Guide -
http://pubs.vmware.com/view-
50/topic/com.vmware.ICbase/PDF/view-50-administration.pdf
What We Covered
Persistent Disk
Disposable Disk
Folder Redirection
Demonstrations

Printing
Printing
In This Lesson:
Printer Mapping Options
View Location-Based Printing
Implementing View Location-Based Printing
Walkthroughs
Printing
Allow redirection of client printers
Uses the Virtual Printing option of the View Agent
OEM version of the ThinPrint .print technology
Utilizes a universal print driver
Provides print job compression to improve transfer time
Login script printer mapping
Map printers based on user, groups, computer name, etc.
View provides information about the client device in
HKCU\Volatile Environment that can be used (IP, client
machine name, type of device, etc.)
Active Directory Group Policy
View location-based printing
Printing
Configured via Group Policy applied to the virtual desktops
Printer is directly mapped within the virtual desktop
Requires the printer driver be installed in the virtual desktop
Printers are mapped to the virtual desktop during user login
based on a rules table
A combination of rules is defined for each printer
Printing
Each row defines criteria for when the printer will be mapped
Client IP Range
Client name
Client MAC address
Username or group membership
Each row defines a printers properties
Printer Name
Printer Driver
IP Port or ThinPrint port
For network printers, use IP_ then the IP address
Whether or not the printer should be default
View Location-Based Printer Mapping
Printing
To access Group Policy settings, you must register
TPVMGPoACmap.dll on all computers that will manage the GPO
32-bit and 64-bit versions can be found on the View
Connection Servers in:
C:\Program Files\VMware\VMware
View\Server\extras\GroupPolicyFiles\ThinPrint
Register the DLL using regsvr32
Create a GPO and apply it to the OU that contains the virtual
desktops
Expand Computer Configuration > Software Settings and select
AutoConnect Map Additional Printer for VMware View
Double-click Configure AutoConnect Map Additional Printers to
access the View Location-Based Printing configuration window
Local Printer Redirection
View Location-Based Mapping
Printing
2. ThinPrint GPO Configuration for Location-Based Printing
http://www.vmware.com/files/pdf/VMware-View-
ThinPrintGPOConfig-IG-EN.pdf
3. Printing in a VMware View Environment Explained
http://www.thatsmyview.net/2011/08/16/drucken-in-einer-
vmware-view-umgebung/
Printing
What We Covered
Walkthroughs

Creating ThinApp
Packages
Creating ThinApp Packages
In This Lesson:
How ThinApp Virtualizes Applications
ThinApp Requirements and Limitations
Steps to Virtualizing with ThinApp
ThinApp Packaging Machine Best Practices
Composition of a ThinApp Projects and Packages
Advanced ThinApp Concepts
Testing Packages
Packaging Walkthrough
Provides a layer of virtualization between OS and application
Partially isolates application from other applications and OS
Runs in User Mode within Windows so user does not have to
have Administrator rights
When application is launched, a bubble is created
Contains a virtual file system and registry that can replace or
merge with the OS file system and registry
Any changes within the bubble are kept in the sandbox
Permeability of bubble is determined during package
creation
Packaging once allows deployment to most Windows versions
Contained in a single executable or small collection of files
Entry points are created to provide access into the bubble
32-bit Windows NT and later
64-bit Windows XP and later
16-bit applications can only be run on 32-bit versions of
Windows
32-bit applications can be run on 32-bit or 64-bit versions of
Windows
Terminal Server or Citrix XenApp
ThinApp Requirements
Applications that do not natively support the deployment OS
Applications requiring low level OS interaction or installation of
kernelmode device drivers
Antivirus, VPN clients and personal firewalls
ODBC drivers work because they are user mode drivers
Scanner drivers and printer drivers
COM Plus and Network DCOM
Reduced functionality of Windows shell integration
COM and DCOM are only supported within a ThinApp bubble
64-bit applications
16-bit applications cannot be run on a 64-bit OS
ThinApp Limitations
Clean Windows VM with ThinApp installed and a snapshot
Pre-scan before any installs
Catalogs the file system and registry
Install the application, including any configuration and tests
Post-scan
Catalogs the file system and registry and compares to
prescan catalog
Configure the ThinApp package
ThinApp copies all files that differ between pre-scan and post-
scan to the Project directory
Directly manipulate project files, registry and package
configuration
Build the package
Use a VM to take advantage of snapshot capabilities
VMware vSphere or VMware Workstation
Use the earliest OS users will use to run package
Usually Windows XP SP3
Use a clean install of the OS
Minimal software installed
If a file the application needs is already in the OS, then
ThinApp will not capture the file
Generally, just install Windows updates
Can be a domain member
Makes accessing network shares easier
Due to regular reverting of snapshots, set AD computer
account to never expire password
Virtual registry
Virtual filesystem
##Attributes.ini
Build.bat
Package.ini
Capture Machine Overview.txt
Composition of a ThinApp Project
Virtual registry
Virtual filesystem
Primary data container
Entry points
Sandbox
MSI package
Composition of a ThinApp Package
Package.ini settings
Optional and Required AppLinks
Sandbox properties
AppSync
MSI package configuration
Any settings configured during the Setup Capture Wizard
Isolation settings
Modified in the Package.ini, registry files or ##Attributes.ini
Sandbox Merge (sbmerge.exe)
Rebuilds package incorporating all changes in the sandbox
ThinApp scripts
Modify the behavior of a package at runtime
Dirty Test
Test package on same machine install and packaging was
completed on
Washed Test
Test package on same machine after uninstalling installed
application
Clean Test
Test after reverting packaging VM to clean state
Production Test
Test using actual desktop, including proper group policies
Testing Packages
Create a ThinApp Package
1. ThinApp Users Guide
http://www.vmware.com/pdf/thinapp47_manual.pdf
2. ThinApp Reviewers Guide
http://www.vmware.com/files/pdf/VMware-ThinApp-
Reviewers-Guide.pdf
3. ThinApp Community Contributed Project Files
http://communities.vmware.com/thinap.jspa
4. ThinApp Team Blog
http://blogs.vmware.com/thinapp/
5. ThinApp Package.ini Parameters Reference Guide
http://www.vmware.com/pdf/thinapp47_packageini_referenc
e.pdf
What We Covered
ThinApp Requirements and Limitations
Composition of a ThinApp Projects and Packages
Testing Packages
Packaging Walkthrough

ThinApp Deployment
ThinApp Deployment
In This Lesson:
Execution Modes
Registering Packages
Deployment Options
Package Security
Deployment Walkthroughs
ThinApp Deployment
Deployed Execution
Package is copied to the desktop and registered
Generally utilizing the MSI package
Can use software deployment tools like SCCM
Best choice for Local Mode virtual desktops and laptops
Streamed Execution
Package is executed directly off of a network location
Windows shortcuts refer to a mapped drive or UNC path
Package is streamed directly to desktop RAM with no
caching to disk
Easier updatability
Best choice for LAN deployment and View desktops
Execution Modes
ThinApp Deployment
Makes application appear and behave like a locally installed
application
Creates local file extension & protocol associations
Based on FileTypes & Protocols parameters
Creates proper shortcuts on the desktop and start menu
Based on Shortcuts parameter
Adds an entry into the Add/Remove Programs Control Panel
Uses InventoryName parameter
Use the thinreg.exe utility
ThinApp Deployment
Usually run from a script (example: thinreg.exe
\\server\share\directory\package.exe)
Copy from the ThinApp installation directory to file server
Must be run for each entry point
Built into MSI package
Useful parameters
/a /allusers registers package for all users
/q /quiet suppresses all messages, including errors
/u /unregister /uninstall unregisters the package
/r /reregister forces a registration even if already
registered
/noarp doesnt create Add or Remove Programs control
panel entry
ThinReg.exe Utility
ThinApp Deployment
Option 1 Software distribution application
Applications like SCCM, Altiris or Group Policy software
distribution
Utilizes the MSI package
Configure sandbox to use %AppData% or network share
Option 2 USB
Place ThinApp package onto a USB thumb drive
Portable to all Windows computers
Configure sandbox to use same directory as the package
Deployment Options
ThinApp Deployment
Option 3 Login script
Script the thinreg.exe utility to register applications during
login
Use a VBScript to apply logic to the registration process (i.e.
group membership, location-based)
Can run once per entry point or utilize wildcards to do
multiple endpoints & packages per thinreg.exe execution
Option 4 Shortcut deployment
Use a script, default user profile or third-party utility to copy
or create shortcuts in the users Desktop and Start Menu
File & protocol extensions will not be properly configured
since thinreg.exe is not utilized
Deployment Options (cont.)
ThinApp Deployment
Option 5 View integration
Utilizes a ThinApp Repository
Define ThinApp deployment per pool or desktop
Registers ThinApp packages during desktop customization
Can deploy package using streamed or deployed execution
Requires creation of MSI package
Option 6 3
rd
party applications
Deployment designed specifically for ThinApp packages
Liquidware Labs
AppSense
RES Software
Deployment Options (cont.)
ThinApp Deployment
Define Permitted Groups within package
Blocks users not in listed AD groups from executing
Prevents package from launching application
Directory permissions
thinreg.exe registers in user mode, so user must have access
to package in order to register it
Could register entire directory of ThinApp packages utilizing
wild cards
Custom scripting option
Scripts can be added to package to execute prior to launch
Can use variables other than group membership to allow or
prevent user access
Third-party deployment tools
Package Security
Login Script Deployment
Integration with View
ThinApp Deployment
1. ThinApp Users Guide
http://www.vmware.com/pdf/thinapp47_manual.pdf
2. ThinApp Deployment Guide
http://www.vmware.com/files/pdf/VMware_ThinApp_Deploym
ent_Guide.pdf
ThinApp Deployment
What We Covered
Execution Modes
Deployment Options
Package Security
Deployment Walkthroughs

Monitoring View
Monitoring View
In This Lesson:
Event Database
System Health Dashboard
View Administrator Dashboard
Desktop States
Session Status
Monitoring Walkthroughs
Monitoring View
Store event information that occurs on the Connection Servers,
Agents and View Administrator
The Events screen displays the details of these events
Stores the data historically
Doesnt display this data in the View Administrator
Must be accessed using database queries
Can define how far back events will appear in View
Administrator (up to 2000 entries)
Microsoft SQL or Oracle database
Uses SQL Server Authentication
Defining a table prefix allows multiple View infrastructures to
use the same database
Event Database
Monitoring View
Located in the top left of the View Administrator
Displays the current number of:
Remote sessions
Local sessions
Problem desktops
Error and Warning events
Displays the current number of View components, vSphere
services, AD domains and datastores that are in each of the
following states:
Up
Down
Unconfigured
Unknown
Monitoring View
Provides detail on the health of the entire view system,
including versions, some configuration details and current status
Current status of all desktops summarized by status
Listing of all utilized datastores with capacity information
Monitoring View
Summary counts in the View Administrator Dashboard
Detail available in the Desktops Inventory
Desktop can be in only one state at a time
Preparing
Provisioning VM is being created
Customizing QuickPrep/SysPrep, View deploying ThinApp
Waiting for agent VM was powered on, but Agent is not
available yet
Deleting VM marked for deletion
Maintenance mode Users cannot login
Startup Agent is available, but other services are still
starting
Desktop States
Monitoring View
Prepared for use
Provisioned VM created but powered off
Available VM powered on and ready for an user session
Connected Session that is currently connected
Disconnected User assigned, but not connected
Checked out VM is currently running in Local Mode
Unentitled desktops
Desktops that are assigned to a user that is no longer entitled to
the pool
Can be viewed in the Desktops Inventory or using vdmadmin
Desktop States (cont.)
Monitoring View
Can view and manage individual user sessions under the
Monitoring section of View Administrator
Remote Sessions Users connected to desktops running
centrally
Local Sessions Users who have desktops checked out in Local
Mode
Session Status
Monitoring View
What We Covered
Event Database
Desktop States
Session Status
Monitoring Walkthroughs

Troubleshooting View
In This Lesson:
Common Failure Points
Connection Procedures
How Linked Clones Work
Ports Needed For View
PCoIP Performance
Log Locations
Collecting Diagnostic Information
Troubleshooting Walkthroughs
Network connectivity between Client and Connection or Security
Server
Check proxy and firewall settings
Verify DNS resolution
May need to configure IP in the External URL field in the
Connection Server or Security Server configuration
Enable PCoIP Secure Gateway and set PCoIP External URL
Network connectivity between Desktops and Connection Server
Check proxy and firewall settings
Verify DNS resolution on Desktop and Connection Server
Verify desktop received valid DHCP IP address
Failure to create pool
Verify vCenter web service is running and there are no
network problems from Connection Server
Check amount of free space on configured datastores
Verify service account has proper permissions to create a
pool, access the template, access configured customization
specification or parent VM, and access vSphere
infrastructure
If vCenter is overloaded, reduce the maximum number of
concurrent provisioning and power operations or configure
additional vCenter Servers
Common Failure Points (cont.)
VM stuck in Provisioning state
Most likely due to restart of Connection Server
Delete VMs and allow View to attempt provisioning again
VM stuck in Customizing state
Most likely due to insufficient free space on datastore to
start VM
Delete VM,
USB Redirection
Use PCoIP instead of RDP
Ensure USB Redirection is enabled in the View policies
Examine the virtual desktops logs for entries of class
wssm_usb
Examine the clients logs for entries of class wswc_usb
Verify the VMware View Virtual USB Device Manager and
VMware View Virtual USB Hub drivers are installed and
enabled on the virtual desktop
Verify the VMware View Generic USB Device driver and the
USB driver for the redirected device are installed and
enabled on the client device
1. Client initiates connection to Connection Server, providing username
and password (TCP port 443)
2. Connection Server returns a list of entitled desktops and user selects
one (TCP port 443)
3. Client initiates PCoIP connection to desktop (TCP port 4172)
4. Client and Agent negotiate PCoIP session (TCP port 4172)
5. Agent initiates PCoIP data channel connection to Client (UDP port
4172)
6. Control and data session opened between Client and Agent (UDP port
4172)
7. PCoIP heartbeat connection opened between Client and Agent (TCP
port 4172)
8. View Session heartbeat between Client and Connection Server (TCP
port 443)
All linked clone desktops link back to a replica VM
Replica is a thin provisioned full clone of the parent VM
snapshot chosen as the base image
One replica per datastore unless stored on specific datastore
All pools using the same parent VM snapshot will share replicas
Replicas can be orphaned and need to be deleted manually
Replicas can be viewed by enabling Show View Composer
virtual machines in Edit > Client Settings
To unprotect all replicas, use the following command on the
vCenter/Composer server:
SviConfig-operation=UnprotectEntity-VcUrl=https://vc01/sdk
-Username=User1 -Password=123
-InventoryPath="/Home/vm/VMwareViewComposerReplicaFolder"
-Recursive=True
TCP 80/443
Client -> Connection or Security Server
Security Server -> Transfer Server
Connection Server -> vCenter Server
TCP 8009
Security Server -> Connection Server
TCP 4001
Security Server -> Connection Server
Virtual Desktop -> Connection Server
TCP 3389 (RDP), 32111 (USB redirection), 9427 (multimedia)
Security Server -> Virtual Desktop
TCP 4172 (PCoIP), 32111 (USB redirection)
Client -> Connection or Security Server
Connection or Security Server -> Desktop
UDP 4172 (PCoIP)
Client <-> Connection or Security Server
Connection or Security Server <-> Desktop
TCP 4100
Inter-Connection Server communication
Ports Needed For View (cont.)
PCoIP is self adapting, so only tweak when necessary
Reduce effects and animations
Review logs first
Use PCoIP ADM template
Max Bandwidth Maximum PCoIP session bandwidth (Kbps)
Bandwidth Floor Minimum PCoIP session bandwidth (Kbps)
MTU Size Larger could result in fragmentation
Minimum Image Quality Lower quality = higher frame rate
Maximum Initial Image Quality Lower quality = smaller
bandwidth peaks
Maximum Frame Rate Lower = less bandwidth
Audio Bandwidth Limit Maximum bandwidth for audio
Encryption Determines algorithms available
PCoIP Performance
Agent, Connection Server, Security Server and Transfer Server
C:\Documents and Settings\All Users\Application
Data\VMware\VDM\logs
C:\ProgramData\VMware\VDM\logs
Client
C:\Documents and Settings\%username%\Local
Settings\Application Data\VMware\VDM\Logs\
C:\Users\%username%\AppData\Local\VMware\VDM\Logs\
Composer
C:\Documents and Settings\All Users\Application
Data\VMware\View Composer\Logs
C:\Users\All Users\VMware\View Composer\Logs
Log File Locations
Create an information bundle to aid VMware with
troubleshooting
Procedure depends on component
View Agent
vdmadmin-A -d Administrative_Pool-m Admin_02_DT-
getDCT-outfileC:\myfile.zip
Run on View Connection Server
View Client
Click Options >> then click Support Information
Click Collect Support Data then click Yes
A command window will show the progress of the collection
Provide relevant Connection Server URLs when prompted
View Composer
Go to C:\Program Files\VMware\VMware View Composer in a
command prompt on the vCenter Server
Run cscript".\svi-support.wsf
View Connection Server
Set the level of logging by using: Start > All Programs >
VMware > Set View Connection Server Log Levels
Complete task(s) that are failing
Create log bundle: Start > All Programs > VMware >
Generate View Connection Server Log Bundle
Support.bat
Can be found in the DCT directory in the installation location
for the Agent, Client and Connection Server
Collecting Diagnostic Information (cont.)
What We Covered
PCoIP Performance
Log Locations
Troubleshooting Walkthroughs
VMware View 5 Essentials

Upgrading to View 5
Upgrading to View 5
In This Lesson:
Version Compatibility
Upgrade Steps
Upgrade Demonstrations
Upgrading to View 5
From the View 5 Upgrade Guide (http://pubs.vmware.com/view-
50/topic/com.vmware.ICbase/PDF/view-50-upgrades.pdf):
Upgrading to View 5
1. Verify system compatibility
2. Upgrade Connection Servers
3. Upgrade Transfer Servers
4. Upgrade Composer
5. Upgrade Agents
6. Upgrade Clients
Upgrade Steps
Upgrading to View 5
Supported Infrastructure Differences
Connection Server
Recommended config is now 4 CPUs (was 2 CPUs)
Windows 2003 without R2 no longer supported
vSphere
3.5 no longer supported
4.0 must be at least Update 3 (was Update 2)
4.1 must be at least Update 1
5.0 now supported
Composer
Windows 2008 R2 is only supported platform (was 2003 or
2008)
1. Verify System Compatibility
Upgrading to View 5
Make sure to have your View 5 key available
Snapshot if running in a VM
Document all global settings and pool configurations
Create a backup of LDAP database (vdmexport.exe)
Stop the View Connection Server service on all servers
Leave the VMwareVDMDS service running
Run the View 5 installer
Verify service started, login to View Administrator and version
Enter View 5 license key
Stop Connection Server service and upgrade all other
Connection Servers one at a time
Start View Connection service on all servers
Repeat process to upgrade Security Servers
Upgrading to View 5
If upgrading onto a new server (i.e. Windows 2003 to Windows
2008 upgrade):
Upgrade one existing View Connection server to 5.0
Make sure new Connection Server can communicate with
existing Connection Server
Install a replica instance on the new server, pointing to
existing instance
Uninstall View Connection Server from existing server
If uninstalled server still appears in the Server section of
View Administrator:
Run vdmadmin.exe -S -s server_name -r
Upgrading to View 5
In View Administrator, go into the Servers section and place the
Transfer Server into Maintenance Mode
Run the View 5 installer on the Transfer Server
Verify the Transfer Server service restarts
In View Administrator, remove the Transfer Server from
Maintenance Mode
3. Upgrade Transfer Servers
Upgrading to View 5
Snapshot if running in a VM
Backup vCenter and Composer databases
Make a copy of the SSL certificates folder:
%ALLUSERSPROFILE%\Application Data\VMware\VMware
VirtualCenter
Disable provisioning for linked-clone pools (can be re-enabled
after Agents are updated)
Set Refresh OS disk on logoff to Never
Run the View Composer install
4. Upgrade Composer
Upgrading to View 5
If upgrading from Composer 1.0 (View 3.0), you will be asked to
have the installer upgrade the database
Upgrades direct from Composer 1.0 are not supported
If a Database upgrade completed with warnings
dialog appears, you can safely ignore it
The installer may adjust the Composer port number from 8443
to 18443
May need to modify the vCenter Server configuration within
View Administrator to reflect the new port number
Enter vCenter password and check Enable View Composer
4. Upgrade Composer
Upgrading to View 5
If upgrading to View Composer 2.7 and vCenter Server 5.0 from
a 32-bit instance of vCenter Server 4.0.x or earlier
Upgrade to View Composer 2.6 & vCenter 4.0.x
Backup the RSA keys: aspnet_regiis -px
SviKeyContainer keys.xml -pri and copy to
destination server
Stop vCenter & Composer services on source machine
Load the RSA keys: aspnet_regiis -pi
SviKeyContainer path\keys.xml on the
destination server
Follow instructions in the vSphere 5.0 Upgrade Guide to
migrate vCenter to the destination server
Manually copy the View Composer database (if local)
4. Upgrade Composer
Upgrading to View 5
If upgrading to View Composer 2.7 and vCenter Server 5.0 from
a 32-bit instance of vCenter Server 4.0.x or earlier (cont.)
Create 64-bit DSNs for vCenter and Composer
Run the View Composer 2.7 installer
Ensure all services have started
Validate View Administrator connectivity to vCenter Server
4. Upgrade Composer
Upgrading to View 5
Run Agent installer in Parent VM
Create new snapshot
Deploy a small test pool to verify
Make sure to update Agents inside manual pool desktops,
physical desktops and Terminal Servers used as desktop sources
Enable provisioning on linked-clone pools and set the Refresh
OS disk on logoff setting to its original setting
Recompose linked-clone pools using new snapshot
5. Upgrade Agents
Upgrading to View 5
Have users using the Local Mode client check-in their desktops
Upgrade View Client software on Windows machines
Update firmware on thin clients (based on manufacture
availability)
6. Upgrade Clients
Connection Server Upgrade
Transfer Server Upgrade
Composer Upgrade
Agent Upgrade
Client Upgrade
Upgrading to View 5
1. VMware View 5.0 Upgrade Guide
50/topic/com.vmware.ICbase/PDF/view-50-upgrades.pdf
2. VMware vSphere 5.0 Upgrade Guide
http://pubs.vmware.com/vsphere-
50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-
server-50-upgrade-guide.pdf
Upgrading to View 5
What We Covered
Upgrade Steps
Upgrade Demonstrations

Next Steps
Next Steps
Installation of View
Configuring and Maintaining Desktop Pools
Printing
ThinApp Deployment
Monitoring View
Preparing for the VMware VCA-DT Certification Exam
What We Learned
Next Steps
Practice and Experiment
Research
Deploy to Production
Proof of Concept
Pilot
Phased Rollout
Certification
What Next?
Next Steps
VCA-DT
Entry level desktop certification
VCP-DT
System engineer level certification
More focus on the individual components, installation and
configuration
Requires VCP
VCAP-DT
Architect level certification
Validates understanding of requirements and design
Requires VCP-DT
VMware Desktop Certifications
Next Steps
1. VMware View Documentation
http://www.vmware.com/support/pubs/view_pubs.html
2. VMware View Community
http://communities.vmware.com/community/vmtn/desktop/vi
ew
3. VMware User Group (VMUG)
http://www.myvmug.org
4. VMware Certifications
http://mylearn.vmware.com/portals/certification/
5. View-centric Blogs
http://blogs.vmware.com/view/
http://blogs.vmware.com/thinapp/
http://www.myvirtualcloud.net/
http://www.thatsmyview.net/
Next Steps
We Value Your Opinion
Next Steps
Call us at 1-888-229-5055 (worldwide: 1-847-776-8800)
Email us at feedback@trainsignal.com
Post on our forums at http://forums.trainsignal.com/
Comment on our blog: http://www.trainsignaltraining.com
Instructors:
brian.knudtson@gmail.com or @bknudtson
lane.leverett@gmail.com or @wolfbrthr

VMwar View Instructor Slides

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VMwar View Instructor Slides

Uploaded by

Copyright:

Available Formats

VMware View 5

VMware View 5 Essentials Training

VMware View 5 Essentials Training

VMware View 5 Essentials Training

VMware View 5 Essentials Training

VMware View 5 Essentials Training

VMware View 5 Essentials Training

VMware View 5 Essentials Training

VMware View 5 Essentials Training

VMware View 5 Essentials Training

VMware View 5 Essentials

VMware View 5 Essentials Training

You might also like