student guide (1 of 2)

VMware View 5.0: Install, Configure, Manage

Student Guide (1 of 2)

HL273S A.00

VMware View 5.0: Install, Configure, Manage

Student Guide (1 of 2)

HL273S A.00 Use of this material to deliver training without prior written permission from HP is prohibited.

These materials, developed and copyrighted by VMWare, Inc., are licensed to Hewlett-Packard Company for customer delivery. Restrictions on use and reproduction are described on the VMWare legal page.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

UNIX is a registered trademark of The Open Group.

Export Compliance Agreement

Export Requirements. You may not export or re-export products subject to this agreement in violation of any applicable laws or regulations.

Without limiting the generality of the foregoing, products subject to this agreement may not be exported, re-exported, otherwise transferred to or within (or to a national or resident of) countries under U.S. economic embargo and/or sanction including the following countries:

Cuba, Iran, North Korea, Sudan and Syria.

This list is subject to change.

In addition, products subject to this agreement may not be exported, re-exported, or otherwise transferred to persons or entities listed on the U.S. Department of Commerce Denied Persons List; U.S. Department of Commerce Entity List (15 CFR 744, Supplement 4); U.S. Treasury Department Designated/Blocked Nationals exclusion list; or U.S. State Department Debarred Parties List; or to parties directly or indirectly involved in the development or production of nuclear, chemical, or biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S. Export Administration Regulations (15 CFR 744); or to parties directly or indirectly involved in the financing, commission or support of terrorist activities.

By accepting this agreement you confirm that you are not located in (or a national or resident of) any country under U.S. embargo or sanction; not identified on any U.S. Department of Commerce Denied Persons List, Entity List, US State Department Debarred Parties List or Treasury Department Designated Nationals exclusion list; not directly or indirectly involved in the development or production of nuclear, chemical, biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S. Export Administration Regulations (15 CFR 744), and not directly or indirectly involved in the financing, commission or support of terrorist activities.

Printed in US VMware View 5.0: Install, Configure, Manage Student guide part 1 January 2012

VMware Education ServicesVMware, Inc.

www.vmware.com/education

VMware View:Install, Configure, ManageStudent Manual Volume 1View 5.0

View5ICMGuideVol1.book Page 1 Monday, December 19, 2011 4:41 PM

www.vmware.com/education

Copyright/Trademark

Copyright 2011 VMware, Inc. All rights reserved. This manual and its accompanying materials are protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.

The training material is provided as is, and all express or implied conditions, representations, and warranties, including any implied warranty of merchantability, fitness for a particular purpose or noninfringement, are disclaimed, even if VMware, Inc., has been advised of the possibility of such claims. This training material is designed to support an instructor-led training course and is intended to be used for reference purposes in conjunction with the instructor-led training course. The training material is not a standalone training tool. Use of the training material for self-study without class attendance is not recommended.

These materials and the computer programs to which it relates are the property of, and embody trade secrets and confidential information proprietary to, VMware, Inc., and may not be reproduced, copied, disclosed, transferred, adapted or modified without the express written approval of VMware, Inc.

VMware View:Install, Configure, ManageView 5.0Part Number EDU-ENG-VICM5-LEC1-STUStudent Manual Volume 1Revision A


VMware View: Install, Configure, Manage i

T A B L E O F C O N T E N T S

M O D U L E 1 Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3You Are Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Typographical Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Housekeeping Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

M O D U L E 2 Introduction to VMware View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7You Are Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10VMware vSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Virtual Desktop Infrastructures and VMware View . . . . . . . . . . . . . . . .12What Is View? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Key Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16View Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Internationalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21View Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23PCoIP Supports the Broadest Coverage of Use Cases . . . . . . . . . . . . . .24View Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25View User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27View Client with Local Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28View Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29ThinApp and Virtual Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31vShield Endpoint Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Extensibility to Third-Party Management Tools . . . . . . . . . . . . . . . . . . .33View Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34vSphere Desktop Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Required vSphere Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Required AD Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Key Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

M O D U L E 3 View Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41You Are Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Module Lessons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Lesson 1: Installing View Connection Server . . . . . . . . . . . . . . . . . . . . .45Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Deploying View (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Deploying View (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48You Are Here in View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

View5ICMGuideVol1.book Page i Monday, December 19, 2011 4:41 PM

ii VMware View: Install, Configure, Manage

View Connection Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . .50View Connection Server Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . .52SSL Certificate Requirements for View Administrator . . . . . . . . . . . . .54Preinstallation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Starting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Selecting the Type of Connection Server . . . . . . . . . . . . . . . . . . . . . . . .58Accepting the ADAM or AD LDS License . . . . . . . . . . . . . . . . . . . . . .59Opening Firewall Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Lesson 2: Configuring View Connection Server. . . . . . . . . . . . . . . . . . .63Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Connecting to View Connection Server with Browser . . . . . . . . . . . . . .65Logging In to View Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Initial Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Licensing View Manager and Components . . . . . . . . . . . . . . . . . . . . . .69View Servers: vCenter Server Systems . . . . . . . . . . . . . . . . . . . . . . . . . .70Adding vCenter Server Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71View Event Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Integrating with the Event Database . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Configuring the View Event Database . . . . . . . . . . . . . . . . . . . . . . . . . .76Modifying Event Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Lab 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Key Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

M O D U L E 4 View Desktops. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83You Are Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Module Lessons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Lesson 1: Configuring Virtual Machines as Desktops . . . . . . . . . . . . . .87Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88Multiple vCPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Creating a Windows Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . .91Windows 7 and Windows Vista Activation . . . . . . . . . . . . . . . . . . . . . .92Windows 7 Sysprep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Disabling Power Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94ESX/ESXi Virtual Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95General Windows Performance Tuning (1) . . . . . . . . . . . . . . . . . . . . . .96General Windows Performance Tuning (2) . . . . . . . . . . . . . . . . . . . . . .97General Windows Performance Tuning (3) . . . . . . . . . . . . . . . . . . . . . .98vCenter Server Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

View5ICMGuideVol1.book Page ii Monday, December 19, 2011 4:41 PM

Contents iii

Group Policy Objects and Roaming Profiles. . . . . . . . . . . . . . . . . . . . .100Disabling the Themes Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Lesson 2: Remote Display Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . .103Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104PCoIP Remote Display Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Highly Efficient Encoding for Desktop Display . . . . . . . . . . . . . . . . . .106PCoIP Progressive Build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Progressive Build Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109VMware PCoIP Remote Display Options . . . . . . . . . . . . . . . . . . . . . . . 110PCoIP Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111PCoIP Display Protocol Features (1) . . . . . . . . . . . . . . . . . . . . . . . . . . 112PCoIP Display Protocol Features (2) . . . . . . . . . . . . . . . . . . . . . . . . . . 113PCoIP Display Protocol Features (3) . . . . . . . . . . . . . . . . . . . . . . . . . . 114Video, Audio, and USB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Configuring PCoIP Optimization Controls . . . . . . . . . . . . . . . . . . . . . . 116PCoIP Administrative Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117PCoIP Policy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118PCoIP Optimization Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Disabling the Build-to-Lossless Feature . . . . . . . . . . . . . . . . . . . . . . . .121Configuring Image Cache Size on the Client System . . . . . . . . . . . . . .123Configuring the PCoIP Audio Bandwidth Limit. . . . . . . . . . . . . . . . . .124Configuring PCoIP Image Quality Levels . . . . . . . . . . . . . . . . . . . . . .125Example of Overriding PCoIP Image Quality Levels . . . . . . . . . . . . . .127Configuring Maximum PCoIP Session Bandwidth. . . . . . . . . . . . . . . .128Configuring the PCoIP Session Bandwidth Floor. . . . . . . . . . . . . . . . .129Remote Desktop Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130Latest Available Version of Remote Desktop Connection . . . . . . . . . .131Remote Enabled Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Firewall Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Lesson 3: View Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Preparing Virtual Desktops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Creating a Standardized Virtual Machine . . . . . . . . . . . . . . . . . . . . . . .138Choosing the Time-Synchronization Method . . . . . . . . . . . . . . . . . . . .139Joining the AD Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Disable Windows Time? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141Installing Applications and Tuning the Desktop . . . . . . . . . . . . . . . . . .142Enabling Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143Installing the View Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144Custom Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Enabling Remote Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

View5ICMGuideVol1.book Page iii Monday, December 19, 2011 4:41 PM

iv VMware View: Install, Configure, Manage

View Agent on Virtual Machines with Multiple NICs . . . . . . . . . . . . .148Lab 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Lesson 4: Manual Pool Deployment and Entitlement . . . . . . . . . . . . . .151Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152Creating a Virtual Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153Creating a Template and Customization Specification . . . . . . . . . . . . .154Testing Deployment and Customization . . . . . . . . . . . . . . . . . . . . . . . .156Adding a Virtual Desktop to a Manual Pool . . . . . . . . . . . . . . . . . . . . .157Starting the Add Pool Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Creating a Manual Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159Selecting the Type of Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160Selecting Type of User Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . .161Selecting the Type of Desktop Sources. . . . . . . . . . . . . . . . . . . . . . . . .162Selecting the vCenter Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . .163Creating the Pool Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Configuring Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165General and Remote Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166Remote Display Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . .167Adobe Flash Bandwidth Reduction. . . . . . . . . . . . . . . . . . . . . . . . . . . .169Adobe Flash Bandwidth Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170Adobe Flash Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171Adobe Flash Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172Overriding Bandwidth Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173Adobe Flash Bandwidth Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174Adding Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175Reviewing the Pool Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .176Pool Is Now in the View Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . .177Entitling Users to Connect to Desktops. . . . . . . . . . . . . . . . . . . . . . . . .178Adding Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179Entitled Users or Groups Are Listed . . . . . . . . . . . . . . . . . . . . . . . . . . .180Pool Is Entitled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181Unmanaged Desktops in a View Environment . . . . . . . . . . . . . . . . . . .182Types of Unmanaged Systems That View Supports . . . . . . . . . . . . . . .183Terminal Services Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184Preparing an Unmanaged Desktop Source . . . . . . . . . . . . . . . . . . . . . .185Registering the Unmanaged Desktop . . . . . . . . . . . . . . . . . . . . . . . . . .186Lab 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188Key Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

View5ICMGuideVol1.book Page iv Monday, December 19, 2011 4:41 PM

Contents v

M O D U L E 5 View Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191You Are Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193Module Lessons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194Lesson 1: View Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196View Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Installing View Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198Default Login Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Before Using View Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Connecting to View Connection Server . . . . . . . . . . . . . . . . . . . . . . . .203View Client SSL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Entering User Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207Selecting a Desktop and Display Option. . . . . . . . . . . . . . . . . . . . . . . .208Unblocking Windows Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Common Login Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210Login Successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212USB Device Status Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214Flexible Monitor Support with PCoIP. . . . . . . . . . . . . . . . . . . . . . . . . .216Session Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217View Client for Mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218SSO Timeout Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219View Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Client Information Available to Desktop . . . . . . . . . . . . . . . . . . . . . . .221What Is a Thin Client?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223What Is a Zero Client?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224Thin Clients That Are Compatible with View . . . . . . . . . . . . . . . . . . .225Troubleshooting Unavailable Desktops . . . . . . . . . . . . . . . . . . . . . . . .226Lab 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228Lesson 2: Virtual Printing with View Clients . . . . . . . . . . . . . . . . . . . .229Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230What Is Virtual Printing?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231Benefits of the Virtual Printing Feature . . . . . . . . . . . . . . . . . . . . . . . .232Reasons to Use the Virtual Printing Feature . . . . . . . . . . . . . . . . . . . . .233Transparency for the User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234Virtual Printing Functions at the Desktop and Client Systems . . . . . . .235Additional Virtual Printing Functions . . . . . . . . . . . . . . . . . . . . . . . . . .236Virtual Printing Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237Installation of Virtual Printing Feature . . . . . . . . . . . . . . . . . . . . . . . . .238Searching for Printers on the Desktop. . . . . . . . . . . . . . . . . . . . . . . . . .239Reinstalling Virtual Printing on the Desktop . . . . . . . . . . . . . . . . . . . .240

View5ICMGuideVol1.book Page v Monday, December 19, 2011 4:41 PM

vi VMware View: Install, Configure, Manage

Reinstalling Virtual Printing on the Client System . . . . . . . . . . . . . . . .241Configuring Virtual Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Adjusting the Compression Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243Location-Based Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244Setting Up Location-Based Printing . . . . . . . . . . . . . . . . . . . . . . . . . . .246The Name-Translation Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247Lab 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249Key Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250

M O D U L E 6 View Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251You Are Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253Module Lessons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254Lesson 1: Initial View Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .255Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256Logging In to View Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . .257View Configuration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258Servers Panes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259VMware vCenter Server Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260Editing vCenter Server: Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261Editing vCenter Server: Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . .262View Connection Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263Restricted Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Restricted Entitlements: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Rules for Creating Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268Tagging a Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Tag-Matching Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270Authentication Options: Smart Cards . . . . . . . . . . . . . . . . . . . . . . . . . .271Connecting to View Connection Server with Smart Cards . . . . . . . . . .272Smart-Card Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274Configuring Smart-Card Authentication . . . . . . . . . . . . . . . . . . . . . . . .276Certificate Revocation Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Smart-Card Removal Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279Authentication Options: RSA SecurID . . . . . . . . . . . . . . . . . . . . . . . . .280Configuring RSA SecurID Authentication . . . . . . . . . . . . . . . . . . . . . .281Adding or Removing View Administrators . . . . . . . . . . . . . . . . . . . . .282Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285Lesson 2: Managing Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . .286Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287Users and Groups Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288Summary Tab for a Selected Group . . . . . . . . . . . . . . . . . . . . . . . . . . .289

View5ICMGuideVol1.book Page vi Monday, December 19, 2011 4:41 PM

Contents vii

Entitlements Tab for a Selected Group . . . . . . . . . . . . . . . . . . . . . . . . .290Summary Tab for a Selected User. . . . . . . . . . . . . . . . . . . . . . . . . . . . .291Details of a User's Persistent Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . .292Sessions Tab for a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293Global Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294Policies at the Pool Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296Overriding Pool Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297Overriding Policies at the User Level . . . . . . . . . . . . . . . . . . . . . . . . . .298Group Policy ADM Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299View ADM Template Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300Lab 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303Lesson 3: Automated Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305User Assignment to a Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306Desktops in a Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307Dedicated-Assignment Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309Creating an Automated Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310Adding a Desktop or Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Selecting the Type of Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312Selecting the User Assignment for Desktops . . . . . . . . . . . . . . . . . . . .313Selecting the vCenter Server System . . . . . . . . . . . . . . . . . . . . . . . . . .314Entering Pool Identification Parameters . . . . . . . . . . . . . . . . . . . . . . . .315Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317Available Desktops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319Provisioning Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320Specifying Names Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322vCenter Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324Selecting a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325Selecting the Virtual Machine Folder . . . . . . . . . . . . . . . . . . . . . . . . . .326Selecting a Host or Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327Selecting a Resource Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328Selecting a Datastore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329vCenter Server Settings Completed. . . . . . . . . . . . . . . . . . . . . . . . . . . .330Selecting the Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331Ready to Complete Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332Entitling the Desktops in the Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333vCenter Server Creates Desktops . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334New Desktop Is Available to View Client . . . . . . . . . . . . . . . . . . . . . .335Desktop Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336Floating-Assignment Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337Floating-Assignment Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .338Lab 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339

View5ICMGuideVol1.book Page vii Monday, December 19, 2011 4:41 PM

viii VMware View: Install, Configure, Manage

Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340Lesson 4: Role-Based Delegated Administration . . . . . . . . . . . . . . . . .341Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342View Connection Server Roles and Privileges . . . . . . . . . . . . . . . . . . .343Using Folders to Delegate Pool Administration . . . . . . . . . . . . . . . . . .345Example: Different Administrators for Different Folders. . . . . . . . . . .347View Connection Server Permissions . . . . . . . . . . . . . . . . . . . . . . . . . .348Examples of Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349Predefined Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350Creating an Administrative User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352Adding Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .353Adding a Pool to a New Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354Adding a Custom Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356Selecting Privileges for a Custom Role. . . . . . . . . . . . . . . . . . . . . . . . .357Best Practices for Administrator Users and Groups . . . . . . . . . . . . . . .358Lab 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360Lesson 5: Monitoring the View Deployment . . . . . . . . . . . . . . . . . . . .361Learner Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362View Administrator Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363Dashboard Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364Examining Component Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365Desktop Status from the Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . .366Monitoring Sessions and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367Events Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368Remote Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369Local Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370Monitoring a Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371Monitoring a Desktop: Summary Tab . . . . . . . . . . . . . . . . . . . . . . . . . .372Monitoring a Desktop: vCenter Settings Tab . . . . . . . . . . . . . . . . . . . .373Monitoring PCoIP Session Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . .374Windows Management Instrumentation . . . . . . . . . . . . . . . . . . . . . . . .375Commonly Used PCoIP Statistics (1) . . . . . . . . . . . . . . . . . . . . . . . . . .377Commonly Used PCoIP Statistics (2) . . . . . . . . . . . . . . . . . . . . . . . . . .378Review of Learner Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379Key Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380

View5ICMGuideVol1.book Page viii Monday, December 19, 2011 4:41 PM

VMware View: Install, Configure, Manage 1

C

ourse Introduction1M O D U L E 1

Course Introduction 1Slide 1-1Cou se t oduct o

Module 1


2 VMware View: Install, Configure, Manage

Importance Slide 1-2

Server-oriented system administrators should be equipped with the knowledge, skills, and abilities to build and run their first VMware virtual desktop infrastructure using VMware Viewvirtual desktop infrastructure using VMware View . This course focuses on View configuration and management using View Connection Server and View Composer.


Module 1 Course Introduction 3

C

ourse Introduction1Learner Objectives

Slide 1-3

After this course, you should be able to do the following:

Identify the View components. Install and configure View Connection Server. Install and configure virtual desktops. Configure and manage View Clients.g g Use View Administrator to configure the View environment. Configure and manage pools of linked-clone desktops. C fi t Vi d kt Configure secure access to View desktops. Configure a local-mode desktop deployment. Describe the steps to deploy View Persona Management to manage user profiles. Manage the performance and scalability of a View deployment. Use VMware ThinApp to package and deploy applications.



You Are HereSlide 1-4

Course Introduction

Introduction to View

Configuring and Managing Linked Clones

Local-Mode Desktops

View Connection Server

View Virtual Desktops

Managing View Security

View Persona Management

Command-Line Tools and Backup OptionsView Client Options

View Administrator

p p

View Connection Server Performance

VMware ThinApp


Module 1 Course Introduction 5

C

ourse Introduction1Typographical Conventions

Slide 1-5

You can find course timing suggestions in the file View5ICM_class_timings_RevA.xlsx. An estimated time for each lab exercise is also included as an instructor note at the end of the lab.

The following typographical conventions are used in this course:

Monospace Filenames folder names pathMonospace Filenames, folder names, path names, command names:the bin directory

Monospace bold What the user types:Monospace bold What the user types:Type ipconfig and press Enter.

Boldface Graphical user interface items:the Configuration tabg

Italic Book titles and emphasis:vSphere Datacenter Administration Guide

Placeholders:



Housekeeping Items Slide 1-6

Sign-in sheet Daily start and end times R t Restrooms Fire exits Meals Class introductions Questions



Introduction to V

Mw

are View2

M O D U L E 2

Introduction to VMware View 2Slide 2-1t oduct o to a e e

Module 2




Course Introduction



Local-Mode Desktops






View Administrator

p p


VMware ThinApp


Module 2 Introduction to VMware View 9

Introduction to V

Mw

are View2


VMware View offers many features for supporting distributed desktops. View consists of several components. To ensure a successful deployment of View you must understand thesuccessful deployment of View, you must understand the relationships between the components.



Learner Objectives Slide 2-4

After this module, you should be able to do the following: Describe the differences between a virtual desktop infrastructure and

View Connection ServerView Connection Server. Describe the features and benefits that View offers. Identify View components:

View Connection Servers Virtual desktops Client systems View Composer

Explain the major function of each View component. List the system requirements for a successful View installation.List the system requirements for a successful View installation.



Introduction to V

Mw

are View2

VMware vSphere Slide 2-5

The VMware vSphere product family is designed for building and managing virtual infrastructures. It consists of VMware ESX/ESXi and VMware vCenter Server (used for configuration and management). Many features that are essential for a virtual desktop infrastructure are available in vCenter Server. For example, the vCenter Server system is used to manage the deployment of virtual machines by using templates and cloning. Cloning is a key feature for virtual desktop deployment.

VMware vSphere: VMware ESX/ESXi App App App App App App App App

Existing Applications Future Applications

VMware vCenter ServerFeatures: Availability

VMware vSphere

VMware vCenter Suite

Availability ScalabilitySecurityAvailability Scalability Security

ApplicationServices

vMotionStorage vMotionHAFault ToleranceData Recovery

vShield ZonesVMSafe

DRSHot Add

Availability ScalabilitySecurity

vCenter Server templates for management of virtual machine deployment InfrastructureServices

ESX and ESXiDRS and DPMMemoryOvercommit

VMFSThin ProvisioningStorage I/O Control

Distributed SwitchNetwork I/O Control

Storage NetworkCompute

Private Cloud Resource Pools Public Cloud



Virtual Desktop Infrastructures and VMware View Slide 2-6

VMware View is different than VMware Virtual Desktop Infrastructure, but it relies on many aspects of VDI operating on the vSphere platform.

Major characteristics of VDI include:

Any guest operating system that is supported by ESX/ESXi can be used as a desktop. As a result, if your enterprise uses Windows, Ubuntu, Red Hat, or Solaris x86 desktops, you can use those in a virtual environment.

A vCenter Server system can manage resources and help deploy desktops. Components like vSphere Distributed Resource Scheduler (DRS), vSphere High Availability, and VMware vSphere vMotion are available for resource management, load balancing, and high availability. vCenter Server features like templates can be used to help deploy virtual desktops.

Various connection brokers can be used. A connection broker (also called a connection server) automates the connection of client PCs to a virtual desktop. Some connection brokers can allow a user to connect to any one of several identical desktops in a pool of desktops. This situation is ideal for environments like help desks, kiosks, and departments where everyone needs the same desktop.

Any remote protocol can be used: Virtual Network Computing (VNC), Remote Desktop Protocol (RDP), Independent Computing Architecture (ICA), or X Window System. Anything

VMware Virtual Desktop Infrastructure (VDI): A solution that virtualizes user desktops within a datacenter infrastructure Can use various operating systems, remote access protocols, and management

tools

Highly customizable but not a packaged solution

VMware View: A VMware solution for VDI Uses PCoIP and Remote Desktop Protocol (RDP) for remote access protocol Uses PCoIP and Remote Desktop Protocol (RDP) for remote access protocol Focuses on Windows desktops Provides View Connection Server, a connection broker and management

t f VDIcomponent for VDI

Packaged solution that includes desktop pool management, virtual printing, application virtualization, storage management, assignment of VMware ThinApp MSI packages offline desktop capabilities and moreMSI packages, offline desktop capabilities, and more



Introduction to V

Mw

are View2

that is built on the TCP/IP protocol can be used to connect a remote client to a virtual desktop. Windows systems normally use Microsoft RDP. Citrix systems use ICA. UNIX and Linux systems can use SSH, VNC, or X Window System (sometimes in combination).

View is the VMware solution for a virtual desktop infrastructure. As such, it relies on VDI elements but necessarily focuses on certain features and capabilities. Major features include:

View offers two display protocols for remote access: PCoIP and RDP.

View focuses on Windows XP, Windows Vista, and Windows 7 desktops.

View provides View Connection Server, which is the connection server and management component for physical and virtual desktops.

View supports secure access to desktops from the Internet.

View is a packaged solution that includes desktop pool management, virtual printing, application virtualization, storage management, integration of VMware ThinApp MSI packages, and offline desktop capabilities.



What Is View?Slide 2-7

The term universal client describes a new desktop or personal computing model. Users want to access applications, data, and workspaces in a personalized and dedicated manner, from anywhere, anytime, using any device. The old model of tightly coupled applications, operating systems, and hardware is not efficient, secure, or adaptable. And end users want applications that can be accessed from multiple devices anywhere, anytime. Enterprises need to provide access to applications and data that are independent of devices or location, in a secure and controlled model.

End users want MyView: a single familiar view of all their applications and data, independent of the device.

View is a universal client solution that enables you to manage operating systems, hardware, applications, and users independently of one another, wherever they might reside. View streamlines desktop and application management, reduces costs, and increases data security through centralization, resulting in greater end-user flexibility and IT control. By encapsulating the operating system, applications, and user data into isolated layers, View enables IT staff to change, update, and deploy each layer independently for greater business agility. View enables customers to extend the value of vSphere and its enterprise-class features (high availability, disaster recovery, and business continuity) to the desktop.

An integrated solution that includes: vSphere 5 and vSphere 4vSphere 5 and vSphere 4 vCenter Server View Connection Server View Composer ThinApp

Unmanaged desktops

VMware vShield Endpoint

Local Mode



Introduction to V

Mw

are View2

With View, you get vSphere software, which includes vCenter Server. A View Premier bundle includes:


View Composer

VMware vShield Endpoint

View Client with Local Mode

ThinApp

View Connection Server is an enterprise-class desktop management server that securely connects users to desktops running on vSphere virtual machines, physical PCs, blade PCs, or Microsoft Terminal Services. With View Connection Server, rolling out desktops and applications to existing users, new users, or groups is fast. It is done from a single Web-based management console in a centralized location.

View Composer works with View Connection Server and vCenter Server. View Composer enables scalable management of virtual desktops that are provisioned from a single master image. It reduces storage cost by using VMware linked-clone technology. It streamlines desktop management by enabling automatic updating and patching of hundreds of images from the master image.

vShield Endpoint enables offloading and centralizing antivirus and antimalware solutions for desktops. It also provides the ability to integrate with antivirus solutions from third-party partners. (vShield Endpoint is not a View component, but it is included with a View Premier license.)

View Client with Local Mode works with View Connection Server. It provides designated end users the ability to download (or check out) their virtual desktop onto a Windows desktop or laptop, update files locally, and check the desktop back in to the datacenter for resynchronization. Administrators have the ability to extend the security and encryption policies of the datacenter to the end users local computer.

Application virtualization with ThinApp further streamlines the management of applications. ThinApp enables organizations to create fewer desktop images by developing a basic image and allowing after-the-fact deployment of applications into those images, with no retesting needed of those images. Fewer View desktop images means fewer images to configure, test, and maintain. (ThinApp is not a View component but is available as part of a View Premier license bundle.)

Additional components that are necessary for a View deployment are a vCenter Server system and Microsoft Active Directory (AD), both of which are shown on the slide.

The slide is key because it is the only one that shows all the View components and ThinApp in context. The relationships among the components is confusing the first time through, so spend adequate time explaining each and their interaction. Recommendation: Discuss the elements on the slide, but defer details until later slides. After you have discussed the major components, return to the slide and talk through a few possible scenarios. Examples include (1) creating a desktop using templates, (2) creating desktops using linked clones, (3) accessing a desktop from a client, (4) managing desktops or pools, and (5) using ThinApp to virtualize an application.



Key Benefits Slide 2-8

View enables IT organizations to decouple a desktop from specific physical devices or locations. View creates a universal client that has an individual, personal view of a users applications and data. The client devices can be Windows and Mac laptops or desktops, Apple iPads, and Android-based tablets, usable from any location.

This capability enables IT organizations to reduce the overall cost of desktop computing by centralizing management, administration, and resources.

Another key benefit is increasing security by:

Understanding and mitigating risk of data loss by maintaining all data within the corporate firewall

Enabling all corporate desktops to be at the highest level of patching and antivirus updates

Providing secure access to View desktops for both PCoIP and RDP through security server

Using the View Client with Local Mode virtual rights management and centrally managed security policies

Creates an individual, personal view of all of a users applications and data

d i fon any device from any location

Reduces costs of overall desktop computing

Unmanaged desktops

desktop computing Increases security Greater management and

t lcontrol Increased business agility

and flexibilityLocal Mode Implicit business continuity

and disaster recovery Decreased power

Local Mode

consumption



Introduction to V

Mw

are View2

View also offers greater management and control by:

Managing all desktops centrally in the datacenter instead of at distributed, remote sites

Provisioning desktops instantly to new users and new departments and facilitating office moves

Managing large numbers of desktops as one entity

Using the View Composer ability to create clones from a central image that automatically join the domain

Using View Connection Server to create dynamic pools of desktops for quick provisioning and rapid updating

Using the ThinApp application sync and application link utilities to dynamically and automatically update applications without the need for an agent

Integrating with AD so that no schema changes are needed

Another key benefit is increased business agility and user flexibility:

View provides flexibility in regard to the changing needs of the business by providing consistent desktops to all users from any network connection.

View provides flexibility to manage business reorganizations, office moves, and expansion into new territories or changing work patterns.

View provides user access from the same desktop from any location, from any device.

ThinApp agentless deployment allows users to install applications on locked-down PCs.

View also provides implicit business continuity and disaster recovery. An alternative work site that has network connectivity can be a recovery site. View guarantees business continuity because the same desktop that is accessed during a disaster recovery scenario is also accessed in the normal workplace. View takes advantage of key components of the vSphere platform, such as vMotion, vSphere HA, and DRS.

View offers decreased power consumption by reducing financial and carbon costs of desktop power used with thin clients, which typically use one-tenth the power of a PC.



View Features Slide 2-9

View is built around vSphere and View Connection Server. View has many significant features:

vSphere integration View uses the vCenter Server system and ESX/ESXi hosts to create an end-to-end virtual desktop solution.

Enterprise-class connection brokering Enterprises use connection brokering to connect their remote clients to their centralized virtual desktops. Connection brokering is also used by administrators for managing View Connection Servers and configuring virtual desktops.

Web-based management user interface Designed for a desktop administrator, View Administrator provides a user-friendly interface that enables central administration of desktops from any location.

Full AD integration View connects to the AD infrastructure to find user and user group accounts. It uses the authentication features of AD to control which users can access virtual desktops.

Support for existing desktops as well as pools of new desktops Manual pools contain existing virtual or physical desktops that have users manually assigned. Users and desktops have a one-to-one relationship. Automated desktop pools provision either dedicated-assignment or floating-assignment virtual desktops. Dedicated desktops mean that users log in to the same desktop every time. Floating desktops are returned to the pool when a user logs out.

vSphere 5.0, 4.1, and 4.0 integration Enterprise-class connection brokering W b b d t i t f Web-based management user interface Full Microsoft Active Directory (AD) integration Support for existing desktops as well as new desktop poolspp g p p p Advanced automated pool management features Flexible deployment options Support for USB client devices Support for USB client devices Ability to cluster many connection servers for high availability and

redundancy S f RSA S ID d d h i i Support for RSA SecurID and smart card authentication View Persona Management to manage user profiles



Introduction to V

Mw

are View2

Advanced pool management features View pool management features enable you to use the desktop cloning features in vCenter Server and View Composer and save power by suspending desktops that are not in use. Suspending desktops this way also frees memory and processing power on the ESX/ESXi host.

Flexible deployment options This flexibility enables deploying critical components of View to different parts of the network to improve security and scalability of the environment.

Support for USB client devices and multimedia redirection USB devices can be locally connected to clients and accessed through the virtual desktop.

Ability to cluster connection servers together for high availability and redundancy Creating a high availability environment avoids a single point of failure. And it adds scalability that eases expanding the environment to support a larger number of users.

Support for RSA SecurID and smart cards Both provide strong, two-factor authentication for added security for end users accessing virtual desktops from clients.

View Persona Management Dynamically associates a user persona to virtual desktops. You can deploy easier-to-manage stateless floating desktops to more use cases while enabling user personalization to persist between sessions.



Internationalization Slide 2-10

View Client and online help for View Client are available in Japanese, French, German, Simplified Chinese, and Korean.

Documents that is available in these languages include VMware View Administration, VMware View Installation, VMware View Upgrades, and VMware View Architecture Planning. All documents are available at http://www.vmware.com/support/pubs.

View Client and online help for View Client are available in the following languages: Japanese Japanese French German Simplified Chinese Korean

The following documents are available in these languages:The following documents are available in these languages: VMware View Administration VMware View Installation VMware View Upgrades VMware View Architecture Planning



Introduction to V

Mw

are View2

Use Cases Slide 2-11

Many use cases appropriate are for View. Only two are discussed in detail here.

One use case is to use View to relocate development and operational functions outside the country. In this use case, View:

Provides centralized, static desktops and test systems while eliminating the risk of data movement or loss

Simplifies the provisioning process for users traveling between locations

Improves application performance and data movement by moving client systems closer to the servers and data typically accessed and supported

A View implementation involves the following:

View virtual desktops are provided to remote users.

Data and applications are moved to servers and storage arrays in the corporate datacenter. Data containment features then prevent data and applications from leaving the datacenter.

Users moving between locations are served by one of the standard desktop images, with data serviced in the datacenter.

Offshore development Remote office and telecommuting C ll t Call centers Office hotelling Desktop replacementp p Brokerage firms Health care industry Business continuity and disaster recovery Business continuity and disaster recovery Any scenario where cost savings, centralized management, security,

user flexibility, and green computing are drivers



Business continuity (BC) and disaster recovery (DR) planning is required to support users offsite from alternative offices and home computers. Comprehensive BC/DR plans achieve:

Reduction in support effort and hardware cost to support exception scenarios

Consolidation of work effort, support, and cost of BC, DR, and production requirements into a single computing model

Simplification of client computing by providing a single interface and access to all applications regardless of location or scenario

Stateless devices provisioned to reduce setup complexity and reduce support effort and cost

A View implementation enables the following:

BC/DR sites can be provisioned ahead of time with appropriate network access.

Thin client devices can be provisioned at BC/DR sites much less expensively than traditional (thick) clients.

Thin client setup is much faster than setup of a standard PC.

Virtual desktops can be migrated or failed over from exception sites, if adequate resources are available at a DR site.

The ability to deploy virtual desktops from a single virtual machine instance reduces virtual desktop setup time.



Introduction to V

Mw

are View2

View Components Slide 2-12

These components are discussed on the following pages.

View Connection Server View Composer Automated desktop provisioning/decommissioning Secure connections to desktops

Storage-saving linked clones Tiered storage options

View user interface Thi A

Secure connections to desktops Desktop pools that can expand on demand Desktop session timeouts

Tiered storage options Rapid desktop deployment Quick update/patch management

View user interface ThinApp Self-service, single sign-on PCoIP remote display protocol Support for thick and thin client devices Support for Windows and Mac client devices

Application virtualization View Administrator can

assign and install ThinApp MSI packages.

Virtual PrintingLocal Mode

Support for Windows and Mac client devices View Persona Management (roaming profiles)

Secure, offline desktop capability Universal print driver



PCoIP Supports the Broadest Coverage of Use Cases Slide 2-13

IT departments are faced with many deployment options and use cases. As the slide shows, the display protocols are designed to solve specific challenges for specific use cases.

View Connection Server using PCoIP is designed to provide a flexible solution that is capable of addressing the broad set of use cases and deployment scenarios shown on the slide.

LAN deliveryLAN delivery WAN deliveryWAN delivery

Hi h b d idth L b d idth High bandwidth PC experience

RDP

Low bandwidth Productivity desktop

RDP

T k k Power userVMware View Connection Server

Task worker Knowledge worker Developers 2-D, 3-D, Flash, multimedia

Power user Designer High resolution 3-D

virtual desktops blade PCs RDP



Introduction to V

Mw

are View2

View Connection Server Slide 2-14

View Connection Server can run on either a physical or a virtual machine, although running View Connection Server on a virtual machine has many advantages.

View Connection Server works with vCenter Server systems to manage virtual desktops. Desktops can be individual virtual machines that are dedicated to a user. The desktops can also be members of an automated pool that is deployed on demand. An automated pool can deploy dedicated-assignment or floating-assignment desktops:

Dedicated-assignment desktop Users are allocated a desktop that retains all of their documents, applications, and settings between sessions. The desktop is statically assigned the first time that the user connects and is then used for all subsequent sessions. No other user is permitted access to the desktop.

Floating-assignment desktop Users might be connected to different desktops from the pool each time that they connect. Environmental or user data does not persist between sessions.

View Connection Server supports the use of a virtual desktop that operates on a physical client system. This capability is called local-mode desktops. First, you check out a vCenter Server virtual desktop, which moves the desktop image to your client system. You can then disconnect from View Connection Server and use the desktop in local mode until you are ready to upload all changes and reconnect to the online version.

Desktop connection broker maintains desktop assignment Supports SSL connection to desktop using RDP

S RSA S ID d d h i i Supports RSA SecurID and smart card authentication Supports virtual desktops operating locally on physical client systems Uses vCenter Server to provision virtual desktops as needed:

Existing virtual desktops (dedicated to a user) Dedicated-assignment pools (dedicated to a user) Floating-assignment pools (available to any user)g g p ( y )

Supports multiple desktop operating systems: Windows 7 Windows XPWindows XP Windows Vista

Administered from a Web-based interface



Desktops, whether virtual machines or physical machines, must be Windows 7, Windows XP, or Windows Vista systems. View Connection Server also manages desktops from a Microsoft Terminal Services server.

For DMZ deployments, View Connection Server provides a security server. The security server can be deployed using RDP as the remote display protocol.

For high availability deployments, more View Connection Servers can be deployed. They are called replica instances of a View Connection Server. All View servers use a replicated database to remain coordinated.

View Administrator, a Web-based management interface, enables View administrators to perform all the configuration, deployment, and administrative tasks for View.



Introduction to V

Mw

are View2

View User Interface Slide 2-15

Three types of clients can access View desktops:

View Client Software that installs into a Windows or Mac client system. The client system can be Windows 7, Windows XP, Windows Vista, Mac OS X Leopard 10.5, Mac OS X Snow Leopard 10.6, Android-based tablets, and Apple iPads.

Thin clients and zero clients.

View Client with Local Mode Permits an image of an online virtual desktop to be moved to a local system, used as if it is a remote desktop, and then moved back.

After a user authenticates with View server, the sign-on can be passed through to the virtual desktop. The user sees a single sign-on process. If a smart card is used for authentication to access the client system, those credentials are passed to the connection server and on to the assigned desktop.

Access: View Client for Windows, Mac systems, iPad, Android tablets, and certain

thin client devicest c e t de ces View Client with Local Mode for Windows client systems View API Embedded in certain thin client devices

Single sign-on to remote desktop sessionSingle sign-on to remote desktop session Unified access to:

Desktop virtual machines Ph i l d kt (PC bl d t ) Physical desktops (PC or blade systems) Terminal Server sessions



View Client with Local ModeSlide 2-16

View Client with Local Mode addresses the challenge of providing continuous access that is implicit in any online desktop solution. Through circumstance or choice, users might find themselves in environments where network availability is limited or absent.

Local mode offers mobile users the ability to check out a cloned instance of certain types of View desktops onto a local physical system, such as a laptop, that is running Windows. After the local copy has been checked out, it behaves like a standalone desktop system and can be used with or without a network connection. The virtual desktop is now considered to be offline. When the user is ready, the updated instance of the desktop can be checked in and the user can then access the online virtual desktop. Only the changes are uploaded to the online version.

Checkout of virtual desktops to physical devices Supported on Windows client systems S t d i th t l t k Supports devices that can lose network

connectivity or work offline, such as laptops Extends security and encryption policies to offline

usersusers Uses a heartbeat to View Connection Server for:

Synchronization of desktops Policy enforcement




Introduction to V

Mw

are View2

View Composer Slide 2-17

View Composer enables View Connection Server administrators to rapidly clone and deploy multiple desktops from a single centralized base image, called a parent virtual machine. After the desktops have been created, they remain indirectly linked to a snapshot residing on the parent virtual machine. View Composer is a separate Windows service that must be installed on the same system that hosts vCenter Server. It is a colocated service.

The link is indirect because the first time a desktop clone is created, a uniquely identified copy of the parent virtual machine (called a replica) is also created. All the desktop clones are anchored to the replica, not to the parent virtual machine. Desktops of this type are called linked-clone desktops.

Because all the linked-clone desktops in this environment are connected to a common source (the replica virtual machine), View Composer permits the centralized management of desktops while maintaining a seamless user experience. Tasks like resetting each system to its default configuration, balancing storage, installing software, and applying service packs are greatly accelerated by this type of deployment.

When a View administrator configures an automated dedicated pool that uses linked-clone technology, an option is to attach a persistent user data disk to the clone. The user data disk retains user-specific data and is never affected by normal centralized-update operations.

Uses linked-clone technology: Disk savings Supports tiered storage

delta disk Adesktop A Supports tiered storage

Image separation: Shared operating system disk:

R li t h i kl

parentread-only

base image

desktop B- Replicates changes quickly across

dependent virtual machines Persistent user data disk:

- Retains user specific data

delta disk B

desktop A persistent disk- Retains user-specific data

QuickPrep or Sysprep for user personalization

Installed on each vCenter Serverdesktop B persistent

disk Installed on each vCenter Server system (but not vCenter Server Appliance)



View Composer will use either the VMware QuickPrep process or Microsoft Sysprep to personalize each deployed desktop. Although QuickPrep is similar to Microsoft Sysprep and is much faster, it does not generate a new system ID for each linked-clone desktop.

View Composer must be installed on the same system that hosts vCenter Server. Using vCenter Server Appliance with View Composer is not supported.



Introduction to V

Mw

are View2

ThinApp and Virtual PrintingSlide 2-18

Application virtualization using ThinApp streamlines the management of applications. ThinApp enables organizations to create fewer desktop images by developing a basic image and allowing deployment of applications into those images with no retesting needed. Another benefit is that upgrading an operating system is easier without so many resident, installed applications. ThinApp further increases the storage savings that a flexible virtual desktop architecture already provides.

ThinApp enhances the deployment of applications in a View environment. View Connection Server can assign a ThinApp package to one or more desktops and then remotely install the package on these desktop systems.

The Virtual Printing feature of View enables View Client users to transparently use local or network printers from their desktop systems. Yet it removes the requirement for installing proprietary printer drivers on each virtual desktop.

Virtual Printing is a plug-and-play solution. After a printer has been installed on the local client system, it is automatically added to the list of available printers on the View-managed virtual desktop. No further configuration is required.

VMware licenses this capability from Cortado (previously known as ThinPrint).

ThinApp: Virtualizes and encapsulates applications:

D l li ti d d t f th ti t Decouples applications and data from the operating system Allows one copy of application to be run by multiple users

View Connection Server enables deployment of ThinApp MSI k di tl t ifi d kt ll d kt i lpackages directly to specific desktops or all desktops in a pool.

Virtual Printing: Uses the Cortado (renamed from ThinPrint) virtualized printer driver, ( ) p ,

included in the View Client Eliminates the need for specific printer drivers in each desktop users

always have access to the right printer.y g p Uses compression to minimize network use Supports location-based printing



vShield Endpoint IntegrationSlide 2-19

vShield Endpoint delivers an introspection-based antivirus solution. vShield Endpoint uses the hypervisor to scan guest virtual machines from the outside without a bulky agent. vShield Endpoint is efficient in avoiding resource bottlenecks while optimizing memory use.

vShield Endpoint installs as a hypervisor module and security virtual machine from a third-party antivirus vendor (VMware partners) on an ESX/ESXi host.

The vShield Endpoint thin agent must be installed on each guest virtual machine to be protected. Virtual machines with the thin agent installed are automatically protected whenever they are started on an ESX/ESXi host that has the security solution installed. That is, protected virtual machines keep the security protection through shutdowns and restarts and even after a vMotion migration to another ESX/ESXi host with the security solution installed.

Centralization of an antivirus solution through vShield Endpoint eliminates agent sprawl across desktop virtual machines. Centralization also helps eliminate the antivirus storm issues that are typically associated with antivirus services distributed across virtual machines.

vShield Endpoint requires vCenter Server 4.1 or later.

Improves performance and effectiveness of existing endpoint security solutions:

VMpersona

VMpersona

VMpersona

SVMendpoint security solutions: Offloads antivirus (AV) activity

to security virtual machine (SVM)

personaappOS

kernelBIOS

personaappOS

kernelBIOS

personaappOS

kernelBIOSOS

AV

hardened(SVM) Eliminates desktop agents and

AV storms Enables comprehensive VMware vSphere 4 1

hardened

introspection

Enables comprehensive desktop virtual machine protection

Centrally manages AV service

VMware vSphere 4.1

Centrally manages AV service across virtual machines with detailed logging of AV activity

Partner integrationg



Introduction to V

Mw

are View2

Extensibility to Third-Party Management ToolsSlide 2-20

Third-party management tools can be used to manage the View environment. View includes automation and integration with Windows PowerShell and integration with Microsoft System Center Operations Manager (SCOM).

View PowerCLI provides Windows PowerShell cmdlets to administer View from the command line. Windows PowerShell uses the Microsoft .NET object model and provides administrators with management and automation capabilities. As with any console environment, you work with Windows PowerShell by running commands, which are called cmdlets.

View Connection Server includes more than 45 Windows PowerShell-based cmdlets. You can use these cmdlets with the VMware vSphere PowerCLI cmdlets. You can also use the View cmdlets to examine the configuration of vCenter Server systems and management of licensing, global configuration, connection brokers, pools, entitlements, and desktop-user assignment. This enhancement allows for automation and scripting and provides extensibility to administration tasks.

View PowerCLI is installed during the View Connection Server installation.

For more about using View PowerCLI, see VMware View Integration at http://www.vmware.com/support/pubs.

Automation and integration with Windows PowerShell: View PowerCLI cmdlets can be used to administer View from the

Windows PowerShell command lineWindows PowerShell command line. Allows:

Configuration of vCenter Server systemsM f li i l b l fi i i l Management of licensing, global configuration, connection servers, pools, entitlements, and desktop-user assignments

Integration with Microsoft System Center Operations Manager (SCOM)(SCOM)



View Licensing Slide 2-21

View is sold in two editions, Enterprise and Premier, either as a bundled solution that includes vSphere or as a desktop add-on to a separate or existing vSphere purchase. View Enterprise offers the View desktop management product. View Premier includes several additional components to substantially lower the costs of managing applications and desktops.

For further information, see VMware View 4.5 FAQ: Pricing, Licensing and Support at http://www.vmware.com/technical-resources/products/view.html.

Enterprise and Premier editions: Enterprise vSphere Desktop edition, vCenter Server system, and View

Connection ServerCo ect o Se e Premier vSphere Desktop edition, vCenter Server system, View

Connection Server, View Composer 2.7, View Persona Management, View Client with Local Mode, ThinApp 4.6, and vShield Endpoint.

Licensed per concurrent user: Number of desktop machines that are simultaneously receiving remote

connections from client systems Additional licensing required:

Support and subscription services Guest operating system licensing for desktops



Introduction to V

Mw

are View2

vSphere Desktop EditionSlide 2-22

vSphere Desktop edition is designed for licensing vSphere in VDI deployments. vSphere Desktop licensing is based on the total number of powered-on desktop virtual machines.

vSphere Desktop edition provides all the capabilities of vSphere Enterprise Plus, as well as an unlimited vRAM entitlement.

vSphere Desktop edition can be used for only VDI deployments. It can also be used with View and third-party VDI connection brokers.

vSphere Desktop edition is designed for licensing vSphere in VDI deployments.

vSphere Desktop edition provides:vSphere Desktop edition provides: All capabilities of vSphere Enterprise Plus Unlimited vRAM entitlement

vSphere Desktop edition can be: vSphere Desktop edition can be: Used for only VDI deployments Leveraged with both View and other third-party VDI connection brokers

vSphere Desktop edition is licensed based on the total number of powered-on desktop virtual machines.



Required vSphere Components Slide 2-23

View requires vSphere 5.0, vSphere 4.1, or vSphere 4.0. Current versions of ESX/ESXi hosts must be present and managed by current vCenter Server instances.

If Sysprep is used for template-based Windows desktop deployment or linked-clone deployment, the vCenter Server system must have Microsoft Sysprep tools installed. All Sysprep customization requires a vCenter Server customization specification that permits cloned virtual machines to join an AD domain.

Requirements for View Connection Server:

vSphere 5.0 or later

vSphere 4.1 Update 1 or later

vSphere 4.0 Update 3 or later

ESX/ESXi hosts vCenter Server system S ft Software:

VMware vSphere 5.0 or later VMware vSphere 4.1 Update 1 or later

vCenter Server systems

VMware vSphere 4.0 Update 3 or later If Sysprep is used to provision a desktop:

For Windows XP desktops, Microsoft Sysprep tools must be installed on the vCenter Server system.

A customization specification that permits cloned virtual machines to join the AD domaincloned virtual machines to join the AD domain

ESX/ESXi hosts



Introduction to V

Mw

are View2

Required AD Components Slide 2-24

View Connection Server relies on Active Directory for authentication. The virtual desktops and the View Connection Servers (standard and replica instances) must be members of a domain. But domain membership is not required for vCenter Server, View clients, or View security servers.

To add users to a different AD domain, you must establish a two-way trust relationship between the domain and the domain in which View Connection Server is located.

A Microsoft AD domain must be present.Domain membership is required for: All desktops View Connection ServerDomain membership is not required for:Domain membership is not required for: vCenter Server systems View Clients View security serversRequired components: AD domain controllers AD domain controllers DNS with both forward and reverse lookup zones DHCP



Review of Learner Objectives Slide 2-25

You should be able to do the following: Describe the differences between a virtual desktop infrastructure and

View Connection ServerView Connection Server. Describe the features and benefits that View offers. Identify View components:

View Connection Servers Virtual desktops Client systems View Composer

Explain the major function of each View component. List the system requirements for a successful View installation.List the system requirements for a successful View installation.



Introduction to V

Mw

are View2

Key Points Slide 2-26

View features include: Enterprise-class connection brokering and simplified desktop

management vSphere integration Support for existing desktops and automatically provisioned desktops Superior end user experience with PCoIP Superior end-user experience with PCoIP Flexible end-user accessView components include : View Connection Servers, which manage View desktops View Composer, which creates and manages linked-clone desktops View desktops which are installed with View Agent View desktops, which are installed with View Agent View client options, which include View Client, View Client with Local

Mode, Apple iPad, and Android-based tablets



View

Connection S

erver3

M O D U L E 3

View Connection Server 3Slide 3-1e Co ect o Se e

Module 3




Course Introduction



Local-Mode Desktops






View Administrator

p p


VMware ThinApp


Module 3 View Connection Server 43

View

Connection S

erver3


Installing and properly configuring VMware View Connection Server is essential for a successful View deployment.



Module Lessons Slide 3-4

Lesson 1: Installing View Connection ServerLesson 2: Configuring View Connection Server


Module 3 View Connection Server 45

View

Connection S

erver3

Lesson 1: Installing View Connection ServerSlide 3-5

Lesson 1:Installing View Connection Server



Learner Objectives Slide 3-6

After this lesson, you should be able to do the following: Compare the types of connection servers. List the recommended hardware requirements for View Connection

Server. Identify the VMware vSphere requirements for a connection server. Describe the network and firewall configurations fo