Specifications
Table Of Contents
- View Manager Administration Guide
- Contents
- About This Book
- Introduction
- Installation
- View Administrator
- Virtual Desktop Deployment
- Client Management
- Installing and Running View Client and View Portal
- Client Connections from the Internet
- Creating SSL Server Certificates
- Using Existing SSL Certificates
- Smart Card Authentication
- RSA SecurID Authentication
- View Client Command Line Options
- Virtual Printing
- Adobe Flash Bandwidth Reduction
- Client Computer Information
- Using PCoIP Display Protocol
- Using HP RGS Display Protocol
- View Composer
- Overview of View Composer
- Preparing vCenter Server for View Composer
- Preparing a Parent VM
- Deploying Linked Clone Desktops from View Manager
- Refreshing, Recomposing, and Rebalancing Linked Clone Desktops
- Using an Existing View Composer Database
- Using the SviConfig Tool for View Composer
- Offline Desktop
- Component Policies
- Unified Access
- Troubleshooting
- Appendix: The locked.properties File
- Glossary
- Index
VMware, Inc. 129
Chapter 6 View Composer
ViewManageradministratorscansimultaneouslyupdate(orchange)theoperating
systemsofalllinkedclonedesktops,installorupdateclientapplications,ormodifythe
desktophardwaresettingsbycarryingouttheseactivitiesontheParentVMandthen
anchoringthelinkedclonestoanewsnapshotofthisconfiguration.Thisaction
iscalled
desktoprecomposition.
Administratorscanalsoreturntheoperatingsystemdataofeachlinkedclone
desktop—whichmayhaveexpandedthroughongoingusage—toitsoriginalstate
(that oftheParentVM)bycarryingoutanactioncalleddesktoprefresh.
InFigure 6‐1thedesktopuserdataisconfiguredtoresideona
separatedisk,soit
remainsunaffectedbydesktoprecompositionordesktoprefreshactions.Inthisway,
systemmodificationisdecoupledfromuserdatastorage.
ViewAdministratordeliversahigh‐leveloverviewofwhatactionsarebeingcarried
out.Policiescancontrolwhatactionsareexecutedandatwhattimeinorder
to
minimizedisruptiontotheuserbase.Connecteduserscanbenotifiedwithcustom
messagesifanupdatethatwillaffecttheirsessionisabouttotakeplace.
Linked Clone Desktop Disk Usage
Theinitialdiskusageofalinkedclonevirtualmachineisfarlowerthanthatofafull
clonebecausetheoperatingsystemandclientapplicationsarederivedfroma
Parent VM.Thegreatlyreducedstorageoverheadforoperatingsystemanduserdata
isaccomplishedthroughtheuseofdeltadisksand
thinprovisioning.
Everynewdesktopcreatedinastandard(non‐linkedclone)automatedpoolisa
duplicateofabasetemplate.Consequently,eachstandardcloneusesthesameamount
ofdiskspaceasthebasetemplatebecausetheoperatingsystemdataanduserdataof
thebasetemplateisreplicatedby
everyclonecreatedinthepool.
ViewComposergreatlyreducesthephysicalstorageoverheadoflinkedclonedesktop
poolsthroughuseofdeltadisks:abstractstoragemechanismswhoselogicalsizecanbe
greaterthantheirphysicalsize.Thindiskgrowthdependsonfactorsincluding
workload,power‐offpolicy,andpooltype.
Inalinkedclonedeployment,deltadisksareusedbythedesktoptostorethedata
differencebetweenitsownoperatingsystemandtheoperatingsystemofthe
Parent VMfromwhichitisderived.Immediatelyafterdeployment,thedifference
betweentheParentVMandeachofitslinkedclonesisextremely
small;therefore,the
deltadiskisalsoextremelysmall.
NOTELinkedclonescanalsobeanchoredtoanewsnapshotofacompletelydifferent
ParentVM.