ILT ViewTechExpress 02IntrotoVMwareView VV4.5 v1.0

Module 2: Introduction to VMware View
> 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.
2010 VMware Inc. All rights reserved
What is VMware View?
View Client with Local Mode
The Desktop Dilemma: User Freedom vs. IT Control
User
Anytime, anywhere access Device, OS and apps diversity
IT
Increasing IT costs Security and compliance risks
Virtualization Unlocks Components
Data
Deliver Desktops as a Managed Service
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.
View 4.5 Licensing

Enterprise vSphere, vCenter Server system, and View Manager 4.5. Premier Adds View Composer 2.5, ThinApp 4.6, vShield Endpoint, and View Client with Local Mode. Number of desktop machines that are simultaneously receiving remote connections from client systems.
Enterprise and Premier editions:
Licensed per concurrent user:
Additional licensing required:
Support and subscription services. Guest operating system licensing for desktops.
Key Features
vSphere and VMware Infrastructure 3 integration
Enterprise-class connection brokering
Web-based management user interface
Full Microsoft Active Directory (AD) integration
Support for existing desktops as well as new desktop pools
Advanced pool management features
Flexible deployment options
Support for USB client devices
Ability to cluster many connection brokers for high availability and redundancy
Support for RSA SecurID and smart card authentication
View User Types
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 across all applications Remote office
How Customers Use VMware View
Business Continuity and Disaster Recovery
Desktops as a Secure, Managed Service
Remote or Branch Offices
Provide a continuous availability of desktops. Ensure highly available desktop. Provide a costeffective, simpler, and more reliable disaster recovery solution.
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.
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 Manager Components Overview

View Manager
View Administrator Web interface Automated desktop provisioning/decommissioning Secure connections to desktops Desktop pools that can grow on demand Desktop session timeouts
View Composer
Storage-saving linked clones Rapid desktop deployment Quick update/patch management Tiered storage options
View User Interface
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.

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 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.,
Windows View Client
Windows View Client with Local Mode
Mac View Client
Thin Client
Microsoft Active Directory
View Transfer Server
View Administrator ThinApp View Connection Server
Non-vCenter Server
Physical PCs
VMware vCenter Server with View Composer

Blade PCs Terminal Servers
ESX/ESXi hosts running on Virtual Desktop virtual machines
View Manager Components

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. 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 analytical activities. 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. 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 Connection Server View Manager Security Server View Manager Transfer Server View Administrator Interface
View Agent
View Composer
View Manager User Interface Components
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.
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 for smart 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 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
VMware View Manager
Highly Efficient Encoding for Desktop Display
PCoIP applies the right imaging codec to the right pixels.
icons
motion video
text photos
graphics
PCoIP Progressive Build
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
Using Smart Cards
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 use smart cards:
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 into a smart card reader.
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.
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 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.
To use offline smart card authentication:
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 virtual desktops to a printer that is closest to the endpoint device.
Floor 3
Floor 2
Floor 1

Introduction Benefits and Features Setting Up a View with Local Mode Desktop Deployment
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 Client with Local Mode Benefits
Capability
Robust Transfer Infrastructure Centralized Data Control Improved Security
Disaster Recovery
Infrastructure Cost Savings Latest Runtime Platform
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 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.
How View Composer Works

View Composer service These components create linked-clone virtual interacts with vCenter desktops. Server service through configurations set in a View Connection Server. Storage requirements are minimized, as compared with a full-clone virtual machine.
Uses a read-from-base-disk and write-todelta-disk technology. Much faster provisioning time for a desktop, usually within a few minutes.
Multiple desktops are cloned and deployed:
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.
How View Composer Works (continued)

The first time desktop clones are created, a identified copy of the parent virtual The link to the parent virtual uniquely machine a replica is also created. machine is indirect. Desktop clones are anchored to the replicas system disk, not to the parent virtual machine.
Parent virtual machine can be updated or replaced:
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.
View Composer Linked Clones
linked clone 1
linked clone 2
linked clone 3
linked clone 4
C:
C:
C:
delta disks C: E:\ data System disk:

Reads are from base disk. Writes are to delta disks.
E:\ data
E:\ data
E:\ data
base system disk from replica

VMware View Composer
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-clone virtual 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.
VMDK delta
original system disk (VMDK)
VMDK delta
VMDK delta
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.
desktop pool parent virtual machine snapshot protected vCenter Server folder
replica
linked clone
vSphere operation
linked clone
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
Desktop Disk Usage

The initial disk usage of a linked-clone virtual machine is far lower than that of a full clone because the operating system and client applications are derived from a parent virtual machine.
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.
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 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
Storage Overcommitment Setting
View Pools and Datastores

View automated pools can use multiple datastores to support hundreds of virtual desktops in a single pool:
This capability is provided to allow View desktop pools to use multiple storage datastores, resulting in support for hundreds of desktop virtual machines in a single logical View Manager pool.
The ESX and ESXi host monitors datastore consumption:
At 95 percent, a log entry is generated. At 99 percent, every virtual machine resident in datastore is halted.
View Composer Rebalance feature
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
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 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.
Benefits of Virtualizing Applications with ThinApp
virtualized application
runtime
virtual file system / virtual registry
app data
application virtualization layer
sandbox (runtime) virtual application changes
program files
app data
Registry
program files
app data
Registry
operating system
How ThinApp Works

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. Windows operating system
ThinApp compressed container (EXE)
application
registry access
virtual registry native Registry
file access
virtual file system
native file system
runtime
sandbox
ThinApp Key Features

You can deploy, entitle, and manage ThinApp applications from View Administrator. ThinApp MSI packages can be assigned to individual desktops or pools in View Administrator to allow for streamlined application deployments.
Compatible with VMware View 4.5
Full Windows 7 support
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.
ThinApp relink.exe utility
Upgrade ThinApp packages without the need of application project files. Speeds up the upgrade process of existing ThinApp packages.
ThinApp Key Features (continued)
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.
Packaging and Building Process
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
Kiosk Mode Introduction
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.
Kiosk Mode and Flexible Authentication

00-32-00-40-22-ca 00-32-00-55-21-a0 00-32-00-af-32-bb VM1 VM2 VM3 00-32-00-40-22-ca 00-32-00-55-21-a0 00-32-00-af-32-bb
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.
Overview of Configuring Clients for Kiosk Mode
Prepare Active Directory for Clients in Kiosk Mode
Set Default Values for Clients in Kiosk Mode
Display the MAC Addresses of Client Devices
Add Accounts for Clients in Kiosk Mode
Enable Authentification of Clients in Kiosk Mode.
Verify the Configuration of Clients in Kiosk Mode.
Connect to Desktops from Clients in Kiosk Mode.
Step 1: Prepare Active Director for Clients in Kiosk Mode
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.
Step 2: Set Default Values for Clients in Kiosk Mode
Set Default Values for Clients in Kiosk Mode
Step 3: Display the MAC Addresses of Client Devices
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
vmware-view -printEnvironmentInfo -s <connection_server>
Step 4: Add Accounts for Clients in Kiosk Mode
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"
Step 5: Enable Authentication of Clients in Kiosk Mode
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.
Step 6: Verify the Configuration of Clients in Kiosk Mode

Example:
C:\ vdmadmin -Q -clientauth -list
vdmadmin -Q -clientauth -list [-b <authentication_arguments>] [-xml] 5 6
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
Enable Authentification of Clients in Kiosk Mode.
Verify the Configuration of Clients in Kiosk Mode.
Overview of Configuring Clients for Kiosk Mode

Example 1: Run View Client on a Windows client whose account name is based on its MAC address, and which has an automatically generated password. C:\Program Files\VMware\VMware View\Client\bin\wswc 1 2 3 consvr2.myorg.com 4 5 6 -unattended -serverURL Example 2: Prepare Enable Run View ClientSet on a Linux client using an assigned name andVerify the Display Add Active Default AuthentifiConfigurapassword. the MAC Accounts
Directory Values for cation of tion of Addresses for Clients for Clients Clients in Clients in Clients in of Client in Kiosk vmware-view -unattended -s 145.124.24.100 --once -u in Kiosk Kiosk Kiosk Kiosk Devices Mode Mode Mode Mode. Mode. Custom-Terminal21 -p "Secret1!"
Connect to Desktops from Clients in Kiosk Mode.
Virtual Printing

Virtual Printing Introduction Benefits How it Works
Virtual Printing Introduction
Driver-free printing from virtual desktops
Utilizes the ThinPrint virtualized printer driver, included in the View Client
Plug-and-play solution
What Is Virtual Printing?

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 with Virtual Printing component
Client with Virtual Printing component, connected to print resources
Virtual Printing Benefits
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.

ILT ViewTechExpress 02IntrotoVMwareView VV4.5 v1.0

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ILT ViewTechExpress 02IntrotoVMwareView VV4.5 v1.0

Diunggah oleh

Hak Cipta:

Format Tersedia

Module 2: Introduction to VMware View

2010 VMware Inc. All rights reserved

What is VMware View?

View Client with Local Mode

2010 VMware Inc. All rights reserved

The Desktop Dilemma: User Freedom vs. IT Control

2010 VMware Inc. All rights reserved

Virtualization Unlocks Components

2010 VMware Inc. All rights reserved

Deliver Desktops as a Managed Service

2010 VMware Inc. All rights reserved

View Client with Local Mode

2010 VMware Inc. All rights reserved

View 4.5 Licensing

Enterprise and Premier editions:

Licensed per concurrent user:

Additional licensing required:

2010 VMware Inc. All rights reserved

Enterprise-class connection brokering

Web-based management user interface

Full Microsoft Active Directory (AD) integration

Support for existing desktops as well as new desktop pools

Advanced pool management features

Flexible deployment options

Support for USB client devices

Support for RSA SecurID and smart card authentication

2010 VMware Inc. All rights reserved

View User Types

Static desktop Repetitive tasks Few applications

Personalized desktop Rich user experience Multiple applications

2010 VMware Inc. All rights reserved

How Customers Use VMware View

Business Continuity and Disaster Recovery

Desktops as a Secure, Managed Service

Remote or Branch Offices

Eliminate the need for moves, adds, or changes.

Allow third parties to access corporate applications in secure, controlled way.

2010 VMware Inc. All rights reserved

View Manager Components Overview

View User Interface

View Client with Local Mode

2010 VMware Inc. All rights reserved

View Manager Concepts and Components

2010 VMware Inc. All rights reserved

View Manager Introduction

Windows View Client

Windows View Client with Local Mode

Mac View Client

Microsoft Active Directory

View Transfer Server

View Administrator ThinApp View Connection Server

VMware vCenter Server with View Composer

ESX/ESXi hosts running on Virtual Desktop virtual machines

2010 VMware Inc. All rights reserved

View Manager Components

2010 VMware Inc. All rights reserved

View Manager User Interface Components

2010 VMware Inc. All rights reserved

View User Interface

2010 VMware Inc. All rights reserved

Simplified Sign On to Virtual Desktop and Applications

2010 VMware Inc. All rights reserved

PCoIP Display Protocol

VMware View Manager