ILT ViewTechExpress 02IntrotoVMwareView VV4.5 v1.0

7/28/2019 ILT ViewTechExpress 02IntrotoVMwareView VV4.5 v1.0

1/66

2010 VMware Inc. All rights reserved


Module 2:

Introduction to

VMware View

> Architecture

> Key Benefits and

Features

> How Customers Use View

> View Components

ILT_TechExpress_02IntrotoVMwareView_VV4.5_v1.0


2/66


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.


3/66


What is VMware View?

View Client with

Local Mode


4/66


IT

Increasing IT costs

Security and compliance risks

User

Anytime, anywhere access

Device, OS and apps diversity

The Desktop Dilemma: User Freedom vs. IT Control


5/66


Data

Virtualization Unlocks Components


6/66


OS

Apps

Persona

OS

Apps

Persona

OS

Apps

Persona

OS

Profile

Data

Persona Apps

DataOS

Apps

Persona

Deliver Desktops as a Managed Service


7/66


Key Benefits

Creates an individual, personal view

of all of a users applications and

data on any device from anylocation.

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.

View Client with

Local Mode


8/66 2010 VMware Inc. All rights reserved

View 4.5 Licensing

Enterprise andPremier editions:

Licensed perconcurrent user:

Additional licensingrequired:

Enterprise vSphere,vCenter Server system, andView Manager 4.5.

Premier Adds ViewComposer 2.5, ThinApp 4.6,vShield Endpoint, and ViewClient with Local Mode.

Number of desktopmachines that are

simultaneously receivingremote connections fromclient systems.

Support and subscriptionservices.

Guest operating systemlicensing for desktops.



Key Features

vSphere andVMware

Infrastructure 3integration

Enterprise-classconnection brokering

Web-based

management userinterface

Full Microsoft Active

Directory (AD)integration

Support for existingdesktops as well as

new desktop pools

Advanced poolmanagement

features

Flexible deployment

options

Support for USB

client devices

Ability to clustermany connectionbrokers for highavailability and

redundancy

Support for RSASecurID and smartcard authentication



Task

Workers

Knowledge

Workers

Power

Users

Mobile

Workers

Static desktop

Repetitive tasks

Few applications

Personalized

desktop

Rich user

experience

Multiple

applications

Device flexibility

24x7 access

Custom

applications

Install requirements

Best user

experience

across all

applications

Device flexibility

Disconnected

Multiple

applications

Best user

experience acrossall applications

Remote office

View User Types



Business Continuity

and DisasterRecovery

How Customers Use VMware View

Provide a continuous

availability of

desktops.

Ensure highly

available desktop.

Provide a cost-

effective, simpler, and

more reliable disaster

recovery solution.

Desktops as a

Secure, ManagedService

Eliminate the need for

moves, adds, or

changes.

Allow third parties to

access corporate

applications in secure,

controlled way. Expedite integration of

companies in mergers

and acquisition

scenarios.

Remote or

Branch Offices

Provide offshore

developers control

while keeping IP in the

datacenter.

Remove the need of IT

resources at branch.

Manage remotelydesktops centralized at

branch or in corporate

datacenter.



View Manager Components Overview

ThinApp

View Composer Storage-saving linked clones

Rapid desktop deployment Quick update/patch management

Tiered storage options

Application virtualization

View Manager can assignand automatically deployThinApp MSI packages.

View Manager

View User

Interface

View Administrator Web interface

Automated desktop provisioning/decommissioning Secure connections to desktops

Desktop pools that can grow on demand

Desktop session timeouts

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

View Client with Local Mode

Secure, Offline Desktop capability

Virtual Printing

Driver-free printing



View Manager Concepts and

Components View Manager Introduction

View Manager Components



View Manager Introduction

Desktop connection broker maintains

desktop assignment.

View Manager can run on either a physicalor virtual machine.

Uses vCenter Server service to provision

virtual desktops as needed:

Existing desktops (dedicated to auser)

Automated pools Supported desktop operating systems:

Windows XP Windows Vista Windows 7

For DMZ deployments, View Managerprovides a Security Server.

For high availability deployments, Replica

instances of View Connection Server can

be deployed.

View Administrator Web-based interface.,

Windows

View Client

Windows View Client

with Local Mode

Mac

View Client Thin Client

Microsoft

ActiveDirectory

View Transfer

Server

View

Administrator

ThinApp

View

Connection

Server

VMware vCenter

Server with View

Composer

Non-vCenter Server

Physical PCs

Blade

PCs

Terminal

ServersESX/ESXi hosts

running on Virtual

Desktop virtual

machines



View Manager Components

View Connection Server

View Manager Security

Server

View Manager Transfer

Server

A software service that acts as a broker for client connections by

authenticating and then directing incoming remote desktop user requests to

the appropriate virtual desktop, physical desktop, or terminal server.

An optional component that is used when the View Connection Server is

installed in Security Server mode.

A View Transfer Server works with View Connection Server to manage and

streamline data transfers between the datacenter and local mode desktops.

View Administrator

Interface

A Web application that allows View Manager administrators to configure the

View Connection Server, deploy and manage desktops, control user

authentication, initiate and examine system events, and carry out analyticalactivities.

View Agent

A software service that is installed on all guest virtual machines, physical

systems, or terminal servers in order to allow them to be managed by View

Manager. The agent enables features such as RDP connection monitoring,

PCoIP, printing, remote USB support, and single sign on.

View Composer

A software service that is installed on the vCenter Server host system in order

to allow View Manager to rapidly deploy multiple linked clone desktops from a

single centralized base image.



View Client

View Client with Local

Mode

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.

View Portal Web page

The View Portal Web page can be used to download the full View Client

installer for computers with Windows or Mac operating systems.

View Manager User Interface Components



View User Interface Single Sign On to Virtual Desktop and

Applications

View PCoIP Display Protocol

Using Smart Cards

Location-Based Printing



Simplified Sign On to Virtual Desktop and Applications

Single Sign On Authentication

Integrates with Microsoft

Active Directory.

User enters Windows user

name and password.

Access View desktops with

View Client, thin clients and

View Client with Local Mode.

Users are able to use USB

connected biometrics devices

and smart cards.

Single Sign On support forsmart cards with PCoIP.

Tap and Go Support

Integrates with SSO Vendors.

Connection

Server



PCoIP Display Protocol

VMware PCoIP is the preferred and

recommended protocol of choice for

addressing the broadest set of usecases 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

VMware View Manager



photos

motion video

graphics

icons

text

Highly Efficient Encoding for Desktop Display

PCoIP applies the right imaging codec to the right pixels.



PCoIP Progressive Build

1. Initial imageLow BW and latency

Grainy picture

Lossless text

0.20.5 bits/pixel

2. Perceptually

losslessBuilt over a few frames

High quality picture

Lossless text

13 bits/pixel3. Lossless

Built as BW permits

Lossless picture

Lossless text

515 bits/pixel

1 2

3



Using Smart Cards

Smart card authentication is supported

by the Windows-based View Client, and

View Client with Local Mode, and thefull Linux client that OEMs use.

It is not supported by View

Administrator.

Two-factor authentication:

Verifies what the user has (the smartcard).

What the user knows (the PIN). To use smart cards:

Client machines must have smart cardmiddleware and a smart card reader.

To install certificates on smart cards,

you must set up a computer to act as an

enrollment station.



Logging In with a Smart Card

User inserts smart card intoa smart card reader.

User initiates a connectionto the View Connection

Server instance or securityserver, the View ConnectionServer instance or security

server sends a list of trusted

certificate authorities (CAs)to the View Client.

The View Client checks thelist of trusted CAs against

the available usercertificates, selects a

suitable certificate, and then

prompts the user to enter asmart card PIN.

The View Client sends theuser certificate to the View

Connection Server instanceor security server, whichverifies the certificate by

checking the certificate trustand validity period.

Logging In to Local Desktops with Offline Smart Card



Logging In to Local Desktops with Offline Smart Card

Authentication

To use smart cards with local desktops, you

must select a 1024-bit or 2048-bit key sizeduring smart card enrollment.

Certificates with 512-bit keys are not supportedfor local desktops.

To use offline smart card authentication:

Users must use the same authentication methodthat they used to authenticate to View

Connection Server the last time they logged in.



PCoIP Support for Smart Cards

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 virtualdesktops to a printer that is

closest to the endpoint device.

Floor 1

Floor 2

Floor 3


27/66


View Client with Local Mode Introduction

Benefits and Features

Setting Up a View with Local Mode

Desktop Deployment


28/66


View Client with Local Mode Introduction

Check-out virtual desktop to physical

devices.

Administrators can manage these local

View Desktops by setting policies for:

Frequency of backups.

Contact with server.

Access to USB devices.

Permission to check in desktops.

View Manager

View Transfer

Server

View Client

with Local

Mode


29/66


Capability

Robust Transfer Infrastructure

Centralized Data Control

Improved Security

Disaster Recovery

Infrastructure Cost Savings

Latest Runtime Platform

View Client with Local Mode Benefits


30/66


Overview of Setting Up a Local Desktop Deployment

To create and deploy View desktops in local

mode you must:

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 Transfer

Server

View Client

with Local

Mode


31/66


View Composer Storage Overcommitment Levels

View Pools and Datastores

Delta Disks

Floating Assignment Linked Clones

Dedicated Linked Clone with

Persistent and Disposable Disks

Key Concepts

How View Composer Works

View Composer Linked Clones

Parent Virtual Machine

vSphere Client Snapshots

Desktop Disk Usage


32/66


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.

Multiple desktops can be patched by

updating the parent image.

master


33/66


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.

C


34/66


How View Composer Works

These components create linked-clone virtualdesktops.

View Composer serviceinteracts with vCenter

Server service throughconfigurations set in a View

Connection Server.

Uses a read-from-base-disk and write-to-

delta-disk technology. Much faster provisioning time for a desktop,

usually within a few minutes.

Storage requirements areminimized, as comparedwith a full-clone virtual

machine.

From a single centralized base image aparent virtual machine

After the desktops have been created, clonesdo not have a link to the parent virtualmachine.

Multiple desktops arecloned and deployed:

H Vi C W k ( ti d)


35/66


How View Composer Works (continued)

The first time desktop clones are created, auniquely identified copy of the parent virtual

machine a replica is also created. Desktop clones are anchored to the replicas

system disk, not to the parent virtual machine.

The link to the parent virtualmachine is indirect.

Will not affect the existing anchored clones.

Can be the basis for another linked-cloneautomated pool.

Parent virtual machine canbe updated or replaced:

Tasks like resetting each system to its defaultconfiguration, balancing datastore consumption,installing software, and applying service packsare greatly accelerated by this type ofdeployment.

View Composer permits thecentralized management ofdesktops while maintaining

a seamless userexperience.

Vi C Li k d Cl


36/66


View Composer Linked Clones

base system disk from replica

delta

disks

linked clone 1 linked clone 3linked clone 2 linked clone 4

System disk: Reads are from base disk.

Writes are to delta disks.

C: C: C: C:E:\

data

E:\

data

E:\

dataE:\

data

VMware View Composer

Li k d Cl D d th R li


37/66


Linked Clones Depend on the Replica

A snapshot of the parent virtual machine is copied to a replica

virtual machine.

The replica virtual machine is used to create multiple linked-clonevirtual machines.

The linked clones read from the replica base image (normally C:\)

but have their own delta disks that operate as a write cache.

If the replica is deleted, all cloned virtual machines linked to it will

stop functioning.

original

system disk

(VMDK)

VMDK

delta

VMDKdelta

VMDK

delta

P t Vi t l M hi


38/66


Parent Virtual Machine

The virtual machine parent is an essential building block:

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.

parent

virtual

machine

snapshot

linked

clone

linked

clone

replica

desktop

pool

protected

vCenter

Server

folder

vSphere operation

S h Cli t S h t


39/66


vSphere Client Snapshots

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

D kt Di k U


40/66


Desktop Disk Usage

The initial disk usage of alinked-clone virtual machine is

far lower than that of a fullclone because the operating

system and client applicationsare derived from a parent

virtual machine.

Every new desktop createdin a full-clone automatedpool, is a clone of a base

template.

During linked-clone pool

configuration you can definethe maximum allowable size ofeach virtual machine, up to theoriginal size of the parent virtual

machine.

View Composer greatly

reduces the physical storageoverhead of linked-clone

desktop pools through the useof delta disks and thin-

provisioned user data disks.

In a linked-clone deployment,delta disks are used by thedesktop to store the data

difference between its ownoperating system and the

operating system of the parentvirtual machine.

Storage Overcommitment Levels


41/66


Storage Overcommitment Levels

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 Storage overcommitment level

None Storage is not overcommitted.

Conservative 4 times the size of the datastore (default)

Free space is used as a buffer.

Moderate 7 times the size of the datastore

Aggressive 15 times the size of the datastore.

Leaves small amount of space for expansion.

Storage Overcommitment Setting


42/66


Storage Overcommitment Setting



43/66



This capability is provided to allow View desktoppools to use multiple storage datastores,

resulting in support for hundreds of desktopvirtual machines in a single logical ViewManager pool.

View automated pools can

use multiple datastores tosupport hundreds of virtualdesktops in a single pool:

At 95 percent, a log entry is generated.

At 99 percent, every virtual machine residentin datastore is halted.

The ESX and ESXi hostmonitors datastoreconsumption:

A mechanism for introducing more storage toa datastore to prevent datastore exhaustion.

You can retire old storage and make resourcepool alterations and host changes.

View ComposerRebalance feature


44/66


VMware ThinApp ThinApp Solution

ThinApp Virtualized Application

Architecture

How ThinApp Works

Virtual Machines and Virtual

Applications

Key ThinApp Features

Packaging and Build Process

VMware ThinApp Solution


45/66


VMware ThinApp Solution

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 andregistry 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.

Benefits of Virtualizing Applications with ThinApp


46/66


Benefits of Virtualizing Applications with ThinApp

program

filesapp data Registry operating system

virtualizedapplication

application virtualization layer

runtimevirtual file

system /

virtual

registry

app data

Registryapp dataprogram

files

sandbox (runtime)virtual application

changes

How ThinApp Works


47/66


How ThinApp Works

Windows

operating system

ThinApp

compressed container (EXE)

runtime

application

registry access

file access

virtual

registry

virtual

file system

native

Registry

native

file system

sandbox

ThinApp uses a build process to link the application, the virtual

operating system, and an embedded file system and registry

into a single executable file.

ThinApp Key Features


48/66


ThinApp Key Features

You can deploy, entitle, and manage ThinAppapplications from View Administrator.

ThinApp MSI packages can be assigned toindividual desktops or pools in View Administratorto allow for streamlined application deployments.

Compatible with VMwareView 4.5

Virtualize legacy applications on an older Windows

platform for deployment to Windows 7. Windows 7 and Windows Server 2008 can beused to capture new applications.

Full Windows 7 support

Upgrade ThinApp packages without the need of

application project files. Speeds up the upgrade process of existing

ThinApp packages.

ThinApp relink.exeutility

ThinApp Key Features (continued)


49/66


ThinApp Key Features (continued)

Virtualizes legacy Internet Explorer 6 Web applications onWindows XP and deploy to Windows 7 and Windows2008 R2.

Full Internet Explorer

6 support Redirects URLs that are entered in Internet Explorer to a

virtualized browser, such as Internet Explorer 6.ThinDirect plug-in

Allows for easy packaging and distribution.Accommodates different Office 2010 centralized licensing

models.Supports Virtualization

of Office 2010

Allows virtualized services to run as natively installedservices on system startup.

Support for startup

services Silently converts multiple application installers

simultaneously into ThinApp packages by using VMwarevSphere virtual machines and vSphere API calls.

ThinApp Converter

Packaging and Building Process


50/66


Packaging and Building Process

On a clean PC,install an

application and

capture theresults of thatapplication

installation into asingle executablethat is portable.

Step1

The SetupCapture wizard

takes twosnapshots: onebefore and oneafter installation

of the targetapplication.

Step2

The ThinAppproject is

created, usingthe differences

between the twosnapshots.

Step3


51/66


Kiosk Mode Introduction

Kiosk Mode and Flexible Authentication

Overview of Configuring Clients for

Kiosk Mode



52/66



A client in kiosk mode is a thin client or a lock-

down PC that runs View Client to connect to a

View Connection Server instance and launch aremote session.

Self-service kiosks can be used in many

different situations, such as healthcare,

hospitality, and education.



53/66



MAC:

00-32-00-40-22-ca

00-32-00-40-22-ca

00-32-00-55-21-a0

00-32-00-af-32-bb

00-32-00-40-22-ca

00-32-00-55-21-a0

00-32-00-af-32-bb

VM1

VM2

VM3

VM1

Kiosk mode allows you to identify and authenticate an endpoint

using a MAC address so that it can access a desktop.

Best Practice:

Use dedicated View Connection Server instances to handle clients in kioskmode, 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.

Overview of Configuring Clients for Kiosk Mode


54/66


Overview of Configuring Clients for Kiosk Mode

PrepareActive

Directoryfor Clientsin KioskMode

SetDefault

Values forClients in

KioskMode

Display

the MACAddressesof ClientDevices

Add

Accountsfor Clientsin KioskMode

EnableAuthentifi-

cation ofClients in

KioskMode.

Verify theConfigura-

tion ofClients in

KioskMode.

Connect toDesktops

fromClients in

KioskMode.

1 2 3 4 5 6 7


55/66

Step 2: Set Default Values for Clients in Kiosk Mode


56/66


Step 2: Set Default Values for Clients in Kiosk Mode

PrepareActive


SetDefault


KioskMode

1 2

Step 3: Display the MAC Addresses of Client Devices


57/66


Step 3: Display the MAC Addresses of Client Devices

PrepareActive


SetDefault


KioskMode

Display


1 2 3

Option Action

Windows C:\Program

Files\VMware\VMwareView\Client\bin\wswc -printEnvironmentInfo

Linux vmware-view --printEnvironmentInfo -s

Step 4: Add Accounts for Clients in Kiosk Mode


58/66


p

PrepareActive


SetDefault


KioskMode

Display


Add


1 2 3 4

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.vdmadmin -Q -clientauth -add -domain MYORG -clientid

00:10:db:ee:76:80 -group kc-grp

Example 2:Add an account for a client specified by its MAC address to the MYORG

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 usedwith the client.vdmadmin -Q -clientauth -add -domain MYORG -clientid Custom-

Terminal21 -password "guest" -ou"OU=kiosk-ou,DC=myorg,DC=com" -

description "Terminal 21"

Step 5: Enable Authentication of Clients in Kiosk Mode


59/66


p

PrepareActive


SetDefault


KioskMode

Display


Add


EnableAuthentifi-

cation ofClients in

KioskMode.

1 2 3 4 5

Example 1:

Enable authentication of clients for the View Connection Server instance csvr-2.

Clients with automatically generated passwords can authenticate themselves without

providing a password.vdmadmin -Q -enable -s csvr-2

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


60/66


61/66


62/66


Virtual Printing Virtual Printing Introduction

Benefits

How it Works


63/66

What Is Virtual Printing?


64/66


Virtual printing uses a client-server architecture:

Consists of a server component on the virtual desktop and a client

component on the View Client.

application rendering printer

Virtual desktop withVirtual Printing

component

Client with Virtual Printingcomponent, connected to

print resources

Virtual Printing Benefits


65/66


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 withnonstandard print devices.

Includes compression to deliver high-quality printing with enhanced

performance even over suboptimal networks.

Module Summary


66/66

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.

Date post:	03-Apr-2018
Category:	Documents
Upload:	ryan-belicov
View:	213 times
Download:	0 times

ILT ViewTechExpress 02IntrotoVMwareView VV4.5 v1.0

Documents