ILT ViewTechExpress 02IntrotoVMwareView VV4.5 v1.0
ILT ViewTechExpress 02IntrotoVMwareView VV4.5 v1.0
> Architecture > Key Benefits and Features > How Customers Use View > View Components
ILT_TechExpress_02IntrotoVMwareView_VV4.5_v1.0
2010 VMware Inc. All rights reserved 2010 VMware Inc. All rights reserved
Module Outcomes
Module 2: Introduction to VMware View Diagram the View architecture. Discuss the key benefits and features of View. List common View use cases. List and explain the View components.
User
Anytime, anywhere access Device, OS and apps diversity
IT
Increasing IT costs Security and compliance risks
Data
Profile
Persona
Persona
Apps
Persona Apps OS
OS
Persona Apps OS
Data
Apps
OS
Persona Apps OS
Data
Key Benefits
Creates an individual, personal view of all of a users applications and data on any device from any location. Reduces costs of overall desktop computing. Increases security. Greater management and control. Increased business agility and flexibility. Implicit business continuity and disaster recovery. Decreased power consumption.
Support and subscription services. Guest operating system licensing for desktops.
Key Features
vSphere and VMware Infrastructure 3 integration
Ability to cluster many connection brokers for high availability and redundancy
Task Workers
Knowledge Workers
Power Users
Mobile Workers
Device flexibility 24x7 access Custom applications Install requirements Best user experience across all applications
Device flexibility Disconnected Multiple applications Best user experience across all applications Remote office
Provide a continuous availability of desktops. Ensure highly available desktop. Provide a costeffective, simpler, and more reliable disaster recovery solution.
Provide offshore developers control while keeping IP in the datacenter. Remove the need of IT resources at branch. Manage remotely desktops centralized at branch or in corporate datacenter.
View Composer
Storage-saving linked clones Rapid desktop deployment Quick update/patch management Tiered storage options
Self-service, single sign on Integrated remote desktop PCoIP capability, and optimized multimedia delivery Support for thick and thin client devices Support for Windows and Mac client devices Location-based printing
ThinApp
Application virtualization View Manager can assign and automatically deploy ThinApp MSI packages.
Virtual Printing
Driver-free printing
Desktop connection broker maintains desktop assignment. View Manager can run on either a physical or virtual machine. Uses vCenter Server service to provision virtual desktops as needed: Existing desktops (dedicated to a user) Automated pools Supported desktop operating systems: Windows XP Windows Vista Windows 7 For DMZ deployments, View Manager provides a Security Server. For high availability deployments, Replica instances of View Connection Server can be deployed. View Administrator Web-based interface.,
Thin Client
Non-vCenter Server
Physical PCs
View Connection Server View Manager Security Server View Manager Transfer Server View Administrator Interface
View Agent
View Composer
View Client View Client with Local Mode View Portal Web page
A locally installed software application that communicates with the View Connection Server in order to allow users to connect to their desktops.
A version of the View Client that is extended to support the View Client with Local Mode feature which allows users to download or check out virtual machines and use them on their local systems. The View Portal Web page can be used to download the full View Client installer for computers with Windows or Mac operating systems.
Single Sign On to Virtual Desktop and Applications View PCoIP Display Protocol Using Smart Cards Location-Based Printing
Connection Server
VMware PCoIP is the preferred and recommended protocol of choice for addressing the broadest set of use cases and deployment options. VMware and Teradici codeveloped PCoIP. PCoIP provides an optimized PC experience for the delivery of images, audio, and video content for a wide range of users on the LAN or across the WAN
icons
motion video
text photos
graphics
1. Initial image
Low BW and latency Grainy picture Lossless text 0.20.5 bits/pixel
2. Perceptually lossless
Built over a few frames High quality picture Lossless text 13 bits/pixel
3. Lossless
Built as BW permits Lossless picture Lossless text 515 bits/pixel
Smart card authentication is supported by the Windows-based View Client, and View Client with Local Mode, and the full Linux client that OEMs use. It is not supported by View Administrator. Two-factor authentication:
Verifies what the user has (the smart card). What the user knows (the PIN). Client machines must have smart card middleware and a smart card reader.
To install certificates on smart cards, you must set up a computer to act as an enrollment station.
User initiates a connection to the View Connection Server instance or security server, the View Connection Server instance or security server sends a list of trusted certificate authorities (CAs) to the View Client.
The View Client checks the list of trusted CAs against the available user certificates, selects a suitable certificate, and then prompts the user to enter a smart card PIN.
The View Client sends the user certificate to the View Connection Server instance or security server, which verifies the certificate by checking the certificate trust and validity period.
To use smart cards with local desktops, you must select a 1024-bit or 2048-bit key size during smart card enrollment.
Certificates with 512-bit keys are not supported for local desktops. Users must use the same authentication method that they used to authenticate to View Connection Server the last time they logged in.
The PCoIP Server feature lets users connect to the View Desktop using the PCoIP display protocol.
Location-Based Printing
Allows IT organizations to set a policy to automatically map virtual desktops to a printer that is closest to the endpoint device.
Floor 3
Floor 2
Floor 1
View Manager
View Client with Local Mode
Capability
Robust Transfer Infrastructure Centralized Data Control Improved Security
Disaster Recovery
Infrastructure Cost Savings Latest Runtime Platform
Have the required license. Set up a View Transfer Server. Use a desktop source managed by vCenter Server. Apply settings and policies specific to local mode.
View Manager
View Client with Local Mode
View Composer
Key Concepts How View Composer Works View Composer Linked Clones Parent Virtual Machine vSphere Client Snapshots Desktop Disk Usage
Storage Overcommitment Levels View Pools and Datastores Delta Disks Floating Assignment Linked Clones Dedicated Linked Clone with Persistent and Disposable Disks
View Composer
Uses VMware linked-clone technology to rapidly create desktop images from a parent image. View Composer is installed on a VMware vCenter Server system. master Multiple desktops can be patched by updating the parent image.
Key Concepts
Parent virtual machine/golden master Base image. Snapshot Baseline configuration for the first set of linked-clone desktops. OS disk The operating system disk. Persistent disk An optional separate disk for each user. Disposable disk A optional disk for paging file and Temp-file folder. Thin disk Type of virtual disks that grow on demand. QuickPrep System tool that personalizes desktops. Recompose operation Enables administrators to update an image. Refresh operation Resynchronizes linked clones to the same snapshot. Rebalance operation Redistributes linked clones among datastores.
2010 VMware Inc. All rights reserved
From a single centralized base image a parent virtual machine After the desktops have been created, clones do not have a link to the parent virtual machine.
Will not affect the existing anchored clones. Can be the basis for another linked-clone automated pool.
View Composer permits the Tasks like resetting each system to its default centralized management of configuration, balancing datastore consumption, installing software, and applying service packs desktops while maintaining are greatly accelerated by this type of a seamless user deployment. experience.
linked clone 1
linked clone 2
linked clone 3
linked clone 4
C:
C:
C:
E:\ data
E:\ data
E:\ data
VMDK delta
VMDK delta
Created from a master template, which is left in a pristine state. A snapshot of the parent virtual machine forms the replica. Leaves the parent virtual machine available for other uses.
desktop pool parent virtual machine snapshot protected vCenter Server folder
replica
linked clone
vSphere operation
linked clone
Linked-clone desktops created by View Composer are linked to a replica of a specific vCenter Server snapshot of a parent virtual machine. Using the replica frees the parent virtual machine to be modified for operating system or application patching or updates. After the changes, another snapshot is taken to create another base image. Existing linked clones can then be re-anchored to the new base image. A new desktop pool can also be created from the same parent after the installation of different applications. The new pool can be entitled for use by different user groups.
snapshot
Every new desktop created in a full-clone automated pool, is a clone of a base template.
During linked-clone pool configuration you can define the maximum allowable size of each virtual machine, up to the original size of the parent virtual machine.
View Composer greatly reduces the physical storage overhead of linked-clone desktop pools through the use of delta disks and thinprovisioned user data disks.
In a linked-clone deployment, delta disks are used by the desktop to store the data difference between its own operating system and the operating system of the parent virtual machine.
Administrators can use the storage overcommitment setting to control how aggressively the system assigns new virtual machines to the free space available on the datastore.
Option None Conservative Storage overcommitment level Storage is not overcommitted. 4 times the size of the datastore (default) Free space is used as a buffer. 7 times the size of the datastore 15 times the size of the datastore. Leaves small amount of space for expansion.
Moderate Aggressive
At 95 percent, a log entry is generated. At 99 percent, every virtual machine resident in datastore is halted.
A mechanism for introducing more storage to a datastore to prevent datastore exhaustion. You can retire old storage and make resource pool alterations and host changes.
VMware ThinApp
ThinApp Solution ThinApp Virtualized Application Architecture How ThinApp Works Virtual Machines and Virtual Applications Key ThinApp Features Packaging and Build Process
2010 VMware Inc. All rights reserved
Clientless application virtualization solution. ThinApp does not require any pre-installed client or server software.
ThinApp applications run within the context of a users account and does not require special security rights. The ThinApp runtime redirects all changes intended for the host machines file system and registry to a private, per-user sandbox. ThinApp has an agent-less architecture. ThinApp can run virtually any application from any device. Supporting components can be run side by side. ThinApp ensures security without compromising user flexibility.
virtualized application
runtime
virtual file system / virtual registry
app data
program files
app data
Registry
program files
app data
Registry
operating system
application
registry access
virtual registry native Registry
file access
runtime
sandbox
Virtualize legacy applications on an older Windows platform for deployment to Windows 7. Windows 7 and Windows Server 2008 can be used to capture new applications.
Upgrade ThinApp packages without the need of application project files. Speeds up the upgrade process of existing ThinApp packages.
Full Internet Explorer 6 support ThinDirect plug-in Supports Virtualization of Office 2010 Support for startup services ThinApp Converter
Virtualizes legacy Internet Explorer 6 Web applications on Windows XP and deploy to Windows 7 and Windows 2008 R2. Redirects URLs that are entered in Internet Explorer to a virtualized browser, such as Internet Explorer 6.
Allows for easy packaging and distribution. Accommodates different Office 2010 centralized licensing models. Allows virtualized services to run as natively installed services on system startup.
Silently converts multiple application installers simultaneously into ThinApp packages by using VMware vSphere virtual machines and vSphere API calls.
Step 1
On a clean PC, install an application and capture the results of that application installation into a single executable that is portable.
Step 2
The Setup Capture wizard takes two snapshots: one before and one after installation of the target application.
Step 3
The ThinApp project is created, using the differences between the two snapshots.
Kiosk Mode
Introduction Kiosk Mode and Flexible Authentication Overview of Configuring Clients for Kiosk Mode
A client in kiosk mode is a thin client or a lockdown PC that runs View Client to connect to a View Connection Server instance and launch a remote session. Self-service kiosks can be used in many different situations, such as healthcare, hospitality, and education.
MAC: 00-32-00-40-22-ca
VM1
Best Practice: Kiosk mode allows you to identify and authenticate an endpoint Use dedicated Connection instances handle clients in kiosk using a MAC View address so that Server it can access a to desktop. mode, and to create dedicated organizational units and groups in Active Directory for the accounts of these clients. Users that access kiosks should secure their physical network to prevent unauthorized devices from masquerading as a known kiosk client.
Configure Active Directory to accept the accounts that you create to authenticate client devices. Whenever you create a group, you must also entitle that group to the desktop pool that a client accesses. Prepare the desktop pool that the clients use. Best Practice: Create a separate organizational unit and group to help minimize your work in administering clients in kiosk mode.
Option
Prepare Active Directory for Clients in Kiosk Mode Set Default Values for Clients in Kiosk Mode Display the MAC Addresses of Client Devices
Action
C:\Program Files\VMware\VMware View\Client\bin\wswc printEnvironmentInfo
Windows
Linux
Example 1: Add an account for a client specified by its MAC address to the MYORG domain, using the default settings for the group kc-grp. Prepare vdmadmin -Q Set -clientauth MYORG -clientid Display-add -domain Add Active Default the MAC Accounts 00:10:db:ee:76:80 Directory Values for -group kc-grp
Addresses for Clients for Clients Clients in of Client in Kiosk in Kiosk 2: Add Kiosk Example an account for a client specified by its MAC address to the MYORG Devices Mode Mode Mode
domain, using an automatically generated password. vdmadmin -Q -clientauth -add -domain MYORG -clientid 00:10:db:ee:76:80 -group kc-grp
Example 3: Add an account for a named client, and specify a password to be used with the client. vdmadmin -Q -clientauth -add -domain MYORG -clientid CustomTerminal21 -password "guest" -ou"OU=kiosk-ou,DC=myorg,DC=com" description "Terminal 21"
Example 1: Enable authentication of clients for the View Connection Server instance csvr-2. Prepare Set Enable Clients with automatically generated passwords can authenticate themselves without Display Add Active Default Authentifithe MAC Accounts providing Directory a password. Values for cation of Addresses for Clients vdmadmin -Q -enable -s csvr-2 for Clients Clients in Clients in of Client in Kiosk Example 2: Enable authentication of clients for the View Connection Server instance csvr-3, and require that the clients specify their passwords to View Client. Clients with automatically generated passwords cannot authenticate themselves. vdmadmin -Q -enable -s csvr-3 -requirepassword
in Kiosk Mode Kiosk Mode Devices Mode Kiosk Mode.
Client Authentication User List =============================== GUID 1: 94be6344-0c9b-4a92-8d54-1brc1c2dc282 2 3 4 ClientID : cm-00_0c_29_0d_a3_e6 Domain : myorg.com Password Generated: true Prepare Set Display Add Active Default GUID : 471d9d35-68b2-40ee-b693-56a7d92b2e25 the MAC Accounts Directory Values for ClientID : cm-00_22_19_12_6d_cf Addresses for Clients for Clients Clients in Domain : myorg.com of Client in Kiosk in Kiosk Kiosk Mode Password Generated: false Devices Mode Mode Client Authentication Connection Servers Client Authentication Connection Servers ======================================== Common Name : CONSVR1 Client Authentication Enabled : false Password Required : false Common Name : CONSVR2 Client Authentication Enabled : true Password Required : false
Virtual Printing
Virtual Printing Introduction Benefits How it Works
Utilizes the ThinPrint virtualized printer driver, included in the View Client
Plug-and-play solution
application
rendering
printer
Automatically discovers, connects, and prints from a virtual desktop to any local or network printer defined on the client. Universal print drivers provided, so no compatibility issues with nonstandard print devices. Includes compression to deliver high-quality printing with enhanced performance even over suboptimal networks.
Module Summary
Module 2: Introduction to VMware View learning objectives: Diagram the View architecture. Discuss the key benefits and features of View. List common View use cases. List and explain the View components.