VMware View 5: Building a Successful Virtual Desktop

VMware View 5: Building a Successful Virtual Desktop
VMware View 5
VMware Press is the official publisher of VMware books and training materials, which
provide guidance on the critical topics facing today’s technology professionals and
students. Enterprises, as well as small- and medium-sized organizations, adopt virtualization as a more agile way of scaling IT to meet business needs. VMware Press provides
proven, technically accurate information that will help them meet their goals for customizing, building, and maintaining their virtual environment.
With books, certification, study guides, video training, and learning tools produced by
world-class architects and IT experts, VMware Press helps IT professionals master a
diverse range of topics on virtualization and cloud computing and is the official source of
reference materials for preparing for the VMware Certified Professional Examination.
VMware Press is also pleased to have localization partners that can publish its products
into more than 42 languages, including, but not limited to, Chinese (Simplified), Chinese
(Traditional), French, German, Greek, Hindi, Japanese, Korean, Polish, Russian, and
For more information about VMware Press, please visit
+),(!0!ƫ(%/0ƫ+"ƫ,.+ 10/ƫƫđƫƫ+ /0/ƫƫđƫƫ.0%(!/ƫƫđƫƫ!3/(!00!./
VMware® Press is a publishing alliance between Pearson and VMware,
and is the official publisher of VMware books and training materials
that provide guidance for the critical topics facing today’s technology
professionals and students.
With books, certification and study guides, video training, and learning
tools produced by world-class architects and IT experts, VMware Press
helps IT professionals master a diverse range of topics on virtualization
and cloud computing, and is the official source of reference materials
for completing the VMware certification exams.
Make sure to connect with us!
This page intentionally left blank
VMware View 5
Paul O’Doherty
Upper Saddle River, NJ • Boston • Indianapolis • San Francisco
New York • Toronto • Montreal • London • Munich • Paris • Madrid
Capetown • Sydney • Tokyo • Singapore • Mexico City
Copyright © 2013 VMware, Inc.
Erik Ullanderson
Published by Pearson Education, Inc.
Publishing as VMware Press
David Dusthimer
All rights reserved. Printed in the United States of America. This publication is
protected by copyright, and permission must be obtained from the publisher prior
to any prohibited reproduction, storage in a retrieval system, or transmission in any
form or by any means, electronic, mechanical, photocopying, recording, or likewise.
To obtain permission to use material from this work, please submit a written request
to Pearson Education, Inc., Permissions Department, One Lake Street, Upper
Saddle River, New Jersey 07458, or you may fax your request to (201) 236-3290.
Joan Murray
Ellie Bru
Sandra Schroeder
All terms mentioned in this book that are known to be trademarks or service marks
have been appropriately capitalized. The publisher cannot attest to the accuracy of
this information. Use of a term in this book should not be regarded as affecting the
validity of any trademark or service mark.
Chuck Hutchinson
VMware terms are trademarks or registered trademarks of VMware in the United
States, other countries, or both.
Brad Herriman
Warning and Disclaimer
Every effort has been made to make this book as complete and as accurate as possible, but no warranty or fitness is implied. The information provided is on an “as
is” basis. The authors, VMware Press, VMware and the publisher shall have neither
liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained in this book or from the use of the CD
or programs accompanying it.
Vanessa Evans
The opinions expressed in this book belong to the author and are not necessarily
those of VMware.
Corporate and Government Sales
VMware Press offers excellent discounts on this book when ordered in quantity for
bulk purchases or special sales, which may include electronic versions and/or custom covers and content particular to your business, training goals, marketing focus,
and branding interests. For more information, please contact U.S. Corporate and
Government Sales, (800) 382-3419, [email protected] For sales outside
the United States, please contact International Sales, [email protected]
Library of Congress Cataloging-in-Publication data is on file.
ISBN-13: 978-0-321-82234-5
First printing November 2012
Deborah Williams
Gary Adair
Mary Sudul
I would like to dedicate this book to my wonderful wife, Heather, for her
patience and support. I also want to thank my two beautiful girls,
Briar and Hannah, who have managed to give Daddy time to write.
This page intentionally left blank
Preface xv
Acknowledgments xix
About the Author
Virtual Desktop Infrastructure Overview
The Evolution of the Virtual Desktop 1
Where Did It All Start?
The Importance of Application Virtualization
The Importance of User Data Management
The Importance of Multimedia
Considerations for Deploying VDI 11
Thin Clients
Test Failure Scenarios
Engage the Users
Planning for VMware View
Summary 31
VMware View Architecture
Virtual 33
Infrastructure Introduction
VMware vSphere 5 Architecture 39
VMware vSphere 5 40
VMware ESXi
vCenter Server
Storage 50
VMware View Architecture 50
Load Balancing 51
Active Directory
Summary 67
VMware View 5 Implementation
Preparing a vCenter Installation
Installing Microsoft SQL Server
Full Backup 82
Differential 89
Log Backups
Installing vCenter 90
Installing vSphere
Auto Deploy 102
Host Profiles 112
Storage Connectivity
Installing VMware View 116
Configuring the View Connection Server
Adding vCenter Server
Configuring the Transfer Server
Adding the Transfer Server
Adding the Image Repository
Publishing Virtual Machine for Offline Mode 129
The Event Database 129
Persona Management 132
Security Servers 133
Firewall Rules 135
Adding the Security Servers
Application Virtualization
Why Virtualize Applications?
Setting Up the ThinApp Packaging Environment 141
ThinApp Packages and Microsoft Activation
Creating a Package 157
Deploying a Package Through View 168
Building Your Virtual Desktop
P2V or Clean Build?
Manually Installing Windows 7 175
Manually Installing the VMware View Agent
Installing Windows 7 Through VMware Workstation 181
Installing an Image Through vCenter 186
General Optimizations
Operating System Optimizations
Manually Installing Windows 2008 RDS Server 199
Making a Terminal Server Look Like a Desktop 199
View Persona Management 202
View Persona Management: A New Approach 209
Completing the Cycle of Persona Management
6 View Operations and Management 211
Managing a VMware View Environment
Using View Folders 212
Types of Desktop Pools 214
Automated Desktop Pools 215
Manual Desktop Pools 215
Microsoft Terminal Services Desktop Pool 215
Creating Desktop Pools 216
SysPrep or QuickPrep?
Power Options 225
Pool Settings 228
View Composer Settings 234
View Composer Disks
vCenter Settings
Provisioning Settings
View Composer 242
Recompose 248
Managing Persistent Disks 251
Managing Applications 254
Updating ThinApp Packages
About Relink
Inplace Upgrades
SandBox Merge
Using AppSync 261
Summary 266
VMware vShield EndPoint 267
VMware vShield EndPoint 267
High-Level Architecture
vSphere Update Manager 271
Creating the 32-Bit ODBC Connection
Installing Update Manager 277
Configuring Update Manager 284
Patching Your Environment 293
Adding the vShield Manager to the vSphere Environment 300
Adding the vShield Driver to Your VMs 307
Plugging In Your Third-Party Solution 308
Integrating vShield and Trend Micro Deep Security 315
A Rich End-User Experience 331
How Do You Deliver a Rich End-User Experience? 332
Enhancements in PCoIP
Building a Performance Test Environment 336
Installing and Configuring WANem
Installing and Configuring WireShark
Tuning PCoIP
Tuning Parameters 351
Further Analysis
PCoIP Bandwidth Utilization 361
PCoIP Bandwidth Rate Limiting 362
PCoIP Connection Quality
PCoIP Packet Counts 363
PCoIP Connection Latency 364
Encoding Graphs 364
The Impact of Load or IOPS
Setting Up VMware ViewPlanner
Setting Up the Client Desktop 371
Offline Desktops
Why Deliver an Offline Desktop? 373
Best Practices
Migrating from Older Versions of View
Upgrading to New Versions of View
Upgrading Example
High Availability Considerations
Making Your View Environment Resilient
Storage Heartbeats
Configuring iSCSI Multipathing
VMware FT
vCenter Heartbeat 431
Installing VMware vCenter Server Heartbeat 432
Configuring VMware vCenter Server Heartbeat 438
Testing VMware vCenter Server Heartbeat 441
Other Services and Considerations
High Availability Scenario
Deploying a Microsoft Cluster on vSphere 448
Creating a Microsoft Windows 2008 R2 Cluster 449
Connecting the Windows Cluster to the SAN 451
Using MCS
Configuring MCS
Using MPIO
Configuring MPIO 458
Preparing the Volumes
Installing the Microsoft Cluster 466
Configuring the Cluster 468
Adding File Services and the Distributed File System 470
Distributed File System
Installing and Configuring DFS
Setting Up Windows NLB 477
Updating Cisco Switches to Support NLB 478
Performance and Monitoring
Establishing a Performance Baseline 481
Installing vCenter Operations 482
Create an IP Pool 484
Deploy vCenter Operations 487
Configure vCenter Operations 488
License vCenter Operations
This page intentionally left blank
The first edition of VMware View 5: Building a Successful Virtual Desktop is the first book
from VMware Press to cover virtual desktop computing.
About This Book
VMware View 5 is a truly enterprise class virtual desktop product that has integrated all
the necessary technology, such as View Persona and Local Mode desktops, to deliver a
complete solution for delivering desktops. When we set out to write this book, there was
very little available that provided a single source and reference for all the pieces. Although
there is a wealth of information on all the individual components provided online by
VMware and independent bloggers, it was difficult to find the information all in one
place. Our approach was to take the most important topics and bring them together under
one cover. As we go to publication, there are a number of items that we would like to
have included, such as VMware’s Project Horizon, which has been released as VMware’s
Horizon Application Manager.
Products like Horizon attempt to bridge between the PC and Post-PC era. With the
aggressive trend toward Cloud, HTML5, and pure application delivery, opinions vary
on any long-term trend toward desktop virtualization. The reality is, though, that the
virtualization of the desktop is important for many reasons. As IT professionals, we are
very familiar with the concept of a desktop PC. The technologies and lifecycle processes
for desktop management have been around almost as long as the desktop itself. What we
are less comfortable with is running IT as a Service. This is the transformation that is
being driven by the promise of Cloud computing. In preparing for this paradigm shift,
the virtualization of your desktops becomes a necessity. It allows IT departments to move
closer to the IT as a Service model using a form factor that they are comfortable with: the
desktop. This book is designed to get you moving down the path comfortably. We have
taken a very operational viewpoint and looked at not just the deployment but also what is
required to ensure success.
Some of the points we make are not necessarily about the VMware View software but the
importance of your approach. From our experience, one of the most important considerations is the engagement of the end users in the process in a structured way. This comes
back to thinking about the service of delivering desktops versus the mechanics. As you are
designing a service to meet the requirements of your end users, it stands to reason that
involving them in the process provides an opportunity to “market test” before opening up
the service to everyone.
It is our hope in providing this book, we will have simplified some of the challenges and
taken some of the mystery out of how the technology works.
In Chapter 5, “Building Your Virtual Desktop,” we initially developed two versions of the
chapter: the first based purely on what was capable using VMware tools, and a second based
on using a more generic tool, the Microsoft Deployment Toolkit (MDT). Given the series
and audience, we decided to include the one on VMware tools in the final print version.
However, if you are interested in the MDT version, it is available via Safari Books Online.
There is a coupon code in the back of the book that provides free limited access (45 days) to
the book and the additional chapter.
On a more general note, in this book, we use the terms View desktop, virtual desktop, and
desktop instance interchangeably. These terms refer to the deployment of a Windows
desktop OS deployed in a virtual machine, running on VMware vSphere and managed by
VMware View.
What This Book Covers
Here is a quick overview of all the topics covered in this book:
Chapter 1, “Virtual Desktop Infrastructure Overview”
In this chapter we cover the grassroots of desktop virtualization and how it evolved
to become a key technology today. We delve into all the components of a virtual
desktop environment in a general way so you understand their value and where they
fit into your planning. We also review licensing and the underlying infrastructure at
a high level.
Chapter 2, “VMware View Architecture”
From the more general topics in Chapter 1, we delve into the specific architecture of
VMware View 5. In addition, we cover key aspects of the supporting vSphere virtual
infrastructure and how they add value to a virtual desktop environment. We also
look carefully at network and storage because problems in these layers can quickly
translate to performance issues in your virtual desktop environment.
Chapter 3, “VMware View 5 Implementation”
In this chapter we go through the steps required to set up the virtual infrastructure
and add VMware View software. This is the step-by-step guide to installing
and configuring your VMware View environment properly. We also cover the
integration of View Persona.
Chapter 4, “Application Virtualization”
In Chapter 4 we discuss the benefits of application virtualization and then the
specifics of ThinApp. We discuss how to properly set up, package, and manage
the process in your VMware View environment. Originally, I had considered
changing the order of Chapters 4 and 5 because we are four chapters into the book
and have not yet talked about building a virtual desktop or desktop template. In
my experience, however, I find that ThinApp is often not considered carefully in
many View environments. By ordering the chapters this way, I am hoping that you
consider the capabilities and benefits at an earlier stage so that you can get the most
out of this technology.
Chapter 5, “Building Your Virtual Desktop”
In Chapter 5 we discuss the building of the virtual desktop and tuning it properly.
We have incorporated a shared server desktop as a component of this chapter.
This was actually debated by the technical team quite a bit because the integration
of Windows 2008 R2 RDS is an underused feature of the View platform. It does
provide a real opportunity for cost savings if you can meet the requirements of a user
segment using this versus a full-featured desktop, so we considered it important to
include. We review all the steps required to make this appear as seamless as possible.
Chapter 6, “View Operations and Management”
Many books do a good job of explaining software installation. To add additional
value, we thought it was important to talk about the long-term management of
things like ThinApp packages. We also wanted to spend some time reviewing the
features of pools and how pools are applied to user segments and translated to
functional requirements, which can be a challenge in large environments.
Chapter 7, “VMware vShield EndPoint”
Antivirus software can be a challenge in a virtual desktop environment if you take a
traditional approach involving distributing agents to all endpoints. The solution is
integrated in VMware View as vShield EndPoint but often not well understood to
enable you to take advantage of it. In Chapter 7 we step through how it works and
then use a sample installation so that you are comfortable with the implementation
and configuration.
Chapter 8, “A Rich End-User Experience”
How do you ensure that the end-user experience is good, and more importantly, how
do you qualify and quantify it in a controlled manner before you deploy the solution
in production? We review the many improvements in PCoIP and additional parameters you can tune in Chapter 8. We then look at a number of tools to enable you to
simulate different conditions and quantify the effect it has on the PCoIP protocol.
Chapter 9, “Offline Desktops”
Offline desktops allow you to deliver View desktops in a variety of different situations. To do so, you must understand the requirements and how to control them
through policy. In Chapter 9 we review the benefits, go through the configuration,
and discuss the policies required to manage offline desktops.
Chapter 10, “Migrating from Older Versions of View”
In Chapter 10 we look at a scenario that allows us to go through the migration
process from start to finish. We provide detailed steps on how to ensure the components are properly backed up before the migration and the steps required finish it
Chapter 11, “High Availability Considerations”
To provide a production VMware View environment, you must make sure that you
have considered all the single points of failure. In Chapter 11 we start looking at
multipathing from the ESXi hosts all the way up to clustering and site-to-site replication using native technologies. We examine a real-world scenario and go through
the step-by-step process to configuring the environment to provide HA within a site
and to extend that to a second site.
Chapter 12, “Performance and Monitoring”
In Chapter 12 we review the importance of monitoring the VMware View
environment. We go through all the steps to integrate vCenter Operations Manager
with the recently released VMware View Adapter. We review all the information
that is provided by integrating vCenter Operations. We also discuss how you can
turn up the Alerting feature of vCenter Operations Manager to ensure that the
environment is being actively managed.
Author Disclaimer
All steps in this book have been reviewed to ensure they are accurate; however, because
we are dealing with software, they may change from release to release. Although every
precaution has been taken in the preparation of this book, the contributors and author
assume no responsibility for errors or omissions. Neither is any liability assumed for
damages resulting from the use of the information contained herein.
I appreciate your buying this book and hope this helps ensure that your VMware View
environments can scale to meet the needs of your users.
Featured in Safari Edition
In the version of Chapter 5 only available in the Safari Online version, the integration of
Windows 2008 R2 RDS is covered as a component of the complete build process. If you
don’t have a subscriptions to Safari, you can access this version free for 45 days. See the ad
in the back of the book for more details.
Anyone who undertakes the writing of a book knows that your ability to deliver
is largely determined by the quality of your supporting team. I consider myself
extremely lucky to have had the privilege of working with my team. From the
initial acceptance of the project by Joan Murray, the Editor/Program Manager with
Pearson, and her support throughout the process, and the tireless efforts of Eleanor
“Ellie” Bru, my primary technical editor, I am deeply grateful.
I also had great support from my two technical content reviewers: Stephane Asselin
and Shawn Tooley. Stephane was a direct contributor to Chapter 5 and offered his
expertise in all matters related to VMware View. Stephane is a leading expert in
VMware View working with VMware. Shawn Tooley is a published author himself,
and his suggestions greatly contributed to the polish of this book. I also want to
thank Seth Kerney, who worked hard to put this book together.
About the Author
Paul O’Doherty is a Cloud Solution Manager at Onx.com, specializing in the architecture and delivery of cloud-based services. Prior to that, Paul spent 10 years as the
Managing Principal Consultant at Gibraltar Solutions architecting and delivering
end-user computer and virtualization environments in Fortune 500 companies involving
VMware, VMware View, Citrix XenApp, and XenDesktop technologies. Paul has a broad
range of infrastructure experience and has achieved numerous industry certifications such
as VCP, CCEA, MCITP, RCSP, and is recognized as a VMware vExpert. In addition,
Paul maintains a blog at http://virtualguru.org and has contributed to sites such as http://
virtualization.info and is reoccurring speaker at VMUG sessions and other technical
About the Technical Reviewers
Stephane Asselin, with his 20 years of experience in IT, is a Senior Consultant for
the Global Center of Excellence (CoE) for the End-User Computing business unit at
VMware. In his recent role, he had national responsibility for Canada for EUC planning,
designing, and implementing virtual infrastructure solutions, and all processes involved.
At VMware, Stephane has worked on EUC pre-sales activities, internal IP, product
development, and as technical specialist lead on BETA programs. He has also done work
as a Subject Matter Expert for projects Octopus, Horizon, View, vCOPs and ThinApp.
Previously, he was with CA as Senior Systems Engineer, where he has worked on Enterprise Monitoring pre-sales activities and as technical specialist. As a Senior Consultant at
Microsoft, he was responsible for the planning, design, and implementation of Microsoft
solutions within major provincial and federal governments, financial, education, and
telco. In his current role in the CoE at VMware, he’s one of the resources developing
presentation materials and technical documentation for training and knowledge transfer
to customers and peer systems engineers. Stephane also contributed content to this book.
Shawn Tooley is a Senior Virtualization/Cloud Architect and VMware, Citrix, and
Microsoft Virtualization Subject Matter Expert at IBM, with more than 20 years of
experience in information technology. As a Senior Architect with IBM, he takes pride
and enjoyment in bringing solutions to real-world problems by first understanding the
customer’s problem and then designing an effective solution. Shawn is also an author
and blogs at http://www.shawntooley.com. Shawn’s certifications include Microsoft
Certified Trainer—Information Systems, Microsoft Certified Systems Engineer,
MCITP, VMware Sales Professional, VMware Technical Sales Professional, Citrix
Certified Enterprise Administrator, Citrix Certified Sales Professional, HP ASE, IBM
XSeries Server Specialist, CompTIA A+, and CompTIA Certified Trainer, among many
others. In his free time, he enjoys spending time with his family and playing golf. Shawn
dedicates his work on this book to his wife Heather, for supporting and understanding
the long hours being away from home to do what I love—and also, to their newborn son
Gavin Tooley.
We Want to Hear from You!
As the reader of this book, you are our most important critic and commentator. We value
your opinion and want to know what we’re doing right, what we could do better, what
areas you’d like to see us publish in, and any other words of wisdom you’re willing to pass
our way.
As an associate publisher for Pearson, I welcome your comments. You can email or write
me directly to let me know what you did or didn’t like about this book—as well as what
we can do to make our books better.
Please note that I cannot help you with technical problems related to the topic of this book. We do
have a User Services group, however, where I will forward specifi c technical questions related to
the book.
When you write, please be sure to include this book’s title and author as well as your
name, email address, and phone number. I will carefully review your comments and share
them with the author and editors who worked on the book.
Email: [email protected]
David Dusthimer
Associate Publisher
800 East 96th Street
Indianapolis, IN 46240 USA
Reader Services
Visit our website at www.informit.com/title/9780321822345 and register this book for
convenient access to any updates, downloads, or errata that might be available for this
Chapter 3
VMware View 5 Implementation
This chapter describes how to get the components of vSphere up and running. First,
however, you need to install vCenter. Let’s run through the installation of vCenter,
starting from the configuration of the database.
Preparing a vCenter Installation
vCenter supports several different types of databases. The supported databases and
versions are
IBM DB2 Express, Workgroup, and Enterprise (versions 9.5–9.7.2, both 32- and 64-bit
Microsoft SQL Server 2008 Standard, Express, Enterprise, and Datacenter Editions
(versions R2, SP1 and SP2, both 32- and 64-bit editions)
Microsoft SQL Server 2005 Standard, Enterprise, and Datacenter Editions (versions
running SP4, both 32- and 64-bit editions).
Oracle 10g Standard, Standard ONE, and Enterprise Editions (versions, both 32and 64-bit editions)
Oracle 11g Standard, Enterprise Edition (Release 1 and 2, and versions and
VMware generally recommends that you use Microsoft SQL 2008 Express for smaller
environments because it has a fixed limit on how large the database can grow. Although
VMware View 5 Implementation
this limit used to be fixed at 4 GB, it is now fixed at 10 GB. VMware recommends that
SQL Express be used in environments of no more than 5 hosts with 50 virtual machines.
The following steps assume you are deploying Microsoft SQL 2008 R2. vCenter 5 is a
64-bit operating system and so requires Windows 2008 R2. This section is by no means
comprehensive, so you should check the content against your own internal SQL best
practices. You can deploy vCenter as a VM or as a physical server or Linux virtual appliance.
Deploying vCenter as a VM used to be a heated topic, but doing so has now become
common practice and is also a VMware best practice. What can be problematic is having
vCenter as part of the environment it is managing or in the virtual cluster. This is why
VMware recommends a separate management cluster in large environments. These
problems can be mitigated by ensuring you have built redundancy into the vCenter Server
configuration. VMware’s best practice is to run Fault Tolerance (FT), which provides a
constant mirrored copy of the virtual machine so that if the primary fails, the secondary
takes over with no interruption. VMware refers to this technology as virtual lockstep or
vLockstep. VMware FT does have some scaling limitations, however, which may not make
it ideally suited for large environments. For example, VMware FT is limited to a single
vCPU, so it does not support symmetric multiprocessing (SMP). Future releases will
support up to four vCPUs. If you require a multiprocessor server or intend to deploy
vCenter as a physical machine, vCenter Heartbeat is the recommended solution; it is
discussed in Chapter 11, “High Availability Considerations.” vCenter Heartbeat keeps two
vCenter Servers in sync but provides more flexibility on the physical or virtual configuration of the server, such as the number of processors. If you mirror or cluster the SQL
database, you do have a few other options for protecting the vCenter server:
You can schedule physical-to-virtual (P2V) migrations of the vCenter server. You
can schedule a P2V to create a virtual hot spare in the event you have a problem with
the physical vCenter server.
You can schedule a one-time P2V which is similar to the previous method only is
not reoccurring. You can convert the vCenter after it is configured and leave it as a
powered-off cold standby VM.
You can run SQL database locally within the vCenter VM and use VM FT as
VMware actually recommends using a standalone Microsoft SQL Server 2008 R2 cluster
with redundant SAN and LAN connections in large scalable environments. The SQL
cluster should have dedicated logical unit numbers (LUNs) based storage volumes on the
SAN to offload the IO from the VMware cluster versus using datastore-based VMDKs.
This option also ensures that the metadata is available outside the VMware cluster if you
have a failure.
Preparing a vCenter Installation
Although this chapter is not an extensive guide to vSphere 5 deployment, it is important
that you configure your underlying installation properly. It also is important to ensure you
have a production-grade deployment, which means proper configuration and backup.
To install vCenter, you need database services. In most cases, a separate database is
recommended. For smaller environments, however, it is possible to use a copy of
Microsoft SQL Server 2008 R2 Express. vCenter Server supports IBM DB2, Oracle,
and Microsoft SQL Server databases. Be aware that Update Manager supports only Oracle
and Microsoft SQL Server databases.
The minimum hardware requirements are as defined in Table 3.1.
Table 3.1 Minimum Hardware Requirements for Installing vCenter
Intel or AMD x86 processor with two or more logical
cores, each with a speed of at least 2 GHz. The Intel
Itanium (IA64) processor is not supported. Processor
requirements might be higher if the database runs on
the same machine.
4 GB RAM. RAM requirements may be higher
if your database runs on the same machine.
VMware VirtualCenter Management WebServices
requires 512 Mb to 4.4 GB of additional memory.
The maximum WebServices JVM memory can be
specified during the installation depending on the
inventory size.
Disk storage
4 GB. Disk requirements may be higher if the
vCenter Server database runs on the same machine.
In vCenter Server 5.0, the default size for vCenter
Server logs is 450 MB, which is larger than in
vCenter Server 4.x. Make sure the disk space
allotted to the log folder is sufficient for this increase.
Microsoft SQL Server 2008 R2
Express disk requirements
Up to 2 GB free disk space to decompress the
installation archive. Approximately 1.5 GB of these
files are deleted after the installation is complete.
1 Gbit connection recommended.1
based on VMware’s vCenter best practice Knowledge Base article at http://kb.vmware.
vCenter Server 5.0 is a 64-bit application, so it requires a 64-bit Windows operating
system. The following platforms are supported for vCenter Server 5.0:
VMware View 5 Implementation
Microsoft Windows Server 2003 Standard, Enterprise, or Datacenter SP2 (required)
Microsoft Windows Server 2003 Standard, Enterprise, or Datacenter R2 SP2
(required) 64-bit2
Microsoft Windows Server 2008 Standard, Enterprise, or Datacenter SP2 64-bit
Microsoft Windows Server 2008 Standard, Enterprise, or Datacenter R2 64-bit
Because Microsoft SQL Server is the most common platform selected, the following
sample installation is based on vCenter Server 5.0 running on SQL Server. Before
deploying your vCenter Server database instances, you should follow a few Microsoft
SQL best practices. Microsoft recommends that you use separate accounts for all the SQL
services. By default, the installer creates a virtual account, which is a local account on the
server that a Windows user cannot use to log in to a Windows server. The default installation creates all services with a virtual account except for the SQL Server Browser, which
is a local service account, and the SQL Server VSS Writer, which is a local system account.
Unlike in prior releases of SQL in which you needed to assign permissions, now the setup
takes care of assigning the appropriate permissions for you. However, you can still create
the accounts manually, as shown in Figure 3.1. In most cases, the default accounts suffice;
however, if you are deploying a cluster, the following need to be domain accounts:
Database Engine Account
SQL Server Agent
The SQL Server Analysis Service account
Figure 3.1 shows the manual creation of specific service accounts.
Figure 3.1 Manually creating SQL service accounts.
Although it is dated, Microsoft provides a guide called “Services and Service Accounts
Security Planning Guide.” This guide provides general best practices about securing
understand the impact of SP2, see http://technet.microsoft.com/en-us/windowserver/
Installing Microsoft SQL Server
service accounts and can be downloaded from http://technet.microsoft.com/en-us/library/
In addition, you need to install the Microsoft .NET Framework. The installation detects
if you have not done so and enables the feature for you. If you are installing VMware
Update Manager and vCenter Server on the same 64-bit host, keep in mind that vCenter
is a true 64-bit application and requires a 64-bit Data Source Name (DSN) file, and
Update Manager is a 32-bit application that requires a 32-bit DSN. To create a 32-bit data
source, you need to run the 32-bit version of the tool, which you can find at C:\Windows\
SysWOW64\odbcad32.exe. To locate the 64-bit data source tool, go to the Start menu,
Administrative Tools, and then click Data Sources.
Installing Microsoft SQL Server
Follow these steps to install Microsoft SQL Server:
Launch the installation. Click OK to have the SQL Server 2008 R2 setup enable the
Microsoft .NET Framework, as shown in Figure 3.2.
Figure 3.2 Run the Microsoft SQL Server 2008 R2 Setup.
Select New Installation or Add Features to an Existing Installation, as shown in
Figure 3.3.
VMware View 5 Implementation
Figure 3.3 Select New Installation.
After the installer verifies that your server meets the requirements (see Figure 3.4),
click OK.
Figure 3.4 The Installer verifies the prerequisites.
Installing Microsoft SQL Server
Accept the licensing terms, as shown in Figure 3.5, and click Next. Click the check
box if you want to help Microsoft further develop SQL by sending usage data. In
most production environments, this option is not selected.
Figure 3.5 License terms.
Select the SQL features. The only features you need are the Database Engine
Services and the Management Tools, as shown in Figure 3.6. After selecting the
features, click Next.
It is quite common to run into a deployment in which the SQL Server instance is
already up and running, but the management tool has not been installed. Because
the 2008 Management Tools are no longer available as a separate download, it is
possible to use SQL Express Management Studio 2005. An even better solution
is to have a ThinApp version of SQL Express Management Studio 2005 as part
of your toolkit.
VMware View 5 Implementation
Figure 3.6 Select Database Engine Services and Management Tools.
Set the SQL named instance (see Figure 3.7). Although using the default instance is
fine, it is better if you provide a specific instance name and then click Next.
Figure 3.7 Name the SQL Instance.
Installing Microsoft SQL Server
Specify the SQL administrators (see Figure 3.8). After adding the appropriate SQL
administrators, select Data Directories. Select Mixed Mode (SQL Server authentication and Windows authentication) if you intend to run all databases from one
location. Although the vCenter database uses Windows authentication, the Event
Database does not.
Figure 3.8 Select Mixed Mode.
Update the default locations for the databases and logs, as shown in Figure 3.9.
Even if you are running the Windows Database Server as a VM, it is a good idea to
separate the database and the logs on separate partitions. Separating the database and
logs on separate partitions ensures that you can still manage the SQL Server in the
event you run out of capacity on the volumes. If the SQL Server is virtual, you can
separate different Virtual Machine Disks (VMDKs) on different storage tiers to more
finely control IO.
VMware View 5 Implementation
Figure 3.9 Separate the database logs from the OS partition.
After the SQL instance is installed, it is important to ensure your SQL databases are
backed up properly. Microsoft SQL 2008 makes this process easy to configure. Of course,
there are other third-party solutions that back up not only your database instances but also
everything else in your environment. SQL supports a Simple or Full recovery model. A
Simple recovery model does not back up the logs, so recovery is limited to the last backup.
A Full recovery model includes the logs, so it allows you to recover the database to a
certain point in time, assuming the log is not damaged.
For a VMware vCenter environment, you have a vCenter database, an Update Manager
database (which is optional but highly recommended), and also with VMware View, a
View Composer and Events database. We discuss View Composer more in Chapter 6,
“View Operations and Management.” Make sure that you create the database and also
provide the permissions necessary for connecting to the SQL database. The account
requires db_owner permissions to the vCenter and Update Manager database for the
installation. In addition, the account requires temporary db_owner permissions to the
MSDB System database for both vCenter and Update Manager. The purpose is to ensure
the installation can create SQL Agent jobs for the vCenter statistic rollups, for example.
The vCenter statistic rollup jobs allow vCenter to purge data it is collecting to populate
the performance data within vCenter. The tables used to store this data are as follows:
VPX_HIST_STAT1—Stores integral values at the lowest level of granularity (daily
Installing Microsoft SQL Server
VPX_HIST_STAT2—Weekly Stats Rollup Job, which repeats every 30 minutes,
performing rollups at a weekly level.
VPX_HIST_STAT3—Monthly Stats Rollup Job, which repeats once every two
hours, performing rollups at a monthly level
VPX_HIST_STAT4—Yearly Stats Rollup Job, which repeats twice a day,
performing rollups at a yearly level.
It is best to install vCenter and configure the VMware Update Manager before revoking
the db_owner access to the System databases.
The default installation of SQL assigns a Simple recovery model. A Simple recovery model
means that a point-in-time backup is the only one supported. Data added or changed
between backups may be lost with a Simple recovery model. Changing the type to Full
recovery allows you to restore data up to the point of recovery.
You can change the recovery model by selecting the properties of the database and, on the
Options, changing the recovery model from Simple to Full, as shown in Figure 3.10.
Figure 3.10 Change the recovery model to Full.
Let’s step through the process required to create the database and assign the appropriate permissions; then we will review how to ensure the database is properly backed up.
VMware View 5 Implementation
Create each database by opening the Microsoft SQL Management Studio and taking the
following steps:
Connect to the SQL database instance on the SQL Server.
Right-click the Database Module and select a new database.
Ensure your database names are indicative of what they will be used for—that is,
vCenter, VMware Update Manager (VUM), vComposer, and vEvents.
Expand the Security Module and add a new login.
The account should be the one that you created so that you can connect and perform the
installation. In this case, we created a svc_SQL Account, as shown in Figure 3.11.
Figure 3.11 Choose the account that will be the db_owner.
Ensure the account is mapped to the appropriate database and has the db_owner
permission. To ensure the SQL Agent jobs are created properly, db_owner permission is
also required for the MSDB database. After the installation is complete, this permission
should be revoked.
Figure 3.12 shows the three databases mapped to the db_owner role.
Installing Microsoft SQL Server
Figure 3.12 User mapping.
After you create the databases and have the appropriate permissions, you should
schedule the database backups if an enterprise backup solution is not in place. Although
most server virtualization environments do have enterprise backup solutions in place,
due to the requirement of needing a second virtual server, this is not always the case
in virtual desktop environments. It is recommended that you have a specific backup
solution in place, but at a minimum, you should set up backups. In most cases, a
dedicated SQL support team exists and has a defined backup process. The steps provided
in this book are not meant to supersede established backup practices and policies, but
instead serve as a reference in case an option is needed or if additional understanding is
required on SQL backups.
When you are looking at a backup strategy for your vCenter and your virtual desktops,
you should consider how valuable the data is, how much the data is changing, the overall
size of the database, and how much the data is used. With vCenter, the database is a
configuration database to store metadata. As your environment grows, however, the availability of the data and overall service becomes increasingly critical.
When using SQL Server 2008, you have three primary backup types: full, differential, and
log backups.
VMware View 5 Implementation
Full Backup
A full backup copies all the information in the database. Full backups also include the
transaction logs and any data that has not been written to the database. In a small virtualization environment, it is possible to run full backups for the vCenter database. When the
environment grows beyond 20 ESXi hosts, the database can grow to 10–15 GB. In this
case, a combination of full or differential backups might be necessary.
Open the SQL Server Management Studio and connect to the SQL Server instance.
Navigate to the Server\Databases folder.
Right-click the database you want to back up.
From the shortcut menu, select Tasks, Backup.
In the Database Backup dialog box, select the type of backup you want the server to
perform, the backup destination path, and the backup options.
Click OK to back up the database or click the Script button if you want to generate
a script to run the backup with the selected options.
You can also run backups from the SQL command line by performing the following:
Browse to c:\Program Files\Microsoft SQL Server\100\Tools\Binn.
Run SQLCMD. The 1> prompt tells you that you are connected to SQL Server
instance 1.
Enter the backup command, as shown in Figure 3.13.
The command to do a full backup is BACKUP DATABASE [Name of database]
TO DISK = N’[PATH]’. In this example, we typed
BACKUP DATABASE vCenter TO DISK = N'S:\Backup\vCenter_12282011.bak'
Installing Microsoft SQL Server
Figure 3.13 The BACKUP DATABASE command.
To execute the command, type go and press Enter. The backup should process
successfully, as indicated in Figure 3.14.
Figure 3.14 A successful backup.
To set up reoccurring backups, you need to set up a maintenance plan under SQL and
ensure that SQL Agent is started. If you are running a SQL Express Edition, you need to
look at scheduling a SQLCMD command because maintenance plans are not available in
the Express Edition.
After the SQL Agent starts, you can set the backups to happen according to a schedule. If
you are not using a SQL Express Edition, you should see the Maintenance Plans module
under Management, as shown in Figure 3.15.
VMware View 5 Implementation
Figure 3.15 Maintenance Plans module.
Create a Back Up Database task and set it up according to a reoccurring schedule, as
shown in Figure 3.16.
Figure 3.16 Set a reoccurring schedule.
If you are using SQL Express, you can use the following process to automate the
SQLCMD Backup command. First, you need to create a SQL script using the command
you ran from the command line:
BACKUP DATABASE vCenter TO DISK = N'S:\Backup\vCenter.bak'
The file extension does not matter, but in this case save the database with a .bak extension
so that it is easy to identify. Now you need to create a scheduled task to initiate the
SQLCMD command and execute the SQL script. You also need to create a local ID under
which the scheduled task can run with suitable privileges including the logon as batch job
Installing Microsoft SQL Server
privilege. You can add a policy through the Active Directory (AD) by separating out your
vCenter Server in a separate OU. You should do this through Active Directory policy, but
you can configure this locally by doing the following:
Navigate to Administrative Tools\Local Security Policy.
Expand the Security Settings\Local Policies\User Rights Assignment.
Add the account that will run the scheduled job to the Logon as Batch Job Properties
and click OK.
When you are done, you can open the scheduler to create a basic task.
Open the scheduler on the SQL Express Server and create a basic task. Provide a
descriptive name such as vCenter Backup job and a description of when the job
occurs, as shown in Figure 3.17. Then click Next.
Figure 3.17 Create a Task.
Configure the trigger; in this case, set up the backup job to be triggered weekly (see
Figure 3.18). Then click Next.
VMware View 5 Implementation
Figure 3.18 Configure a trigger (weekly).
Set the frequency you would like the backup to occur at (see Figure 3.19) and click
Next. If you would like the backup to happen every two weeks, you can adjust the
Recur setting from 1 to 2.
Figure 3.19 Determine the schedule and reoccurrence.
Set it to start the SQLCMD command with arguments. To do so, select Start a
Program (see Figure 3.20). Then click Next.
Installing Microsoft SQL Server
Figure 3.20 Select Start a Program.
Select the SQLCMD program and the argument as –i [Path to your SQL script], as
shown in Figure 3.21.
Figure 3.21 Select SQLCMD as the program and your script as the arguments.
After you complete these steps, you need to adjust the properties a little for the job:
Browse to the Task Scheduler Library and verify the reoccurring vCenter Database
job appears in the right pane.
VMware View 5 Implementation
Select the task, right-click, and select the properties of the newly created batch job,
as shown in Figure 3.22.
Figure 3.22 Right-click properties.
Ensure Run Whether the User Is Logged On or Not is selected, as shown in
Figure 3.23. Then select Change User or Group… and ensure the job is running
under the proper credentials.
Figure 3.23 Select the user under which to run the task.
Installing Microsoft SQL Server
The preceding description is just a sample of how you can ensure you have regular full
backups running if you have opted to run SQL Express. You might want to fine-tune
your settings to keep several weeks’ worth of full backups and also to move them to a
separate location.
If your database is getting too big for a full backup, you can perform a differential backup.
A differential backup copies any changes made since the last full backup job. It is designed
to reduce the time needed to perform a full backup. You can make your backup job a
differential job by adding the WITH DIFFERENTIAL statement, as shown in Figure
3.24. In this case, your final backup strategy adds a combination of full and differential
backups, so you must ensure you have access to all the backup files.
Figure 3.24 WITH DIFFERENTIAL command.
Log Backups
The third type of backup does not copy the changes; it copies only the transactional logs
of the database. After the logs are copied, the portions of the log files not needed for active
transactions are truncated. For regular maintenance, it is a good practice to back up your
log files daily.
When you are happy with your scheduled job, you can quickly apply it to the remaining
databases because the jobs are exportable to XML files from the Task Scheduler console.
Simply export the job as an XML file, make some edits so that it can be applied to the other
databases, and reimport it. In general, the VMware Update Manager View Composer or
Event databases do not require the same frequency of backups as the vCenter database.
VMware View 5 Implementation
Installing vCenter
After checking to ensure the database is up and running and your backup rotations and
recovery plans are properly configured, you are almost ready to begin the vCenter installation. Installing vCenter requires a domain account with local administrator privileges. If
you are installing vCenter on a Windows 2008 R2 host, you have some decisions to make:
Should you keep the firewall enabled, and what ports do you need to have open if you do?
It is a best practice to keep the firewall active although it increases the complexity of the
deployment. By keeping it on, however, you are dramatically reducing the attack vector
or vulnerability of the service. This, of course, is both a judgment call and consideration
of your internal security policy toward native Windows firewalls. In some organizations,
the default is to turn off the firewalls. If you do want to keep the firewall on, you should
be aware of which ports are opened during the installation of the vCenter Server. You can
open these ports in advance, or during the installation, they are opened by default.
Table 3.2 provides a list of the ports.
Table 3.2 Port Descriptions
vCenter Server requires port 80 for direct HTTP connections. Port 80 redirects
requests to HTTPS port 443. This redirection is useful if you accidentally use
http://server instead of https://server/.
Note: Microsoft Internet Information Services (IIS) also use port 80.
This port must be open on the local and all remote instances of vCenter Server.
This is the LDAP port number for the Directory Services for the vCenter Server
group. The vCenter Server system needs to bind to port 389, even if you are not
joining this vCenter Server instance to a Linked Mode group. If another service
is running on this port, it might be preferable to remove that service or change
its port to a different port. You can run the LDAP service on any port from 1025
through 65535.
If this instance is serving as the Microsoft Windows Active Directory, change the
port number from 389 to an available port from 1025 through 65535.
This is the default port that the vCenter Server system uses to listen for
connections from the vSphere Client. To enable the vCenter Server system to
receive data from the vSphere Client, open port 443 in the firewall.
The vCenter Server system also uses port 443 to monitor data transfer from SDK
If you use another port number for HTTPS, you must use ip-address:port when
you log in to the vCenter Server system.
Installing vCenter
For vCenter Server Linked Mode, this is the SSL port of the local instance. If
another service is running on this port, it might be preferable to remove that
service or change its port to a different port. You can run the SSL service on any
port from 1025 through 65535.
This is the default port that the vCenter Server system uses to send data to
managed hosts. Managed hosts also send a regular heartbeat over UDP port 902
to the vCenter Server system. This port must not be blocked by firewalls between
the server and the hosts or between hosts.
Port 902 must not be blocked between the vSphere Client and the hosts. The
vSphere Client uses this port to display virtual machine consoles.
Web Services HTTP. This port is used for the VMware VirtualCenter Management
Web Services.
Web Services HTTPS. This port is used for the VMware VirtualCenter Management
Web Services.
Web Service change service notification port.
vCenter Inventory Service HTTPS.
vCenter Inventory Service Service Management.
vCenter Inventory Service Linked Mode Communication.3
After reviewing the port requirements, you are ready to begin installing vCenter. Ensure
you have the latest version of the vCenter 5 software downloaded and follow these steps:3
Launch the installer. You will notice that several services and features can be
installed from the Installation Utility, which we discuss later. To install vCenter,
select the vCenter Server option and click Install.
Select the language from the drop-down; vCenter ships with language support.
When the installation wizard appears, click Next.
After reviewing the end-user patent agreement, click Next.
Agree to the license terms and click Next.
Enter your user name, organization, and license key in the fields provided and click
information was referenced from the VMware Knowledge Base at http://kb.vmware.
VMware View 5 Implementation
You have the option of installing a Microsoft SQL Server 2008 Express instance
or using a supporting database. Because vCenter is a true 64-bit operating system,
it requires a 64-bit DSN. If you have not created one, you are prompted to do so.
Click Next to start the creation of the DSN or select it from the drop-down list and
proceed to step 15. Figure 3.25 assumes you need to create the DSN.
Figure 3.25 Select the database.
Provide a name for the vCenter DSN, provide a description, and then select the
SQL instance you are connecting to (see Figure 3.26).
Figure 3.26 Specify SQL Server information.
Installing vCenter
Click With Integrated Windows Authentication, as shown in Figure 3.27.
Integrated Windows security is more secure than SQL Server authentication, so you
should use it. Click Next.
Figure 3.27 Select With Integrated Windows Authentication.
Ensure you are connecting to the vCenter Server, as shown in Figure 3.28, and click
Figure 3.28 Change the default database.
VMware View 5 Implementation
Click Finish.
Click Test the Data Source…
When the installation completes successfully, as shown in Figure 3.29, click OK.
Figure 3.29 Check your database connectivity.
When you see your DSN in the highlighted area, as shown in Figure 3.30, select it
and click Next.
Figure 3.30 Select your DSN.
Installing vCenter
Click Next.
Accept the default location and click Next.
You have the option of installing vCenter in linked mode so that you can view all
vCenter information from a single management tool. It is common for the vCenter
Server being deployed for the VDI environment to be the second vCenter Server
deployed. If you install it in standalone mode and then want to update it to linked
mode, you can be rerunning the installer. If this is the case, install the server in
linked mode; otherwise, select Create a Standalone VMware vCenter Server
Instance, as shown in Figure 3.31, and click Next.
Figure 3.31 Select the standalone option unless this is the second vCenter Server.
vCenter Server Web services is provided by Tomcat. In this screen, shown in
Figure 3.32, you are asked to tune the maximum memory pools for Java based
on the expected size of the environment. Although this screen was introduced in
vCenter 4.1, the capability to tune Tomcat has been available for a while through the
Configure Tomcat utility that is provided. Select the maximum memory configuration based on the expected size and click Next.
VMware View 5 Implementation
Figure 3.32 Select the appropriate inventory size to configure the Tomcat memory setting.
You have the option of increasing the number of ephemeral ports, as shown in
Figure 3.33. An ephemeral port is a short-lived endpoint created by the Windows
Server when a program makes a user port connection. Because virtual desktop
environments can scale into the thousands of virtual desktop instances, it is typical
that you adjust the ephemeral ports on both VMware View Servers and vCenter
Servers. Click Install to begin the installation.
Figure 3.33 Increase the ephemeral ports for large View environments (thousands of instances) if
needed and install vCenter.
Ensure the installation completes properly (see Figure 3.34) and click Finish.
Installing vCenter
Figure 3.34 Finalize the installation.
When the installation is complete, you need to install the vSphere client to connect to the
environment. The vSphere client is a Windows-based client that allows you to connect to
vCenter and the ESXi hosts in your environment. The difference in connecting to ESXi
versus vCenter is that ESXi uses the local root login credentials, whereas the vCenter
Server uses Windows login credentials. To get access to the vCenter Server you just
installed, complete the following steps:
Launch the vCenter installer.
Select the vSphere Client and click Install.
Select the language for the installation and click OK.
Click Next on the welcome screen.
Click Next on the user patent agreement.
Agree to the license terms and click Next.
Click Install on the ready to install screen.
Click Finish when the installation completes.
Open the vSphere client in Programs\VMware\vSphere Client.
Enter the name of the vCenter Server and the Windows username and password and
click Login.
To summarize the process, the high-level installation steps shown in Figure 3.35 are
necessary to complete the installation.
VMware View 5 Implementation
Figure 3.35 Installation steps.
Installing vSphere
Installing VMware View starts with the installation of vSphere and related components.
With vSphere 5, there are two options for vSphere: installable and embedded. Installable
is an installation of vSphere ESXi because vSphere 5 no longer supports ESX native or
the version that had the console operating system (COS) for management purposes. You
can download the ESXi binaries from VMware at https://my.vmware.com/web/vmware/
try-vmware or order the server with the embedded version.
If you download the binaries, it is possible to create a manual embedded version by
installing to a USB drive in an internal or external port on the server. The embedded
version is supplied by the hardware vendors and incorporates their specific tools to enable
greater visibility on the hardware and software layer. For example, you can download an
ESXi version from HP, Dell, IBM, and CISCO. One of the drawbacks of the embedded
option is that the build from the vendor may not have the latest and greatest utilities or
tools. With vSphere 5, this issue is addressed by providing an automated build option that
allows you to add OEM packs to the installation. Let’s review the installation:
To install ESXi installable, follow these steps:
Boot from the ISO file. After it boots, the splash screen comes up, and the necessary
files to start the installer are loaded, as shown in Figure 3.36.
Installing vSphere
Figure 3.36 ESXi splash screen.
You can maneuver around the installer by using the Tab key. To continue the
installation, press the Tab key and press Enter on the keyboard, as shown in
Figure 3.37.
Figure 3.37 Select Enter to continue.
Press F11 to accept the license agreement shown in Figure 3.38 and continue.
VMware View 5 Implementation
Figure 3.38 Press F11 to accept the license agreement.
Select a disk to install or upgrade, as shown in Figure 3.39. It is considered a best
practice to install vSphere ESXi first before presenting storage so that you can be
assured that you are installing ESXi on the right drive unless you intend to boot
from SAN. Once you have selected the drive press Enter.
Figure 3.39 Select the storage device where you would like to install ESXi.
Select the correct keyboard layout (US Default), as shown in Figure 3.40, and press
Enter to continue.
Installing vSphere
Figure 3.40 Select the keyboard layout.
Specify a password for the root account, as shown in Figure 3.41, and press Enter.
Figure 3.41 Specify the password.
Confirm the parameters, as shown in Figure 3.42, and press F11 to begin the
Figure 3.42 Press F11 to install.
If you are installing ESXi to a USB stick, you need to verify that your server is on the
supported Hardware Compatibility List (HCL) and that the USB device is supported by
the server vendor. If both conditions are met, the USB device shows up as an installable
location. Rather than select a local drive, you can select the USB location to install ESXi.
VMware View 5 Implementation
For detailed instructions, refer to VMware’s Knowledge Base article located at http://
Auto Deploy
One of the other options you have is to use the new Auto Deploy feature, which essentially allows you to provision a vSphere 5 ESXi Server and apply the configurations in an
unattended manner through the Configuration Manager to create a truly stateless host.
Why would you use Auto Deploy in a VDI environment? VDI is a technology that scales
quite quickly. To reduce the time it takes to provision additional capacity, Auto Deploy
may be a good option. In addition, it allows you to design the ESXi configuration once
and have it consistently applied across the board. It does require extra consideration if you
are going to run vCenter in a virtual machine, however.
When you use Auto Deploy, you are creating a major dependency on the service for all
hosts that are set up to use it. You therefore need to run two ESXi hosts that are not
dependent on Auto Deploy in a cluster. A separate cluster ensures that your vCenter and
Auto Deploy Server can reside on a set of hosts that are running vSphere HA with the
boot priority properly set on the VMs so that the service is readily available all the time.
Before we get too far ahead ourselves, though, let’s look at the requirements and process.
To deploy the Auto Deploy feature, you need a few additional components:
PowerShell installed on the vCenter Server
The PowerCLI from VMware
A TFTP Server for downloading the files
The ESXi downloadable files (The files can be downloaded from the VMware
Using the vCenter that you have installed and running, you can add these additional
components to take advantage of rapid provisioning of stateless ESXi hosts in the VDI
The architecture of Auto Deploy is made up of the following components, also shown in
Figure 3.43:
A TFTP Server to store the boot loader files
Attributes in the DHCP scope to identify the TFTP Server and boot loader files
Rules in the vCenter Server Auto Deploy feature to associate a physical ESXi Server
to an image file
A software depo where the ESXi installable files are located
Installing vSphere
Software Depo
plugging in
vCenter Server
Attribute 66 &
TFTP Server
Physical Servers
Figure 3.43 Auto Deploy components.
Let’s enable and step through each of the components.
PowerShell is included in Windows 2008 R2, but you do have to add it as a feature.
PowerShell should be installed on the vCenter Server along with the VMware PowerCLI.
To install PowerShell, follow these steps:
To add PowerShell, open Server Manager.
Browse to the Add Features module and right-click Add Feature.
Select the Windows PowerShell Integrated Scripting Environment.
Click Install.
Open a PowerShell script window, browsing to Start\Programs\Administrative tools
and opening a Windows PowerShell Module.
Enable the PowerCLI by changing the remote execution policy for scripts by typing
Set-ExecutionPolicy RemoteSigned. This allows scripts that are not signed by a
vendor to run on the vCenter Server.
VMware View 5 Implementation
You can download the VMware PowerCLI directly from VMware. After downloading it,
simply follow these steps to install it properly:
Run the VMware Power CLI executable.
Click Next on the Installer screen.
Click Next on the Patent information screen.
Accept the license agreement and click Next.
Accept the default location and click Next.
Click Install.
Click Finish.
You may be prompted to install the VMware VIX files; VMware VIX is an API that allows
you to automate VM and guest operations. You should install VIX when prompted.
To get the boot loader files, you need to install the plug-in in vCenter for Auto Deploy.
You can install the plug-in using the VMware vCenter Installer:
Click the VMware Auto Deploy, as shown in Figure 3.44, and click Install.
Figure 3.44 Select VMware Auto Deploy.
Installing vSphere
Choose the setup Language and click OK.
Click Next on the Auto Deploy Installation Wizard.
Click Next on the patent information screen.
Accept the license agreement and click Next.
Accept the default location and set the Auto Deploy Repository location and size.
The default repository size is 5 GB. Because Auto Deploy is being used to provide
ESXi images, the default size is sufficient.
Enter the IP address or hostname of the server, leave the default HTTP port, and
enter the username and password. Then click Next.
For network-based services, I prefer to go with IP addresses so that name resolution is not
a requirement for the service. If you are likely to change IP addresses, it is best to put in a
The default Auto Deploy Server Port is 6501. Leave this setting and click Next.
Specify how vSphere Auto Deploy should be identified on the network and click
My recommendation is to use the IP address so that name resolution is not
required for the deployment server to run.
Click Install.
Click Finish.
When you reconnect to vCenter, you see a new administration plug-in called Auto Deploy.
Launch the Auto Deploy plug-in, which should look similar to the one in Figure 3.45.
VMware View 5 Implementation
Figure 3.45 Auto Deploy appears under Administration.
The plug-in displays the boot loader filename, which in this case is undionly.kpxe.
vmw-hardwired. The boot loader files can be downloaded from here, as shown in
Figure 3.46.
Figure 3.46 Download bootloader files.
Now that you have the name of the boot loader file and the zip files containing those files,
you can set the attributes for your DHCP scope and unzip the files on your TFTP Server.
The files are downloaded as deploy-tftp.zip. When you unzip them, by default, they are
placed in a subdirectory of your root folder (deploy-tftp) on your TFTP Server. To ensure
you can find the files, unzip them in the root directory of your TFTP Server without the
default subdirectory.
Installing vSphere
It is recommended that you restrict your Auto Deploy process to a service network.
This means that your builds should happen on an isolated network segment separate
from your production network. By doing so, you ensure that even though the building
of an ESXi host involves a very small image file, the downloading and installing do not
interfere with production traffic. In addition, DHCP is required for this process to
work. From a security perspective, DHCP traffic should not be run on the same network
as your ESXi management traffic. If you do not have the flexibility of separating your
management and Auto Deploy service network, use nonroutable IP addresses to build
the hosts and then apply production IPs afterward. A separate Auto Deploy network may
require a dedicated port group on your vSphere ESXi vSwitches, so make sure that you
build this into your planning.
When the boot loader files are in place, update options 66 and 67. In a Windows-based
DHCP Server, follow these steps:
From the DHCP Management Utility, browse to the scope that you will be using to
enable the Auto Deploy process.
Expand the scope and select Options. Then right-click and select Configure
Under Available Options on the General tab, select 066 and add the IP address of
your TFTP host under the string value.
Select 067, and under the string value, add the name of the boot loader file, which in
this case, is undionly.kpxe.vmw-hardwired.
Click OK.
At this point, you should have the boot loader process running. If you boot a physical
server, it gets a DHCP address, contacts the TFTP Server, and downloads the boot loader
file. It connects to the Auto Deploy service on the vCenter Server and halts because no
rules have been configured to tell the server which image profile is assigned to the host.
After downloading the boot loader file, the server contacts the vCenter Server but stops
because the image profile has not been assigned to the host yet, as shown in Figure 3.47.
VMware View 5 Implementation
Figure 3.47 The server contacts vCenter.
To complete the Auto Deploy configuration, you must run some PowerCLI scripts from
the vCenter Server to specify a software depo. Extract the ESXi downloadable images into
the software depo and create a rule to associate the image with an image profile. The final
step is to make this the default image profile.
Log in to your vCenter Server and start the PowerCLI interface. If you get an error
message, it is likely that you have not set the execution policy properly in PowerShell. In
this instance, run PowerShell and set the execution policy, as shown in Figure 3.48:
"Set-ExecutionPolicy RemoteSigned"
This command allows code that has not been signed by a trusted publisher such as
Microsoft to run.
Figure 3.48 Set the execution policy to unsigned.
Installing vSphere
Run vSphere PowerCLI and connect to your vCenter Server by typing ConnectVIServer [servername], which results in the output shown in Figure 3.49.
Figure 3.49 Connect to your vCenter Server.
After you are connected, you need to create a software or repository. You do this by
running the Add-EsxSoftwareDepot command along with the path to your ESXi
downloadable files. For example:
Add-EsxSoftwareDepot S:\Depo\VMware-ESXi-5.0.0-469512-depot.zip
After creating the software depo, you should verify it is set up properly by running the
Get-EsxImageProfile command. The command should return information on the image
profiles available in the software depository, like those shown in Figure 3.50.
Figure 3.50 Image profiles.
VMware View 5 Implementation
Although the initial images are fine for a proof of concept, you need the vSphere HA
modules for production deployment. These modules are part of the Auto Deploy software
depot and can be added by running Add-EsxSoftwareDepot http://vCenter Server/
vSphere-HA-depot. The output is shown in Figure 3.51.
Figure 3.51 Add the software depository URL.
To add the HA options, add the HA software depot on the vCenter Server, as shown in
Figure 3.52.
Figure 3.52 Add HA to your ESXi image.
After adding the HA files, you need to create a copy of the existing images so that you can
add the new files to it. To take one of the existing images and clone it, run the following
PowerCLI> New-EsxImageProfile -CloneProfile ESXi-5.0.0-469512-standard
-Name "ESXi-5.0.0-469512-HA"
In this example, you are taking the ESXi-5.0.0-469512-standard image and copying it to
one called ESXi-5.0.0-469512-HA, shown in Figure 3.53 (Note that the HA components
were not included in the original ESX software depo zip files, but now they are).
Installing vSphere
Figure 3.53 Make a copy of the original image.
If you rerun the Get-EsxImageProfile command, you see an additional image profile. You
still need to add the vmware-fdm or HA package to the image. You do this by running the
following command:
PowerCLI> Add-EsxSoftwarePackage -ImageProfile "ESXi-5.0.0-469512-HA"
-SoftwarePackage vmware-fdm
After verifying that the software depository is working and that you have images available,
you can create a deployment rule. The syntax for creating a deployment rule is
New-Deployment—Name "Name of Rule"—Item "Image Name"
You have the option of pattern matching or making this image file available as the default
by adding switches. The –Allhosts switch applies the rule to any server, and the –pattern
switch allows you to specify specific attributes to match, such as vendor=VMware, Inc.
You can concatenate multiple patterns by separating each with a comma. Perhaps the most
useful of the patterns is specifying an IP range. If you have separated your build network
and use a set range of IP addresses, you can restrict the build process to that range.
The syntax used in this example is as follows (see Figure 3.54):
PowerCLI> New-DeployRule -Name "ESXi Default Build v.01" -Item "ESXi-5.0.0469512-HA" -Pattern "ipv4="
Figure 3.54 Associate the image to an IP pattern.
VMware View 5 Implementation
After creating the build rule, you must activate it. The command to activate it is
Add-DeployRule –DeployRule “Name”, as in this example:
Add-DeployRule –DeployRule "ESXi Default Build v.01"
One point to keep in mind with Auto Deploy is that the deployment can generate a significant load on the Auto Deploy service. Because the location of the image file is essentially
a web server, it is possible to use reverse proxies to offload some of the overhead. A reverse
proxy can also store the image file. It is possible to redistribute the load to the reverse
proxy by editing one of the boot loader files. If you go into the TFTP root directory and
edit a file called tramp, you can specify alternate locations. If you open the tramp file, you
can easily specify alternate locations, as shown in Figure 3.55.
Figure 3.55 Edit the tramp file.
Host Profiles
After you set up Auto Deploy, essentially you have ESXi Servers that are running, but
they do not yet have a production configuration applied to them. The other component to
vCenter that you need to integrate is host profiles.
Host profiles allow you to create a set of configurations that can be consistently applied
across the environment. They eliminate the manual configuration of ESXi hosts on an
individual basis. Host profiles also allow you to force compliancy across your environment
because after a host profile is associated, any changes made are identified and remediated.
Because Auto Deploy essentially creates an installed ESXi, you need to use host profiles
to apply a consistent production configuration. There are two ways to configure a host
Installing vSphere
profile: You can import an existing profile through the vCenter console or create one from
an existing ESXi host. Unless you have a company standard (and this should be adjusted
for a VMware View environment), the easiest way is to just configure an ESXi host as
you would like and create one from the host. A host profile assumes that the EXi hosts
are configured the same way, so it is important to have everything configured properly on
your reference ESXi Server.
Using host profiles is a four-step process:
Create a reference profile from an ESXi host.
Attach the profile to an existing host or cluster.
Run a comparison against the hosts assigned to the profile and the profile itself.
Apply the profile to fix any differences between the assigned hosts and the profile.
The actual process is as follows:
From vCenter, navigate to Home, Management and Host Profiles.
Click the Create Profile button and provide a name and description for the profile,
as shown in Figure 3.56. Then click Next.
Figure 3.56 Create a host profile.
You can edit the profile to make any additional changes. Simply open the profile and
expand the profile policies to update the settings, as shown in Figure 3.57.
VMware View 5 Implementation
Figure 3.57 Expand the profile policies to edit settings.
You can select to attach the profile to an ESXi host or cluster.
After attaching the profile, click Check Compliance.
If anything is noncompliant, click Apply Profile to have the changes made.
At this point, you have deployed vCenter and have the ESXi hosts coming online. Now
make sure that the reference server is properly configured before you build your host
profile. For an ESXi Server, you should ensure that the storage is properly attached and
that key features such as VMotion and DRS are set up and working. Let’s review each of
the technologies and the configuration so that the reference server is representative of
what you want in production.
VMotion allows the virtual machine to be hot migrated from one ESXi host to another.
To set up VMotion properly, you must make sure that any ESXi host you are migrating
to and from has access to the same storage. ESXi supports just about every type of shared
storage configuration out there, whether it is Fiber Channel (FC), iSCSI, or NFS.
VMware View environments are unique in that you have two kinds of I/O to contend
with: operational I/O and burst I/O. Operational I/O is essentially the storage throughput
requirement while the virtual desktop is on, whereas burst I/O, or “boot storms,” is
typically experienced when multiple virtual machines are being created. We look at the
design principles in Chapter 12, “Performance and Monitoring,” when we review performance, but for now let’s talk mechanics. Rather than go into every aspect regarding
Installing vSphere
storage considerations and configurations, let’s stick to a few important considerations in
setting up storage.
No matter which storage solution you select for your VMware View installation, you
should understand and have calculated your throughput requirement. In addition, your
storage connections from the ESXi host to the storage solution should use multipathing.
Multipathing allows you to segregate the storage paths on isolated networks and ensure
there are redundant paths to the same storage pool.
Storage Connectivity
vSphere 5 has simplified the setting up of multipathing using the iSCSI software initiator.
In vSphere 5, a new graphical interface allows you to set up multipathing. You therefore
can set up multiple VMkernel ports quickly and easily. You can now bind multiple
VMkernel ports to the iSCSI software initiator. After you do so, however, the iSCSI traffic
must be restricted to layer 2 traffic or nonroutable. If you use a single VMkernel port, you
can route iSCSI traffic. In addition, if you have both VMkernel ports on the same vSwitch
with two uplinks, one must be active and the other passive. Let’s look at the configuration
to understand how this works.
If you want two active paths to your iSCSI storage device, you need to create two separate
vSwitches with two separate VMkernel ports with one active uplink each. This configuration has a separate management network and two separate paths to the iSCSI appliance,
as you can see in Figure 3.58.
Figure 3.58 Two separate paths to the iSCSI appliance.
VMware View 5 Implementation
When you have the networking configuration in place, you can bind the second VMkernel
port to the software initiator using the following process:
Log in to the vCenter.
Select the Configuration tab from the ESXi host.
Select Storage Adapters and the properties of the software iSCSI initiator.
Under the Network Configuration tab, add the second VMkernel port.
After the second VMkernel port is added, check the paths to ensure you have the appropriate number of paths, as shown in Figure 3.59:
Figure 3.59 Check to ensure you have multiple paths.
Installing VMware View
If you are running VMware View as a virtual machine on Windows 2008 R2, much of the
performance tuning is complete. You should, however, make the following changes to
your VM.
Manually set the pagefile for the system based on 1.5 times the memory assigned to the
VM. You can complete this process using the following steps:
Installing VMware View
Open Server Manager on the VM.
Select Change System Properties.
Select the Advanced tab and settings.
Select the Advanced tab, and under Virtual Memory, select Change.
Select Custom Size and set the minimum and maximum value to 1.5 times the
memory allocated.
Click Set and click OK and OK again.
When prompted, reboot the VM.
The first server you should install is a standard Connection Server. As mentioned, there
are actually four kinds of Connection Servers you can install: View Standard (or the first
Connection Server in the environment), View Replica (or all servers after the initial
Connection Server is installed), Security Server, and Transfer Server for local mode VMs.
To install the first Connection Server, follow these steps:
Launch the VMware View Installer and click Next on the welcome screen.
Click Next on the end user patent agreement.
Accept the license agreement and click Next.
Accept the default location and click Next.
Because this is the first server, select View Standard Server, as shown in Figure
3.60, and click Next.
Figure 3.60 Choose View Standard Server.
VMware View 5 Implementation
Have the installer automatically configure the Windows Firewall and click Next.
Note: The installer does not check the firewall state during the installation; it simply
prompts you to configure it automatically or not to (see Figure 3.61).
Figure 3.61 Adjust the Windows Firewall.
Click Install, as shown in Figure 3.62.
Figure 3.62 Click Install.
Click Finish, as shown in Figure 3.63.
Installing VMware View
Figure 3.63 Click Finish.
The installer installs eight services on the Windows Server:
VMwareVDMDS—Provides the View LDAP directory services.
VMware View Web Component—Provides View Web Services.
VMware View Security Gateway Component—Provides secure tunneling services
for View.
VMware View Script Host—Disabled by default but provides support for third-party
VMware View PCoIP Secure Gateway—Provides secure tunneling for the PC over
IP (PCoIP) protocol.
VMware View Message Bus Component—Provides messaging services between
View components.
VMware View Framework Services—Provides event logging, security, and COM+
framework services for View Manager.
VMware View Connection Server—Provides connection broker services.
After VMware View is installed, you can connect to it by launching the shortcut on the
desktop or by opening a web browser and going to http://[Connection Server]/admin. Be
aware that the admin is case sensitive, and the IP address can be used in place of the server
name, which is not case sensitive. If you omit the /admin, you are redirected to the client
installation page. When you connect to the console for the first time, you are prompted
to install Adobe Flash Player. The Administrator Console requires Adobe Flash version
VMware View 5 Implementation
10 or higher. After you have logged in, you will need to configure the environment so that
everything is running properly.
Configuring the View Connection Server
As mentioned in Chapter 1, “Virtual Desktop Infrastructure Overview,” there are two
versions of VMware View: Enterprise and Premier. Premier includes local mode and View
Composer. If you apply a Premier license, you see View Composer and local mode VMs
as options. After logging in, you need to add the license. Click Edit License, as shown in
Figure 3.64.
Figure 3.64 Add the license.
Enter the VMware View Serial Number in the provided field (see Figure 3.65).
Figure 3.65 Enter the license key.
Configuring the View Connection Server
Premier licenses enable View Composer and local mode, as shown in Figure 3.66.
Figure 3.66 Premier enables View Composer and local mode.
You now have to add vCenter Server, but you should ensure the View Composer service
is running first. View Composer supports both 32-bit and 64-bit versions of SQL and
Oracle. In addition, VMware View 5.1 can be installed on a separate server, or with
vCenter. In View 5.1, View Composer creates a self-signed certificate during installation,
so a certificate exchange is done when configuring View to communicate with View
Composer. It is also a good idea to ensure you can resolve the vCenter hostname from the
Connection Server. You should do a forward-and-reverse lookup using the hostname and
then IP. This can easily be done by running nslookup from the command prompt.
To install View Composer on vCenter, follow these steps:
Click Next on the installation wizard screen.
Click Next on the end user patent agreement.
Accept the license agreement and click Next.
Accept the default path for the installation and click Next.
Type in the name of the ODBC connection you created, as shown in Figure
3.67. You have the option of specifying a username and password. By default, the
connection uses Windows NT integrated security. You should avoid hard-coding a
password and ID because doing so creates a major security weakness.
VMware View 5 Implementation
Figure 3.67 Specify the DSN connection.
Accept the default port and have the installer create an SSL certificate, as shown in
Figure 3.68.
Figure 3.68 SOAP port.
Click Install to install the View Composer service, as shown in Figure 3.69, and click
Finish when it is complete.
Configuring the View Connection Server
Figure 3.69 Click Install.
Adding vCenter Server
You are now ready to add vCenter Server to the View Connection Server. Under View
Configuration and Servers in the right pane, click the Add button to configure your
vCenter Server connection, as shown in Figure 3.70.
Figure 3.70 Add vCenter Server.
Specify the Fully Qualified Domain Name (FQDN) of your vCenter Server and the
VMware View Service Account name created in Chapter 2, “VMware View Architecture.”
Enable View Composer because you have verified that the Composer service is running on
the vCenter Server, as shown in Figure 3.71. It is important for View Composer connectivity that you use the format [Domain\User Name], but the vCenter connectivity accepts
User Name only. For consistency, it is best to use the same format in both.
VMware View 5 Implementation
Figure 3.71 Add vCenter Server.
Click Add under Domains in the View Composer Settings, as shown in Figure 3.71.
Then add the domain information in the Add Domain box, as shown in Figure 3.72. This
enables the management of computer accounts in the Active Directory. Click OK and OK
again to save the configuration.
Figure 3.72 Enter domain information.
You should now see the vCenter Server and your first Connection Server as part of the
configuration, as shown in Figure 3.73.
Configuring the View Connection Server
Figure 3.73 vCenter Server is added.
To ensure reliability, you should install a second View Server. For a PoC, you could use
any one of the methods discussed to ensure a single connection broker such as VMware
FT or vSphere VM HA is highly available. Keep in mind that VMware FT is limited to
a single vCPU at this point in time. VMware recommends that two vCPUs be used for
a View Connection Server, so it would not be suitable for a production deployment. For
production, you want at least two View Servers that use an appliance-based load balancer
such as F5. The process to install the second View Server is identical to the first, except
that the second server is a Replica Server. The second Replica Server points to the first
View Connection Server, as you can see in Figure 3.74.
Figure 3.74 Adding a second View Connection Server.
VMware View 5 Implementation
Configuring the Transfer Server
If you intend to use local mode VMs, you need to set up a Transfer Server and image
repository. After setting up a Transfer Server and repository, you publish a desktop for
offline mode. The publishing process copies the base image into the image repository.
Local mode allows users to check out, check in, roll back, and back up the local mode
VM. When the user checks out a VM, a copy of the base image is copied out of the image
repository on the Transfer Server and placed on the user’s local desktop hard drive. The
virtual desktops are made up of a base image and a delta file. All changes are recorded in
the delta file, and it is this file that is used to facilitate the functionality of the other three
options. When the virtual desktop is checked out, the base and delta files are downloaded
to the user’s desktop and disk files are locked within the vCenter Server so that no changes
can be made to the original source files.
Local mode can be a good option for roaming users who need to get work done both
online and offline. It also is ideal if you have a remote branch with slow access to the
datacenter. Local mode does enable you to copy any changes back the centralized VMware
View environment to ensure that the local VM and locked VM stay in sync.
Checking in synchronizes the delta files stored locally to the one located in the VMware
View environment and then deletes the base image on the local desktop and unlocks the
files within the virtualization environment for use.
Rolling back does not synchronize; it simply deletes both files on the local user drive and
unlocks the files within the virtualization environment for use.
Backing up synchronizes the delta files stored locally and the ones located in the View
environment; however, it does not unlock the centrally stored files because a backup allows
the local mode VM to keep running or remain primary for the user.
The process for setting up the Transfer Server is similar to the installation of the
Connection Server. There are a few things to keep in mind if you are planning on using a
virtual machine as the Transfer Server. Each Transfer Server can handle a maximum of 20
check-in or check-out requests according to VMware (http://pubs.vmware.com/view-50/
index.jsp?topic=/com.vmware.view.installation.doc/GUID-1A3719FC-C75A-4ED9B5D3-70334150BD39.html). After they are added to the View Configuration, they are
disabled from DRS. In addition, the servers are configured with an additional three SCSI
LSI Logic Parallel controllers to allow them to handle more user requests, as shown in
Figure 3.75.
Configuring the View Connection Server
Figure 3.75 Three additional LSI Logic SCSI controllers are added for a total of four.
Although Transfer Servers have to be virtual machines, you cannot use the LSI SAS adapter,
which is the default for Windows Server 2008 R2, because it is unsupported.
If you are deploying the Transfer Server as a new VM, select the LSI Logic adapter, as
shown in Figure 3.76.
VMware View 5 Implementation
Figure 3.76 You must use the LSI Logic adapter.
To install the Transfer Server, follow these instructions
Launch the Connection Server Installer and click Next.
Click Next on the patent agreement screen.
Accept the license agreement and click Next.
Accept the default location and click Next.
Select View Transfer Server and click Next.
On the Transfer Server Configuration screen, provide the name of the domain,
server, and email address of the administrator.
If the firewall is enabled, select Configure Firewall Automatically; otherwise, skip
this step.
Click Install and then Finish.
Adding the Transfer Server
To add a Transfer Server, you must first add the Transfer Server and then add the virtual
machine storage repository as follows:
Log in to the View Connection Server using the View Administrator Console.
Under View Configuration, select Server and select Add Transfer Server.
Configuring the View Connection Server
Ensure your vCenter Server is listed as the source for the Transfer Server and click
The utility queries the inventory of VMs, or you can manually enter the name.
Select your Transfer Server and click Finish.
Adding the Image Repository
After adding the Transfer Server, you need to add an image repository. The image
repository is the place where VMDKs are copied and stored so that they are available for
To add a storage repository, complete the following steps:
Log in to the View Connection Server using the View Administrator Console.
Under Transfer Server Repository, click Edit to add the image repository information. You can specify a repository stored locally on a Transfer Server or on a
centralized file share.
Publishing Virtual Machine for Offline Mode
To publish a VM for offline mode, you need to create a desktop virtual machine and take
a snapshot to create the delta disk. After creating the snapshot, you can publish this virtual
desktop for use as a local mode VM as follows:
Log in to the View Connection Server using the View Administrator Console.
Under Transfer Server Repository and under Content, select Publish.
Select Snapshot Created Off Your Base Image.
The Event Database
The Event Database was introduced in VMware View 4.5 to allow you to store any
event that occurs in the View environment to an external database. Adding an Event
Database is optional but highly recommended. It is difficult to manage the Connection
Server without the Event Database, which can be a key source of information when you
are troubleshooting issues. The database is supported on Microsoft SQL Server or the
Oracle database. You can create an Event Database by first creating the database in SQL
and then configuring the connection within VMware View. With the Event Database,
unlike other database configurations, you don’t need to create an ODBC connection. You
simply add the connection information to View. The Event Database requires local SQL
VMware View 5 Implementation
authentication, so the first step is to create a local SQL account and ensure it has the
appropriate access to the Event Database. You can create a local SQL account using the
following procedure:
Open SQL Management Studio and connect to your database instance.
Open the Security and then the Logins modules.
Right-click Login and select New Login.
Under the General Settings, ensure SQL Server authentication.
Provide a login name such as svc_Events and provide a password. Note: SQL 2008
requires this to be a complex password, so stay away from any dictionary words.
Retype the password to confirm it.
Because this is a service account, deselect the following:
Enforce Password Policy
Enforce Password Expiration
User Must Change Password at the Next Login
Under the default database, select your Event Database, such as vEvents.
Select the User Mapping page.
Select db_owner in addition to the default public access and click OK.
After creating the local SQL account, you can then add the Event Database from the View
Administrator Console. Under View Configuration select Event Configuration.
Provide the name of your database server, the type, and a user ID in the fields shown in
Figure 3.77 to connect. The table prefix ensures that the Event Database can be unique to
this collection of VMware View Servers. If you have another site, both can use the same
database service because the table prefix is unique. You have to provide a prefix, however,
if you have only a single site for VMware View Servers.
Configuring the View Connection Server
Figure 3.77 Add an Event Database.
After you connect the Event Database, you can set the period in which events appear in
the console and the duration in which events are considered new, as shown in Figure 3.78.
After you have the settings configured, click OK.
Figure 3.78 Set the event display options.
VMware View 5 Implementation
Persona Management
Persona Management, which is new to VMware View 5, allows you to deliver,
synchronize, and manage user profiles. Persona Management came from a licensing and
co-development agreement with RTO Software (http://www.vmware.com/company/
news/releases/rto-vmworld09.html). It can be used as a replacement or an enhancement to
Windows profiles. The difference between Persona Management and Windows profiles
is that only the registry information that is required for the user to log in is downloaded,
not the entire profile. As the user opens additional applications, the remaining files are
downloaded. The minimalistic approach to data at the start keeps the user logon process
quick and streamlined. Like Windows profiles, this feature uses a file server or CIFS share
to ensure the user data is centralized. Persona Management also gives you finer control of
the synchronization of data between the local user session and the storage repository. By
default, this happens every 10 minutes but can be adjusted.
Prior to Persona Management, VMware View offered user data disks, which have now
become persistent attached disks. A persistent attached disk is a second VMDK where any
user writes (including the profile) could be stored. The only challenge with a secondary
drive approach is that the information is local and associated with a virtual desktop versus
centrally available. You can now use both of these technologies to essentially provide a
local user cache. You can use the user persistent disk to provide a local user repository for
linked clones or Composer-created View desktops and Persona to make sure the changes
are synced centrally so that they are preserved in case the virtual machine drives are lost.
You should ensure the local Persona persists between logoffs, so do not enable the Remove
Local Persona at Log Off setting in this case. We review this topic more in Chapter 6.
The nice thing about Persona Management is that it applies to both physical and virtual
desktops as of VMware View 5.1. Keep in mind that if you are using shared server-based
desktops (TS Servers), Persona Management is not supported. If you have users accessing
View desktops using Persona Management and Windows roaming profiles on regular
desktops, the best solution prior to 5.1 was to separate them. Now you can use a single
Persona profile. If you are using a combination of Windows and View profiles, the View
desktops can be configured to override an existing Windows profile in the configuration
settings. This ensures that the Windows roaming profiles don’t overwrite Persona profile
settings when the user logs out.
Outside the file server requirement, Persona Management does not require any additional
infrastructure because it can be installed with the View Agent on the virtual or physical
desktop. The configuration of Persona Management is managed through an Active
Directory Administrative template, which can be imported into the OU that you are
deploying the virtual machines to or the local policy settings of the virtual desktop. The
Administrative template is located on the View Connection Server:
Configuring the View Connection Server
To import these policies into the AD, follow these steps:
Open your Group Policy Management Console.
Right-click your View Desktop OU and create or link a GPO policy.
Enter a name such as View Persona Management Policy.
Right-click the new policy and select Edit.
Browse to Administrative Templates and select Add/Remove Templates.
Click Add again, browse to the location on the View Server, and select the ViewPM.
adm template.
Expand Administrative Templates and VMware View Agent Configuration and
Persona Management.
To import these policies into the local user policy, follow these steps:
Open Local Security Policy.
Right-click Administrative Templates and click Add\Remove Templates.
Click Add again, browse to the location on the View Server, and select the ViewPM.
adm template.
Expand Administrative Templates and VMware View Agent Configuration and
Persona Management.
Security Servers
Security Servers are another type of View Server but designed to be deployed to simplify
remote access. Because they are usually deployed in a DMZ situation, they are not
required to be part of the Active Directory. They reduce the number of connections that
are required to be open on the forward-facing firewall of a DMZ (demilitarized zone) and
corporate or internal firewall. Each Security Server is paired with a specific Connection
Server, so if you are load balancing two Security Servers in the DMZ, you require two
View Servers deployed internally.
New in VMware View 5 is the capability to proxy PCoIP. Prior to version 5, only the
Remote Desktop Protocol (RDP) was available through a Security Server. To work,
the connections must be tunneled through the Security Servers. Typically, the Security
Servers are deployed in a DMZ and should be load balanced behind an appliance-based
VMware View 5 Implementation
firewall such as F5, as shown in Figure 3.79. If you are load balancing the Security
Servers, you should not load balance the connectivity from the Security Servers to the
Connection Servers because there is a one-to-one relationship between Security Servers
and Connection Servers.
View Servers
vSphere 5 Environment
Figure 3.79 Security Servers are deployed in the DMZ.
Configuring the View Connection Server
Firewall Rules
To allow the traffic to pass through the external firewall to your Security Server, you should
translate the external IP to the internal IP and ensure the required ports are open using
NAT. You can find a detailed network flow diagram in the View 5 Architecture planning
guide starting on page 61; it is downloadable from http://pubs.vmware.com/view-50/topic/
com.vmware.ICbase/PDF/view-50-architecture-planning.pdf. The following ports need to
be open:
PCoIP traffic between the View Client and Security Server (External)
a. TCP 443 for the website
b. TCP 4172 from Client to Security Server
c. UDP 4172 between client and security server in both directions
To allow the traffic to pass, you must set the following rules on the internal
PCoIP traffic between the View Security Server and Virtual Desktop (Internal)
a. TCP 4172 from Security Server to virtual desktop
b. UDP 4172 from Security Server to virtual desktop in both directions
You must set up several things for the Security Server to work properly. The first consideration is the external URL. If you are going to provide access to a View environment
remotely, you must register a public-facing IP address and register it in DNS. Let’s use
the example of access.virtualguru.org. The DNS name is important because during the
configuration of the Security Server, you configure it to respond to this external URL
versus its own hostname. Although we discuss straight installation in this chapter, it is not
typical that remote access is offered with single-factor authentication. It should always be
combined with a two-factor authentication method such as RSA.
Adding the Security Servers
The first thing you should do is define a pairing password, which you do from the View
Connection Server, not the Security Server.
First, log in to the View Connection Server. Then, under View Connection Servers, select
the More Commands button, as shown in Figure 3.80.
VMware View 5 Implementation
Figure 3.80 Add the Security Server.
Specify the Security Server pairing password, confirm the password and set the password
timeout. You should specify a short amount of time for security reasons and also ensure
that the Security Server pairing is done before the expiry.
Now you can install your Security Server using the following steps:
Launch the Connection Server Installer and click Next.
Click Next on the patent agreement screen.
Accept the license agreement and click Next.
Accept the default location and click Next.
Select View Security Server and click Next.
Provide the IP or hostname of the Connection Server to which this Security Server
will be associated and click Next.
Provide the pairing password you configured in the View Server and click Next.
Specify the external URL that this Security Server should respond to—for example,
access.virtualguru.org—and also the IP address that this DNS name is registered to
for PCoIP connections. Then click Next.
Allow the installer to automatically configure the firewall. I recommend that you
definitely leave the firewall intact when deploying the Security Server Security
Server in the DMZ and click Next.
Click Install and then Finish.
If you are going to tunnel PCoIP, you must tell the View Server paired with the Security
Server to use PCoIP Secure Gateway for PCoIP to desktop. Under the View Server, select
Edit and ensure User PCoIP Secure Gateway for PCoIP Connections to Desktop
is selected. The Use Secure Tunnel Connection to Desktop setting is the default and
should be left as is, as shown in Figure 3.81. The External URL and PCoIP External URL
Configuring the View Connection Server
point to themselves for the internal View Server, which is fine. Only the Security Server
needs to respond to the external IP addresses.
Figure 3.81 Enable the PCoIP Secure Gateway.
After the gateway is properly installed, if you refresh the View Administrator Console
under Security Servers, you should see your server there, as shown in Figure 3.82.
Figure 3.82 View your Security Servers.
If you need to change the External URL or IP for tunneling PCoIP, you can click Edit on
the Security Server.
VMware View 5 Implementation
It is important to ensure each component of the VMware View environment is functioning
properly. Check the Event Viewer on the Windows Server for error messages related to
the installation. In addition, make sure that the services start properly.
At this point, you have all the major infrastructure pieces of the VMware View
environment up and running. You need to create virtual machines and tune them for
optimal performance. Before you do, though, you should look at one other important
piece of the VMware View platform: application virtualization. When you understand
the benefit of application virtualization, you can integrate it into your View desktops. We
discuss application virtualization next in Chapter 4, “Application Virtualization,” and then
put all the pieces together in Chapter 5, “Building Your Virtual Desktop.”
AppSync utility (ThinApp), 261-265
App-V, 7
activating ThinApp packages, 156-157
Active Directory, 53-61
organizational units (OUs), 53
VMware View, 50-51
Active Directory, 53-61
advanced image management, 5, 9
desktop pools, 66
anomalies, monitoring, 494
load balancing, 51-53
antivirus (AV) software. See AV (antivirus)
local-mode VMs, 66-67
application bubbles, 8
application packaging versus application
virtualization, 8
lifecycle management, 6
managing, VMware View, 254
application virtualization, 6-9, 139-141
ThinApp packages, 140, 153
activation, 156-157
creating, 157-168
deploying, 168-171
setting up environment, 141-156
versus application packaging, 8
PCoIP (PC over IP), 62-66
QoS (quality of service), 65-66
vShield EndPoint, 268-271
vSphere 5, 39-40
Auto Deploy, 102-112, 421-422
automated desktop pools, 215
AV (antivirus) software
AV storms, 267
running, 267
adding driver to VMs, 307-308
Deep Security integration,
AV (antivirus) software
vShield EndPoint, 267-268
deploying, 268
high-level architecture, 268-271
Capture utility (ThinApp), 143
module, 271
case profi ling, 8
third-party support, 308-315
CHAP (Challenge Handshake
Authentication Protocol), 453
Update Manager, 271-300
VMSafe integration, 269
vShield Manager, 268
vShield Manager, 300-307
AV storms, 267
CIDR (Classless Inter Domain Routing)
format, 485
Cisco switches, Windows NLB, updating
to, 478-479
Citrix, 2
Classless Inter Domain Routing (CIDR)
format, 485
client desktop, configuring, 371-372
client hypervisors, 373
Composer database, 401
thin, 15-16
SQL Server
View Client, 29
differential, 89
Zero-clients, 16
full, 82-89
cluster gab disks, 448
log, 89
badges, 493
configuring, 468-470
bandwidth, 337
installing, 466-468
Bandwidth Floor option, 64
MCS (mission critical support), 452-453
Bandwidth Rate Limiting chart
(PCoIP), 362
Microsoft Windows 2008 R2, 449-451
bandwidth usage, 334
vSphere, deploying on, 448-449
Bandwidth Utilization chart (PCoIP), 361
Cluster Services, installing Microsoft
clusters, 466-468
baseline of current utilization, developing, 34
cold migration, 26
baselines, 293
dynamic, 293
ESXi hosts, attaching to, 295
SQLCMD, 83, 86
performance, establishing, 481-482
SQLCMD Backup, 84
best practices, 33
offl ine desktops, 384-389
blackout schedules, 237
Build stage (ThinApp), 145
burst I/O, 36
Common Internet File System (CIFS)
shares, 448
Composer database, backing up, 401
compression, RDC (Remote Differential
Compression), 475
desktop images
computers, usernames, 178
client desktop, 371-372
clusters, 468-470
Composer, backing up, 401
DFS (Distributed File System), 475-477
Event Database, 129-131
IP pools, 485
Events, creating, 408-409
iSCSI multipathing, 427-430
data compression, 65
MCS (mission critical support), 453-457
datastores, linked clones, redistributing
among, 249-251
MPIO (multipath I/O), 458-464
redundancy, 444
Transfer Server, 126-128
Update Manager, 284-292
vCenter Heartbeat, 438-441
vCenter Operations, 488-490
View Composer, 234
disks, 235
provisioning, 239-240
vCenter, 235-239
View Connection Server, 120-123
View Planner, 367-371
WANem, 345-346
Windows NLB, 477-478
WireShark, 347-350
Configuration Manager, 421
config.xml file, updating, 161
Connection Latency chart (PCoIP), 364
Connection Quality chart (PCoIP), 363
Connection Server
installing, 117
View, configuring, 120-123
connection servers, 52
connection types, networks, 46
connectivity, network, 443
creation stages, ThinApp, 143-145
DCUI (direct console user interface), 24, 40
debug logs, Transfer Server, 382
dedicated desktops, 212
Deep Security, 308-309, 315
Administrator account, 312
installing, 309
vShield, integration, 315-329
deployed execution, ThinApp packages, 155
Microsoft clusters, vSphere, 448-449
ThinApp packages, 168-171
vCenter Operations, 487-488
vCenter Server, 41-45
VDI (Virtual Desktop Infrastructure),
VMware View, vSphere 5, 39-40
vShield EndPoint, 268
vSphere 5, 40
deployments, VMware View, infrastructure,
Desktop Experience, Terminal Server,
making look like desktop, 199-201
desktop images, 210
creating, 173-175
installing Windows 7 through
VMware Workstation, 181-186
manually installing VMware View
Agent, 179-181
manually installing Windows 7,
desktop images
manually installing Windows 2008
RDS Server, 199
disabling desktop pools, 396-397
disks, View Composer, 235
installing through vCenter,
Distributed File Services (DFS). See DFS
(Distributed File System)
making Terminal Server appear as,
Distributed Resource Scheduler (DRS).
See DRS (Distributed Resource
View Persona management,
completing cycle, 210
Windows 7 optimization, 198-199
desktop pools, 66, 214
assigning users to, 241
Distributed Switch (DS), 423-427
DLLs (dynamic link libraries), 142
Download settings, Update Manager, 287
DRS (Distributed Resource Scheduling),
26, 43, 421
storage, 44-45
automated, 215
workload distribution, 44
creating, 216-222
disabling, 396-397
DS (Distributed Switch), 423-427
manual, 215
dynamic baselines, 293
Terminal Services, 215
dynamic tiering, 35
desktop rationalization study, 12
see also virtual desktops
client, setting up, 371-372
Encoder (PCoIP), 364-366
dedicated, 212
entitling, 27
end-user performance test environments,
building, 336-340
floating, 212
engaging users, 17
nonpersistent, 12, 50
entitlement, 241
offl ine, 373-380, 389
establishing performance baselines, 481-482
best practices, 384-389
ESXi Server, 2, 23-24, 36, 40-41
publishing, 378-381
hosts, attaching baselines to, 295
Transfer Server, 375-383
installing, 98
provisioning, 102-112
persistent, 12
replicas, 244-245
Events database, 129-131
creating, 408-409
storage requirements, 4
DFS (Distributed File Services), 140,
adding, 470-474
installing, 475-477
execution mode, ThinApp packages, 155
differential backups, SQL Server, 89
Fault Domain Manager (FDM), 26
direct console user interface (DCUI), 24, 40
faults, monitoring, 495
HP Remote Graphics Software (HP RGS)
Fault Tolerance (FT), 70, 420, 430-431
File Services, adding, 470-474
FC (Fibre Channel), 448
iSCSI multipathing, configuring, 427-430
FDM (Fault Domain Manager), 26
MCS (mission critical support), 452-453
Fibre Channel (FC), 448
File Services, adding, 470-474
configuring, 453-457
Microsoft Cluster
fi rewall ports, Update Manager, 285
configuring, 468-470
fi rewalls, rules, 135
installing, 466-467
flex profi les, 9
floating desktops, 212
folders, VMware View, 212-214
FQDN (Fully Qualified Domain Name), 123
Frame Rate Limit setting, 64
frames, jumbo, 47
FT (Fault Tolerance), 70, 420, 430-431
full backups, SQL Server, 82-89
Fully Qualified Domain Name (FQDN), 123
Microsoft Cluster on vSphere, deploying,
Microsoft Windows 2008 R2 clusters,
MPIO (multipath I/O), 457-458
configuring, 458-464
scenario, 446-448
storage heartbeats, 423-427
vCenter, 431-432
vCenter Heartbeat
configuring, 438-440
installing, 432-437
GPOs (Group Policy Objects), 166
graphs (PCoIP)
Bandwidth Rate Limiting, 362
Bandwidth Utilization, 361
Connection Latency, 364
Connection Quality, 363
encoding, 364-366
Packet Counts, 363
Group Policy Objects (GPOs), 166
testing, 441-442
VMware FT, 430-431
volumes, preparing, 465-466
Windows NLB
setting up, 477-478
updating switches to support, 478-479
hairpinning, 11
hardware, estimating requirements, 34
hardware requirements, vCenter, 71
high availability (HA). See HA (high
high-level architecture, vShield EndPoint,
HA (high availability), 41, 419-421, 479
Horizon Application Manager, 145-146
DFS (Distributed File System)
host profiles, 112-115
adding, 470-475
hot migration, 26
installing, 475-477
HP Remote Graphics Software
(HP RGS), 10
IANA (Internet Assigned Numbers Authority)
VMware View, 116-120, 393
VMware View Agent, manually, 179-181
IANA (Internet Assigned Numbers
Authority), 62
image repositories, adding, 129
ImageRepository under Published
subfolder, 380
images, virtual desktop, 210
creating, 173-175
installing through vCenter, 186-197
installing Windows 7 through VMware
Workstation, 181-186
making Terminal Server appear as,
manually installing VMware View
Agent, 179-181
manually installing Windows 7, 175-179
manually installing Windows 2008 RDS
Server, 199
vSphere, 98-102
WANem, 340-344
Windows 7
manually, 175-179
VMware Workstation, 181-186
Windows 2008 RDS Server,
manually, 199
WireShark, 346, 347
integer upgrades, ThinApp packages,
Internet Assigned Numbers Authority
(IANA), 62
Internet Protocol Security (IPSec), 453
I/O (input/output), 36
IOPS (input/output per second), 366-367
IP pools, 483-485
View Persona management, 202-210
IPSec (Internet Protocol Security), 453
Windows 7 optimization, 198-199
infrastructure, virtual desktop, 34-39
configuring multipathing, 427-430
inplace upgrades, ThinApp packages,
storage devices, paths, 115
input/output per second (IOPS), 366, 367
clusters, 466-468
jitter, 337
Deep Security, 309
jumbo frames, 47
desktop images, vCenter, 186-197
DFS (Distributed File Services), 475-477
Key Management Service (KMS), 156
ESXi, 98
SQL Server, 73-81
Lab Manager, 5
Update Manager, 277-283
LANs (local area networks), VLANs, 49-50
vCenter, 69, 90-98
latency, 337
minimum hardware requirements, 71
ldmconfig.ldf fi le, 397-398
preparing for, 69-73
vCenter Heartbeat, 432-437
vCenter Operations, 490-509
vCenter Operations (vCOPS), 482-483
VMware View, 22-23
creating IP pools, 484-486
vShield, 306
Multiple Activation Key (MAK)
lifecycle management, applications, 6
linked clones
controlling, View Composer, 242
installing, 73-81
log backups, 89
Microsoft Windows 2008 R2 clusters
creating, View Composer, 243-245
connecting to SAN, 451
datastores, redistributing among, 249-251
creating, 449-450
decreasing size of, View Composer,
cold, 26
load, 366-367
hot, 26
load balancing, 51-53
P2V (physical-to-virtual), 173
Local Mode (View Planner), 367
local-mode VMs, 66-67
minimum hardware requirements,
vCenter, 71
log backups, SQL Server, 89
Minimum Image Quality setting, 64
lossless data compression, 65
modes, View Planner, 367
controlling the build to, 335
lossy data compression, 65
LSI SAS adapters, 127
modules, vShield EndPoint, 271
capacity remaining, 496
performance baselines, establishing,
vCenter Operations
MAK (Multiple Activation Key), 156, 178
management pane, Update Manager, 284
mandatory profi les, 9
manual desktop pools, 215
manually installing
VMware View Agent, 179-181
Windows 7, 175-179
Maximum Bandwidth option, 64
Maximum Initial Image Quality option, 64
MCS (mission critical support), 452-453
configuring, 453-457
configuring, 488-490
deploying, 487-488
licensing, 490-509
vCenter Operations (vCOPS), installing,
MPIO (multipath I/O), 457-458
configuring, 458-464
MTUs (maximum transmission
units), 47
size option, 64
multimedia, 10-11
multipathing, 423
MDT (Microsoft Deployment Toolkit), 174
iSCSI, configuring, 427-430
Microsoft App-V, 7
MCS (mission critical support),
configuring, 453-457
Microsoft clusters, vSphere, deploying on,
Microsoft Deployment Toolkit (MDT), 174
Microsoft SQL Server
differential backups, 89
full backups, 82-89
MPIO (multipath I/O), 457-458
configuring, 458-464
port groups, 428
Multiple Activation Key (MAK), 156, 178
NAS (network-attached storage) appliances
OUs (organizational units), Active
Directory, 53
NAS (network-attached storage)
appliances, 420
OVF (Open Virtual Format) templates, 487
vShield Manager, 300, 301
network connectivity, 286, 443
Network Connectivity settings, Update
Manager, 286
Network Load Balancing (NLB), 447
connection types, 46
traffic, 46
vShield Manager settings, 303
vSwitches, 47-49
NLB (Network Load Balancing), 447
configuring, 477-478
updating Cisco switches to, 478-479
nonpersistent desktops, 12, 50
normal profiles, 9
P2V (physical-to-virtual) migration, 173
vCenter server, scheduling, 70
packages, ThinApp, 140, 174, 266
activation, 156-157
creating, 157-168
deploying, 168-171
setting up environment, 141-156
updating, 254-265
Packet Counts chart (PCoIP), 363
packet delay variation (PDV), 337
packet loss, 337
pairing password, 413-415
PAM (programmable acceleration module)
cards, 36
offl ine desktops, 373-389
parameters, PCoIP, tuning, 351-357
best practices, 384-389
parent folders, permissions, 203
publishing, 378-381
partitions, VMFS-5, 24
Transfer Server, 375-383
Passive Client Mode (View Planner), 367
offl ine mode, VMs, publishing for, 129
passwords, pairing, 413-415
one-way packet delay variation (PDV), 337
patches, Update Manager, 293-300
Open Virtual Format (OVF) templates,
vShield Manager, 300-301
PBX (private branch exchange), 11
operating systems, optimization, 198-199
PCoIP (PC over IP), 10, 29, 62-66, 215, 332,
372, 408
operational I/O, 36
adjustments, 64
Bandwidth Rate Limiting chart, 362
operating systems, 198-199
Bandwidth Utilization chart, 361
VMs (virtual machines), 197-198
Connection Latency chart, 364
organizational units (OUs), Active
Directory, 53
Connection Quality chart, 363
OS disks, VMs (virtual machines),
replacing, 248-249
enhancements, 334-336
Encoder, 364-366
Packet Counts chart, 363
RDM (Raw Device Mapping)
PCoIP Log Viewer, 337
profi les
traffic, Security Server, 135
flex, 9
tuning, 350-364
host, 112-115
PCoIP Encryption Setting, 64
read-only, 9
PCoIP Log Viewer, 337
read-write, 9
PC over IP (PCoIP). See PCoIP (PC
over IP)
programmable acceleration module (PAM)
cards, 36
PDV (packet delay variation), 337
proof of concept (PoC) environment, 173
performance baselines, establishing,
Propero, 2
performance test environments, building,
properties, vSwitches, 47
see also specific protocols
permissions, parent folders, 203
PCoIP (PC over IP), 10
persistent desktops, 12
RDP (Remote Desktop Protocol), 10, 215
persistent disks, managing, 251-253
Persona Management, 132-133
persona management. See user data
physical-to-virtual (P2V) migrations,
vCenter server, scheduling, 70
physical-to-virtual (P2V) migration. See
P2V (physical-to-virtual) migration
VoIP (Voice over IP), 11
provisioning, ESXi Server, Auto Deploy,
provisioning settings, View environments,
desktops, 378-381
VMs (virtual machines), offl ine
mode, 129
planning VMware View, 17-21
PoC (proof of concept) environment,
38, 173
pools, desktop, 214
assigning users to, 241
automated, 215
QoS (quality of service), 65, 66
creating, 216-222
QuickPrep, 223-224
disabling, 396-397
manual, 215
Terminal Services, 215
Pool Settings, VMware View, 228-234
port groups, multipathing, 428
ports, vCenter, 90-91
R2 Server clusters
connecting, 451
creating, 449-450
Postscan stage (ThinApp), 144, 162
Raw Device Mapping (RDM), 448
power options, VMware View, 225-227
private branch exchange (PBX), 11
RDC (Remote Differential Compression),
private vSwitch, vShield port group, 269
RDM (Raw Device Mapping), 448
RDP (Remote Desktop Protocol)
RDP (Remote Desktop Protocol), 10,
215, 334
read-only profi les, 9
read-write profi les, 9
rebalancing View desktops, 249-251
recompose option, View Composer,
redundancy, configuring, 444
refresh option, View Composer, 245-247
registering vShield, 304
Relink utility (ThinApp), 254-255
remote access, 445
Remote Desktop Protocol (RDP), 10,
215, 334
Remote Differential Compression
(RDC), 475
Remote Graphics Software (RGS), 334
Remote Mode (View Planner), 367
replicas, View Composer, 243-245
Repository, Transfer Server, 383
resource pools, assigning virtual machines
to, 61
return on investment (ROI), 6
RGS (Remote Graphics Software), 334
rich end-user experience, 331-332
delivering, 332-334
load, 366-367
Bandwidth Rate Limiting chart, 362
Bandwidth Utilization chart, 361
Connection Latency chart, 364
Connection Quality chart, 363
Encoder, 364-366
Packet Counts chart, 363
tuning, 361-364
PCoIP enhancements, 334-336
performance test environments, 336-340
setting up client desktop, 371-372
tuning PCoIP, 350-361
parameters, 351-357
View Planner, configuring, 367-371
WANem, 340-346
WireShark, 346-350
ROI (return on investment), 6, 34
roles, vCenter, creating, 54-60
RTO Software, 9
rules, fi rewalls, 135
running AV (antivirus) software, 267
sandboxes, 8
SandBox Merge utility (ThinApp), 257-261
SAN (storage area network), 3
SBC (Server-Based Computing)
environments, 139
physical-to-virtual (P2V) migrations,
vCenter server, 70
Update Manager, 288
Security Server
PCoIP traffic, 135
traffic flow, 62
Security Servers, 133-137
segmentation, users, 211
sequencing, 8
Server-Based Computing (SBC)
environments, 139, 331
connection, 52
Connection Server, installing, 117
Security Servers, 133-134
adding, 135-137
fi rewall rules, 135
traffic flow, 62
SQL (structured query language)
differential backups, 89
full backups, 82-89
thin clients
installing, 73-81
streaming, 8
log backups, 89
streaming execution, ThinApp packages, 155
Terminal Servers, desktop pools, 215
DS (Distributed Switch), 423-427
Transfer Server
adding, 128
private, vShield port group, 269
configuring, 126-128
vSwitches, 47-49
offl ine desktops, 375-383
Windows NLB, updating to, 478-479
vCenter Server, 25-27
symmetric multiprocessing (SMP), 70
adding, 123-125
SysPrep, 223-224
deploying, 41-45
System Data Source, creating, 406
physical-to-virtual (P2V)
migrations, 70
SysTrack VP tool, 33
View Connection Server, 27-28, 135
configuring, 120-123
View Transfer, 29
Windows 2008 RDS Server, manually
installing, 199
session management, 16
Setup Capture utility, 158
side-by-side upgrades, ThinApp packages,
tail drop, 65
TCO (total cost of ownership), 6
Templates view, VMs (virtual machines), 187
Terminal Services, 2, 174
desktop pools, VMware View, 215
making look like desktop, 199-201
SMP (symmetric multiprocessing), 70
test failure scenarios, 16-17
snapshots, Update Manager, 290
testing vCenter Heartbeat, 441-442
solid-state drives (SSDs), 35
ThinApp, 7, 31
SQLCMD Backup command, 83-86
AppSync utility, 261-265
SQL Server
Capture utility, 143
differential backups, 89
creation stages, 143-145
full backups, 82-89
packages, 140, 174, 266
installing, 73-81
activation, 156-157
log backups, 89
creating, 157-168
SSDs (solid-state drives), 35-38
deploying, 168-171
storage, 50
setting up environment, 141-156
connectivity, 115-116
storage area network (SAN), 3
updating, 254-265
upgrading inplace, 256-257
storage DRS, 44-45
Relink utility, 254-255
storage heartbeats, 423-427
SandBox Merge utility, 257-261
storage requirements, desktops, 4
ThinReg, 141
Storage VMotion, 42
thin clients, 15-16
ThinReg, 141
third-party support, vShield EndPoint,
Cisco switches, Windows NLB, 478-479
ThinApp packages, 254-265
threshold (KMS), 156
inplace upgrades, 256-257
tiering, dynamic, 35
Relink, 254-255
total cost of ownership (TCO), 6
traffic flow, Security Server, 62
upgrading VMware View, 391-393, 403,
409, 417-418
Transfer Server
example, 393-417
adding, 128
user acceptance testing (UAT), 17
configuring, 126-128
User Access Control (UAC), 166
debug logs, 382
User Datagram Protocol (UDP), 62
offl ine desktops, 375-383
user data management, 9-10
Repository, 383
usernames, computers, 178
Trend Micro, 268
Trend Micro Deep Security. See Deep
desktop pools, assigning to, 241
tuning, PCoIP, 350-351, 357-361
rich end-user experience, 331-332
engaging, 17
Bandwidth Rate Limiting chart, 362
configuring View Planner, 367-371
Bandwidth Utilization chart, 361
delivering, 332-334
Connection Latency chart, 364
load, 366-367
Connection Quality chart, 363
PCoIP, 334-366
Packet Counts chart, 363
performance test environments,
parameters, 351-357
setting up client desktop, 371-372
WANem, 340-346
WireShark, 346-350
UAC (User Access Control), 166
UAT (user acceptance testing), 17
UDP (User Datagram Protocol), 62
Update Manager, 329, 399
enabling snapshots, 290
fi rewall ports, 285
management pane, 284
schedule, 288
vShield EndPoint, 271-273
configuring, 284-292
installing, 277-283
integrating, 273-277
patches, 293-300
user segmentation, 38, 211
utilities, vdmexport, 397
VAMT (Volume Activation Management
Tool), 156
vApps, 483
vCenter, 33
default SQL accounts, 72
deploying as VM (virtual machine), 70
desktop images, installing, 186-197
virtual desktop images
HA (high availability), 431-432
View Agent, 30
host profiles, 112-115
View Client, 16, 29
installing, 69, 90-98
View Composer, 30, 66
minimum hardware requirements, 71
configuring, 234
preparing for, 69-73
disks, 235
ports, 90-91
enabling, 409
selecting databases, 400
entitlement, 241
settings, View environments, 235-239
linked clones, 242
vCenter Heartbeat, 431
provisioning settings, 239-240
configuring, 438-441
rebalance, 249-251
installing, 432-437
recompose, 248-249
testing, 441-442
refresh, 245-247
vCenter Operations (vCOPs), 482, 510
configuring, 488-490
deploying, 487-488
installing, 482-483
creating IP pools, 484-486
licensing, 490-509
setting logging level, 505-506
vCenter Server, 25-27
adding, 123-125
creating customized roles, 54-60
deploying, 41-45
physical-to-virtual (P2V) migrations,
scheduling, 70
restart priority, 423
replicas, 243-245
vCenter settings, 235-239
View Connection Server, 27-28, 135
configuring, 120-123
View Persona
management, 202-209
completing cycle, 210
permissions, 203
View Planner, 336, 366-367
configuring, 367-371
modes, 367
View Transfer server, 29
offl ine desktops, 375-383
virtual applications, entitling, 27
vCenter Server Installer, 402
Virtual Desktop, 5
vCOPS (vCenter Operations). See vCenter
Operations (vCOPs)
virtual desktop image, creating, 173-175
VDI (Virtual Desktop Infrastructure), 1, 35
deploying, 11-15
evolution of, 2-6
origins, 1-2
vdmexport utility, 397
VDM (Virtual Desktop Manager), 2, 5, 334
vDS (vSphere Distributed Switch), 423
versions, VMware View, 21
View Administrator, 28
installing through vCenter, 186-197
installing Windows 7 through VMware
Workstation, 181-186
manually installing VMware View
Agent, 179-181
manually installing Windows 7, 175-179
virtual desktop images, 210
creating, manually installing Windows
2008 RDS Server, 199
making Terminal Server appear as, 1
virtual desktop images
View Persona management, 202-209
completing cycle, 210
Windows 7 optimization, 198-199
Virtual Desktop Infrastructure (VDI).
See VDI (Virtual Desktop
Virtual Desktop Manager (VDM), 2, 5, 334
virtual desktops, 31
infrastructure, 34-39
best practices, 33
vSphere 5, 39-50
rebalancing, 249-251
recomposing, 248-249
reducing size, 245-247
replicas, 243-245
application, 6-9
x86, 1
Virtual Machine Disks (VMDKs), 29, 44,
234, 431
VLANs (virtual LANs), 49-50
vLockstep, 70
VMDKs (Virtual Machine Disks), 29, 44,
234, 431
VMs (virtual machines)
optimization, 197-198
resource pools, assigning to, 61
VMware Fault Tolerance, 430-431
VMware View
manually installing, 179-181
applications, managing, 254
architecture, 50-51
Active Directory, 53-61
desktop pools, 66
load balancing, 51-53
local-mode VMs, 66-67
PCoIP (PC over IP), 62-66
QoS (quality of service), 65-66
configuring, 234
disks, 235
linked clones, 242
provisioning settings, 239-240
rebalance, 249-251
recompose, 248-249
refresh, 245-247
VMFS-5, 24
replicas, 243-245
VMotion, 42
vCenter settings, 235-239
VMs (virtual machines)
local-mode, 66-67
OS disks, replacing, 248-249
publishing for offl ine mode, 129
infrustructure, 34-39
vSphere 5, 39-40
desktop pools, 214
Templates view, 187
automated, 215
vCenter, deploying as, 70
creating, 216-222
VMDKs (Virtual Machine Disks), 234
manual, 215
vShield driver, adding to, 307-308
Terminal Services, 215
entitlement, 241
API, 267
ESXi, 23-24
vShield Endpoint, integration, 269
Event Database, 129-131
folders, 212-214
installing, 116-120
vShield EndPoint, 267-268, 329
introduction of, 5
deploying, 268
licensing considerations, 22-23
high-level architecture, 268-271
persistent disks, managing, 251-253
module, 271
Persona Management, 132-133
third-party support, 308-315
planning for, 17-21
Update Manager, 271-273
Pool Settings, 228-234
configuring, 284-292
power options, 225-227
installing, 277-283
QuickPrep, 223-224
integrating, 273-277
SysPrep, 223-224
ThinApp packages, updating, 254-265
upgrading, 391-392
example, 393-417
patches, 293-300
VMSafe integration, 269
vShield Manager, 268
vShield Manager, 268, 300-307
vCenter server, 25-27
logging into, 304
versions, 21
network settings, 303
vShield EndPoint, 267-268
Open Virtual Format (OVF) templates,
deploying, 268
high-level architecture, 268-271
module, 271
clusters, deploying, 448-449
Update Manager, 271-300
ESXi Server, provisioning, 102-112
VMSafe integration, 269
installing, 98-102
vShield Manager, 268
SQL Server
VMware View 5
differential backups, 89
installing, 393
full backups, 82-89
introduction of, 6
installing, 73-81
VMware Workstation, 181
Windows 7, installing through,
VoIP (Voice over IP), 11
log backups, 89
storage connectivity, 115-116
vCenter, installing, 69-73
vShield Manager, 300-307
Volume Activation Management Tool
(VAMT), 156
vSphere 5, 39-40
volumes, preparing for HA, 465-466
vSphere Update Manager, 399
vSphere View, 422
Deep Security, integration, 315-329
licensing, 306
registering, 304
VMs (virtual machines), adding driver
to, 307-308
vSphere Distributed Switch (vDS), 423
vSwitches, 47-49
Windows File Cluster, 447
Windows NLB, 477-479
WANem, 336-340, 372
WireShark, 336, 372
configuring, 345-346
configuring, 347-350
installing, 340-344
installing, 346-347
Weighted Random Early Detection
(WRED), 65
Windows 7
WRED (Weighted Random Early
Detection), 65
manually, 175-179
x86 virtualization, 1
VMware Workstation, 181-186
XenApp, 7
optimization, 198-199
Windows 2008 RDS Server, manually
installing, 199
Zero-clients, 16
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF