vmview-Student Lab Guide.pdf

VMware View 5.0: Install, Configure, Manage

Student Lab Guide

HL273S A.00

VMware View 5.0: Install, Configure, Manage

Student Lab Guide

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 lab guide January 2012

VMware® Education ServicesVMware, Inc.

www.vmware.com/education

VMware View:Install, Configure, ManageStudent Laboratory ExercisesView 5.0

View5ICM_LabGuide.book Page 1 Tuesday, December 20, 2011 2:44 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-LAB-STUStudent Laboratory ExercisesRevision A


VMware View: Install, Configure, Manage i

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

Lab 1: Installing and Configuring the View Connection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Lab 2: Installing the View Agent in Desktops. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Lab 3: Creating and Entitling a View Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Lab 4: Installing and Using the View Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Lab 5: Configuring and Using Virtual Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Lab 6: Modifying Global Settings and Managing Users and Sessions . . . . . . . . . . . . . . . . . . . . . . .29

Lab 7: Creating and Using Automated Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Lab 8: Role-Based Delegated Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Lab 9: Accessing VMware ThinApp Applications with View Desktops . . . . . . . . . . . . . . . . . . . . .45

Lab 10: Installing View Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Lab 11: Deploying Linked-Clone Desktops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Lab 12: Modifying Linked-Clone Desktops. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Lab 13: Managing Linked-Clone Persistent Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Lab 14: Configuring a View Security Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Lab 15: Configuring a View Replica Server (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Lab 16: Capturing Applications with VMware ThinApp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Lab 17: Deploying an Application Captured with VMware ThinApp. . . . . . . . . . . . . . . . . . . . . . . .85

Lab 18: Packaging Internet Explorer 6 with VMware ThinApp . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

View5ICM_LabGuide.book Page i Tuesday, December 20, 2011 2:44 PM

ii VMware View: Install, Configure, Manage

View5ICM_LabGuide.book Page ii Tuesday, December 20, 2011 2:44 PM

1

Lab 1 Installing and Configuring the View Connection Server 1

Lab 1

Installing and Configuring the View Connection Server :

Objective: Install and configure the View Connection Server

In this lab, you will perform the following tasks:

1. Add an ESXi host to the vCenter Server inventory.

2. Confirm setup of the virtual machine to be used as the connection server.

3. Install View Connection Server software.

4. License View Manager.

5. Associate a vCenter Server system with the View Connection Server.

6. Configure an event database.

Preparing for the labRecord the following information:

VMware vCenter Server™ system fully qualified domain name (FQDN)

vCenter Server Administrator user name

vCenter Server Administrator password


2 Lab 1 Installing and Configuring the View Connection Server

Task 1: Add an ESXi host to the vCenter Server inventory

In this task, you will add an ESXi host to the vCenter Server inventory.

1. Use the VMware vSphere® Client™ on your Terminal Server desktop to log in to your assigned vCenter Server system as the Administrator user. The FQDN of the vCenter Server system and the Administrator password are recorded in “Preparing for the lab.”

2. Create a datacenter called Training:

a. Right-click the name of your vCenter Server system and select New Datacenter.

b. Type Training for the folder name.

3. Right-click the Training datacenter and select Add Host.

4. Enter the ESXi host FQDN that you recorded in “Preparing for the lab.”

5. In the Username text box, type root.

6. Enter the ESXi host root password that you recorded in “Preparing for the lab” and click Next.

7. On the Security Alert page, click Yes to trust the host.

8. Review Host Information and click Next.

9. On the Assign License page, click Next.

VMware ESXi™ host FQDN

ESXi host root password

VMware View™ Connection Server virtual machine name

View Connection Server Administrator password

Active Directory domain

View administrator user name

View administrator password

UNC for the course files network share

View Connection Server FQDN

View Connection Server remote FQDN:port

View license key


1


10. On the Configure Lockdown Mode page, accept the default and click Next.

11. On the Virtual Machine Location page, select Training and click Next.

12. Review the summary and click Finish.

Task 2: Confirm setup of the virtual machine to be used as the connection server

In this task, you will confirm setup of the virtual machine to be used as the connection server. It must be a member of the domain and configured for remote desktop access. Windows Firewall is not used in the lab exercises, so it must be disabled.

1. Open a remote console to the assigned View Connection Server virtual machine and log in as Administrator. The virtual machine name and password are recorded in “Preparing for the lab.”

2. Join the virtual machine to the classroom domain:

a. Click Start. Right-click Computer and select Properties.

b. Click Change Settings and in the Computer Name tab, click Change.

c. Select Member of Domain and specify the Active Directory domain that you recorded in “Preparing for the lab.” When prompted, enter the View administrator user name and password that you recorded in “Preparing for the lab.”

d. When prompted, restart the virtual machine.

e. After the virtual machine reboots, log in to the domain with the View administrator user name and password that you recorded in “Preparing for the lab.”

3. Configure the server for Remote Desktop access:

a. Right-click Computer and select Properties.

b. Click Remote settings. Verify that the Allow connections from computers running any version of Remote Desktop (less secure) option is selected.

c. Click the Select Users button in the Remote tab and verify that the Remote Desktop Users group is in the list of authorized users.

d. Click OK twice. Close the System window.



Task 3: Install View Connection Server software

In this task, you will Install View Connection Server software.

1. Select Start > Run and enter the UNC for the course files network share, as recorded in “Preparing for the lab.” Click OK.

2. Copy VMware-viewconnectionserver-x86_64-<build>.exe from the shared folder to the desktop. Open the copy on the desktop to start the installation.

3. Click Yes in the User Account Control dialog box to proceed with the installation.

4. Click Next to begin the installation.

5. On the License Agreement page, accept the license agreement and click Next.

6. On the Destination Folder page, click Next to accept the default destination folder.

7. On the Installation Options page, select View Standard Server and click Next.

8. On the Firewall Configuration page, verify that Configure Windows Firewall automatically is selected and click Next.

9. On the Ready to Install the Program page, click Install.

10. When the installer completes, click Finish.

11. Turn off Windows Firewall:

a. Select Start. Right-click Network and select Properties.

b. On the Network and Sharing Center page, select Windows Firewall (lower left corner).

c. On the Windows Firewall page, select Turn Windows Firewall on or off.

d. On the Customize Settings page, select Turn off Windows Firewall (not recommended) under Domain network location settings. Click OK.

e. Close the Windows Firewall page.

12. Close all windows on the connection server desktop.

13. Reset the screen resolution of the View Connection Server virtual machine desktop to at least 1024x768 for View Administrator use.

14. Close the remote console window.


1


Task 4: License View Manager

In this task, you will license View Manager.

1. From the Terminal Server desktop, start Internet Explorer and type <View_Connection_Server_FQDN>/admin. Make sure that you type lowercase admin.

You can also log in to View Administrator from your classroom’s physical desktop by using the View Connection Server remote FQDN:port/admin, as recorded in “Preparing for the lab.”

2. Click Yes to acknowledge any security certificate questions.

3. Log in with the View administrator account and password that you recorded in “Preparing for the lab.”

4. If necessary, select View Configuration > Product Licensing and Usage in the left pane.

5. In the Licensing pane, click Edit License and enter the license serial number that you recorded in “Preparing for the lab.”

6. Click OK.

7. Confirm in the Licensing pane that the license expiration date is later than the ending date of this course and that View Composer is enabled.

Task 5: Associate a vCenter Server system with the View Connection Server

In this task, you will associate your vCenter Server system with the View Connection Server.

1. In the navigation pane, select View Configuration > Servers.

2. In the vCenter Servers pane, click Add.

3. Enter the FQDN of the vCenter Server system that you are using. The FQDN is recorded in “Preparing for the lab.”

4. In the User name box, type Administrator and enter the password for the vCenter Server system, as recorded in “Preparing for the lab.”

5. Enter a description of the vCenter Server instance. Click OK.

6. Accept the SSL and port defaults and click OK.



Task 6: Configure an event database

In this task, you will configure an event database for use by View Manager. Before View events can be captured and recorded, an event database connection must be configured. A database, rather than a log file, is used to keep all event information.

1. Select View Configuration > Event Configuration.

2. In the Event Configuration page, click Edit and enter the following values.

3. Click OK.

Field/Setting Value

Database server Enter the FQDN of your vCenter Server virtual machine, as recorded in “Preparing for the lab.”

Database type Select Microsoft SQL Server.

Port Verify that it is 1433.

Database name Type ViewEventsDB.

User name Type viewadmin.

Password Type vmware.

Table prefix Type VE_.


1


4. Verify connection to the event database. Select Monitoring > Events and confirm that a message like “VMEDUC\ferret01a has added database configuration” is displayed. You might need to refresh the page (click the refresh icon in the upper right corner).

5. Minimize the View Administrator window.

Estimated time: 25 minutes. Each lab exercise gives a time estimate derived from the experience of instructors who did the lab exercises.

Task 1: A general caution: Remind students to always shut down a virtual machine rather than power it off. If the virtual machine is shut down, the DHCP-assigned IP address is returned to the pool. If the virtual machine is powered off, the address is not returned and there is a risk of IP address exhaustion.

Task 2, step2: Students might ask why the domain join is not done automatically. The automated process that deploys virtual machines during the VDC kit setup does not allow an automatic join.

Task 4: Remind students that whenever they are performing administrator functions in the View Connection Server (that is, connecting through HTTP or HTTPS to the administration page), they should use the View administrator credentials. When connecting to a virtual desktop, they should use the View user credentials. This procedure mimics a production environment.




2

Lab 2 Installing the View Agent in Desktops 9

Lab 2

Installing the View Agent in Desktops :

Objective: Install the View Agent in a Windows XP desktop


1. Create a vCenter Server resource pool for View desktop pools.

2. Prepare the Windows XP desktop.

3. Install the View Agent.

4. Establish a Remote Desktop Connection to the virtual desktop.




Administrator password for desktop 1 (dt1)

Active Directory domain

VMware View™ administrator user name



10 Lab 2 Installing the View Agent in Desktops

Task 1: Create a vCenter Server resource pool for View desktop pools

In this task, you will create a vCenter Server resource pool for View desktop pools.

1. Log in to the assigned vCenter Server instance, using the VMware vSphere® Client™ on the Terminal Server desktop. Log in as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Under your VMware ESXi™ host, create a resource pool for desktop virtual machines:

a. Right-click your ESXi host name and select New Resource Pool.

b. In the Name box of the resource pool, type Desktops.

c. Accept all default values. Click OK.

Task 2: Prepare the Windows XP desktop

In this task, you will prepare a virtual machine for use as a View virtual desktop. The virtual machine must be a member of the domain.

1. Use the vSphere Client to review the Summary tab for the desktop 1 virtual machine (dt1-<ESXi_host_name>) and confirm that it is connected to the Privnet network and has an IP address.

2. Open a remote console to the dt1-<ESXi_host_name> virtual machine and log in as Administrator. The password is recorded in “Preparing for the lab.”


a. Click Start, right-click My Computer, select Properties, and click the Computer Name tab. Click Change.

b. Select Member of Domain and specify the Active Directory domain that you recorded in “Preparing for the lab.” When prompted, enter the View administrator user name and password that you recorded in “Preparing for the lab.”

c. When prompted, restart the virtual machine.

d. Log in to the domain with the View administrator user name and password that you recorded in “Preparing for the lab.”


Administrator password for client A (cla)


2

Lab 2 Installing the View Agent in Desktops 11

4. Use the Registry Editor (select Start > Run and type regedit) to make the following changes:

a. Go to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ TermService\Parameters key.

b. Delete the following values if they are present: Certificate, X509 Certificate, and X509 Certificate ID.

c. Exit the Registry Editor.

Task 3: Install the View Agent

In this task, you will install the View Agent, confirm that Windows Firewall is disabled, and verify that remote connections are enabled.

1. On the dt1-<ESXi_host_name> desktop, select Start > Run. Enter the UNC for the course files network share, as recorded in “Preparing for the lab.” Click OK.

2. Connect to the shared folder as Administrator, using the vCenter Server Administrator password that you recorded in “Preparing for the lab.”

3. Copy VMware-viewagent-<build>.exe from the shared folder to your desktop. Open the copy on the desktop to start the installation.


5. Accept the license agreement. Click Next.

6. On the Custom Setup page, accept the default installation of five View Agent features: USB Redirection, View Composer Agent, Virtual Printing, PCoIP Server, and View Persona Management. All but PCoIP Smartcard are installed. Click Next.

7. If prompted, accept the default Enable the Remote Desktop Capability on this computer. Click Next.


9. Click Finish when the installation is complete. Do not restart the system when prompted.

10. Verify that Windows Firewall is disabled:

a. Select Start > Run and type services.msc.

b. Stop the Windows Firewall service if it is running: Right-click the service, select Properties, and select Disabled for the Startup type. Click OK and close the Services window.

11. Restart the system and log in again as the View administrator.


12 Lab 2 Installing the View Agent in Desktops

12. Verify that Remote Desktop is enabled (select My Computer > Properties and click the Remote tab) and that the Remote Desktop Users group is in the list of authorized users.

13. Log out of the desktop virtual machine (Start > Log off) and close the remote console window.

Task 4: Establish a Remote Desktop Connection to the virtual desktop

In this task, you will establish a Remote Desktop Connection to the virtual desktop from another Windows XP virtual machine to verify that the virtual desktop can be connected with a remote connection.

1. Use the vSphere Client to review the Summary tab for the client A virtual machine (cla-<ESXi_host_name>) and confirm that it is connected to the Privnet network and has an IP address.

2. Open a remote console to cla-<ESXi_host_name> and log in as Administrator, using the password that you recorded in “Preparing for the lab.”

3. Verify that the Windows Firewall is disabled: Select Start > Run and type services.msc. Stop the Windows Firewall service if it is running: Right-click the service, select Properties, and select Disabled for the Startup type. Click OK and close the Services window.

4. Verify Remote Desktop Protocol connectivity between the client virtual machine and the desktop 1 virtual machine:

a. From the client virtual machine, start the Remote Desktop Connection client by selecting Start > All Programs > Accessories > Remote Desktop Connection.

b. Connect to the dt1-<ESXi_host_name> virtual machine.

c. Enter your View administrator user name and password to log in to the desktop. Make sure that you use the user name in the form of <domain_name>\<user_name>. These names are recorded in “Preparing for the lab.”

d. After successfully logging in—which verifies connectivity—log out of the remote session. The desktop is now ready to be managed by View Connection Server.

5. Log out of the client virtual machine and close the remote console window.

Estimated time: 15 minutes

Task 2: <ESXi_host_name> is used throughout the labs to refer to the ESXi host identifier that makes each virtual machine name unique. It is not the actual host name, which is of the form sc-kitname0x, but rather the kitname and server number. The kitname is specific to the VMware Virtual Datacenter, so it is not used in the labs.

Task 5, step 4c: Students must log in to the desktop virtual machine with domain credentials to verify that remote connectivity works correctly. Here, the View administrator credentials are used instead of nonadministrator View user credentials to avoid a potential problem with the user profile when students do the linked-clone exercises.


3

Lab 3 Creating and Entitling a View Desktop 13

Lab 3

Creating and Entitling a View Desktop :

Objective: Create a desktop virtual machine from a template and entitle it


1. Clone a Windows XP virtual machine to a template.

2. Modify the customization specification that will be used to clone Windows XP desktops.

3. Deploy a second Windows XP desktop virtual machine from the template.

4. Confirm correct deployment of the virtual machine.

5. Create two manual pools, each with one desktop virtual machine.

6. Entitle the manual pools.




Administrator password

Datastore for the template


14 Lab 3 Creating and Entitling a View Desktop

Task 1: Clone a Windows XP virtual machine to a template

In this task, you will clone a Windows XP virtual machine to a template that can be used to provision desktops in an automated pool.

1. From the Terminal Server remote desktop, start a Remote Desktop Connection to your assigned vCenter Server virtual machine and start the VMware vSphere® Client™ from its desktop:

a. Start the Remote Desktop Connection and enter the vCenter Server system FQDN, as recorded in “Preparing for the lab.” Click Connect.

b. After connecting to the vCenter Server virtual machine, log in as Administrator, using the using the password that you recorded in “Preparing for the lab.”

c. Start the vSphere Client from the desktop and log in to Localhost as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Open a remote console to the dt1-<ESXi_host_name> virtual machine and log in as the View administrator (using the user name and password that you recorded in “Preparing for the lab”). Remove the virtual machine from the domain and add it to WORKGROUP. After the virtual machine reboots, shut down the virtual machine, and close the remote console window.

3. In the vCenter Server inventory, right-click the dt1-<ESXi_host_name> virtual machine name and select Template > Clone to Template. Make sure that you clone this virtual machine. Do not convert it.

4. Type dt-<ESXi_host_name>-template as the name for the template. Select the Training datacenter. Click Next.

5. Select your VMware ESXi™ host and click Next.

6. On the Storage page, leave Same format as source selected.

Windows XP product ID

Local datastore

Active Directory (AD) domain



View administrators group

View users domain group


3


7. Select the datastore that you recorded in “Preparing for the lab” to store the template. Click Next.

8. Click Finish. Go to the next task while you monitor completion of the cloning operation in the Recent Tasks pane.

Task 2: Modify the customization specification that will be used to clone Windows XP desktops

In this task, you will modify the customization specification that will be used to clone Windows XP with Sysprep. The cloned desktops are joined to the domain during customization.

1. From the vSphere Client View menu, select Management > Customization Specifications Manager.

2. Right-click Windows XP Customization Specification and select Edit.

3. For the Cannot decrypt password message, click OK.

4. Verify that VMware is used in Name and Organization. Click Next.

5. Verify that the Use the virtual machine name option has been selected for the computer name. Click Next.

6. Verify that the Windows XP product ID matches the one that is recorded in “Preparing for the lab.”

7. Verify that Include the Server License Information is deselected. Click Next.

8. Enter the Administrator password that you recorded in “Preparing for the lab.” Deselect Automatically log on as the Administrator. Click Next.

9. Confirm that the time zone is (GMT) Greenwich Mean Time. Click Next.

10. Click Next to skip the Run Once page.

11. Leave the network interface settings at Typical settings. The clones will use a DHCP address. Click Next.

12. Click Windows Server Domain and enter the AD domain name, View administrator user name, and View administrator password that you recorded in “Preparing for the lab.” Enter this information carefully: a typographical error here will prevent the deployed virtual machine from joining the domain. Click Next.

13. Leave the Generate New Security ID (SID) setting enabled. Click Next.

14. Review the summary. Click Finish.

15. Click the back arrow next to the address bar to return to the vCenter Server inventory view.



16. When the template-cloning task has finished, rejoin dt1-<ESXi_host_name> to the classroom domain so that it can be used as a virtual desktop:

a. Open a console to the dt1-<ESXi_host_name> virtual machine, power it on, and log in as Administrator, using the password that you recorded in “Preparing for the lab.”

b. Right-click My Computer, select Properties, and click the Computer Name tab. Click Change.

c. Select Member of Domain and specify the AD domain that you recorded earlier in “Preparing for the lab.” When prompted, enter the View administrator user name and password that you recorded in “Preparing for the lab.”

d. When prompted, restart the virtual machine, but do not log in. Close the remote console.

Task 3: Deploy a second Windows XP desktop virtual machine from the template

In this task, you will deploy a second Windows XP desktop virtual machine from the template.

1. Using the vSphere Client, select dt-<ESXi_host_name>-template. You might have to change to the VMs and Templates view (View > Inventory > VMs and Templates).

2. Right-click the template name and select Deploy Virtual Machine from this Template.

3. Type dt2-<ESXi_host_name> as the name for the new virtual machine. Select the Training datacenter. Click Next.

4. Select your ESX host and click Next.

5. Select the Desktops resource pool and click Next.

6. On the Storage page, leave Same format as source selected.

7. Select the local datastore of your ESXi host (recorded in “Preparing for the lab”) to store the virtual machine. Click Next.

8. On the Guest Customization page, select Power on this virtual machine after creation.

9. Select Customize using an existing customization specification and then select Windows XP Customization Specification. Click Next.

10. For the Cannot decrypt password message, click OK.

11. Click Finish to deploy the virtual machine.

12. Monitor the virtual machine deployment in the Recent Tasks pane. After the deployment completes, go to the next task.


3


Task 4: Confirm correct deployment of the virtual machine

In this task, you will confirm correct deployment of the virtual machine. It must be joined to the domain and must have the View Agent installed.

1. Open a console to the dt2-<ESXi_host_name> virtual machine. The virtual machine will boot twice as part of the customization process. Wait until the reboots are finished and the virtual machine is powered on and stable.

2. Log in to your dt2-<ESXi_host_name> virtual machine as View administrator, with the password that you recorded in “Preparing for the lab.” Confirm the following:

• Remote desktop is enabled and the Remote Desktop Users group is authorized to use the remote desktop.

• The View Agent is installed and running. Verify this by finding the VMware View Agent service in the list of started services (select Start > Run and type services.msc).

3. Log out of the desktop virtual machine and close the console window.

Task 5: Create two manual pools, each with one desktop virtual machine

In this task, you will create a manual pool that contains two desktop virtual machines.

1. Use Internet Explorer to connect to View Administrator. In the address box, type cs-<ESXi_host_name>.vmeduc.com/admin. (admin must be lowercase.)

2. Log in as the View administrator. Use the user name and password that you recorded in “Preparing for the lab.”

3. In View Administrator, select Inventory > Pools.

4. On the Pools page:

a. Click Folder and select New Folder:

b. In the Name box, type Marketing desktops and click OK.

c. Create a second folder and name it “Sales desktops.”

5. On the Pools page, click Add.

6. On the Type page, select Manual Pool. Click Next.

7. On the User Assignment page, select Dedicated and confirm that Enable automatic assignment is selected. Click Next.

8. On the Desktop Source page, accept the default of vCenter virtual machines. Click Next.



9. On the vCenter Server page, your vCenter Server system should already be highlighted, so click Next.

10. On the Pool Identification page enter the following values. Click Next when finished.

11. On the Pool Settings page, in the Remote Settings pane, change Allow users to reset their desktops to Yes. Accept all other defaults and click Next.

12. On the Add vCenter Virtual Machines page, select the dt1-<ESXi_host_name> virtual machine. Click Next.

13. On the Ready to Complete page, review the summary and click Finish.

14. Repeat the preceding steps to add a second manual pool. On the Pool Identification page, use the following values. Click Next when finished.

15. On the Pool Settings page, in the Remote Settings pane, change Allow users to reset their desktops to Yes. Accept all other defaults and click Next.

16. On the Add vCenter Virtual Machines page, select the dt2-<ESXi_host_name> virtual machine. Click Next.

Field/Setting Value

ID Type Payroll-XP.

Display name Type Payroll-XP.

View Folder Accept the default root folder.

Description Type Individual dedicated desktop.

Field/Setting Value

ID Type Marketing-XP.

Display name Type Marketing-XP.

View folder Select Marketing desktops.

Description Type Individual desktop.


3


Task 6: Entitle the manual pools

In this task, you will entitle the two manual pools that you created, which allows any user in the View users group or the View administrators group to connect to them. After a connection is made to a desktop, the desktop is dedicated to that user.

1. On the Pools page, select the row with a Display name of Payroll-XP. Click anywhere in the row to select it. You can select only one entry at a time.

2. Entitle the View administrators group and View users group:

a. Click Entitlements to display which users and groups are allowed to connect to this desktop.

b. On the Entitlements page, click the Add button.

c. On the Find User or Group page, deselect Users. In the Name/User Name text box, type View. Click Find.

d. Select both rows and click OK.

e. On the Entitlements page, verify that both groups are listed and click OK. Verify that the Entitled column for the Payroll-XP manual pool has a green check mark.

3. Repeat the preceding steps to entitle Marketing-XP for the same set of domain groups.

4. Leave View Administrator active. You will connect to these desktops in the next lab, after installing View Clients.


Task 1, step 1: The vSphere Client on the desktop of the vCenter Server virtual machine must be used because the credentials retained in the Windows XP customization specification must be updated. The proper certificates for this operation cannot be stored on the Terminal Server.

Task 1, step 2: The desktop machine is removed from the domain as a precaution. For templates that are to be used for the Virtual Desktop Infrastructure, a best practice is that they not be a member of the domain before you convert or clone them to a template. This problem appears to be an issue mainly with the customization process in vCenter Server, not in View.

Task 4, step 2: If you are using the Technical Services virtual datacenter, the VDC Remote Desktop Users group must be present. If for some reason it is not present, have the students select Start > Run and type gpupdate /force to populate the list. If the VDC is not used, the name of the group will be Remote Desktop Users or similar.

Task 5, step 1: The Internet Explorer instance should be the one on the Terminal Server desktop or on the desktop of the student’s physical system in the classroom.




4

Lab 4 Installing and Using the View Client 21

Lab 4

Installing and Using the View Client :

Objective: Install the View Client and connect to a virtual desktop


1. Install the View Client.

2. Connect to a virtual desktop.

3. Clone a second client virtual machine.




Administrator password for client A (cla)


View Connection Server FQDN

View user name A


22 Lab 4 Installing and Using the View Client

Task 1: Install the View Client

In this task, you will install the View Client on a Windows XP virtual machine.

1. If you are not already logged in, use the VMware vSphere® Client™ to log in to vCenter Server. Log in as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Open a remote console to the client A virtual machine (cla-<ESXi_host_name>) and log in as Administrator, using the password that you recorded in “Preparing for the lab.”

3. Select Start > Run and enter the UNC for the course files network share, recorded in “Preparing for the lab.”

4. Copy VMware-viewclient-<build>.exe from the network share to your desktop. Open the copy on the desktop to start the installation.


6. Accept the license agreement. Click Next.

7. On the Custom Setup page, click Next to install with the USB redirection and Login as current user options enabled.

8. On the Default Server page, enter the FQDN of your View Connection Server, recorded in “Preparing for the lab.” Click Next.

9. On the Enhanced Single Sign On page, accept the default setting and click Next.

10. On the Configure Shortcuts page, accept the defaults and click Next.

11. On the Ready to Install the Program page, click Install. Do not restart the system when prompted.

12. Verify that Windows Firewall is disabled:

a. Select Start > Run and type services.msc.

b. Stop the Windows Firewall service if it is running: Right-click the service, select Properties, and select Disabled for Startup type. Click OK and close the Services window.

13. Restart the system and log in again as Administrator.

View user A password

Local datastore


4

Lab 4 Installing and Using the View Client 23

Task 2: Connect to a virtual desktop

In this task, you will connect to a virtual desktop in the Payroll-XP manual pool.

1. If necessary, log in to the client A virtual machine (cla-<ESXi_host_name>) as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Start the View Client from the client A virtual machine desktop.

3. Connect to the View Connection Server, using the FQDN that you recorded in “Preparing for the lab.” This connection server should be the default.

4. Configure the View Client SSL configuration:

a. Click Options.

b. Click Configure SSL.

c. Select Allow the unverifiable connection (Not secure).

d. Click OK.

5. Click Connect in the VMware View Client window.

6. Log in with the assigned View user A credentials that you recorded in “Preparing for the lab.” (Notice that the password for View users A and B might be different than the administrator passwords.)

7. Select the Payroll-XP desktop. (You should see the Payroll-XP and Marketing-XP desktops that you set up and entitled earlier.) Click Connect to connect to the desktop.

8. To distinguish between the client machines’s desktop and the virtual desktop’s desktop, look for the menu bar at the top of the virtual desktop window.

9. After you have confirmed connection to the virtual desktop, click Options on the menu bar and select Disconnect and Log off.

10. Shut down the client virtual machine (select Start > Shut Down) so that it can be cloned. Close the remote console window.

Task 3: Clone a second client virtual machine

In this task, you will clone a second client virtual machine (client B) for use in later labs. Two client machines will enable concurrent connections to two desktops. A vSphere Client connection to your vCenter Server system should still be active.

1. Ensure that cla-<ESXi_host_name> is powered off.

2. Right-click cla-<ESXi_host_name> and select Clone.


24 Lab 4 Installing and Using the View Client

3. Use the parameters in the table when prompted by the Clone Virtual Machine wizard to create the second client virtual machine. Allow the client to power on and complete the Sysprep steps.


Task 3: You can return to lecturing while the clone operation and Sysprep steps complete.

Field/Setting Value

Name clb-<ESXi_host_name>

Inventory location Training

Host Your VMware ESXi™ host

Resource pool Your ESXi host (that is, place the virtual machine in the root resource pool)

Same format as source Leave selected.

Datastore The local datastore that you recorded in “Preparing for the lab”

Power on this virtual machine after creation

Select.

Customization Select Customize using an existing customization specification.

Select Windows XP Customization Specification.

Click Finish.


5

Lab 5 Configuring and Using Virtual Printing 25

Lab 5

Configuring and Using Virtual Printing :

Objective: Configure desktops and clients to use the Virtual Printing feature


1. Install and use a virtual printer.

2. Configure a virtual printer instance on the virtual desktop.



VMware View™ user name A

View user password



26 Lab 5 Configuring and Using Virtual Printing

Task 1: Install and use a virtual printer

In this task, you will install and use a virtual printer in a virtual desktop, using the Virtual Printing feature. Because no physical printer is available, doPDF (a free PDF printer driver from http://www.dopdf.com) is used to demonstrate this feature.

1. Power on the client A virtual machine (cla-<ESXi_host_name>), open a remote console, and log in as Administrator.

2. Verify that no printers are installed.

3. Start the View Client and connect to the Payroll-XP desktop system with View user A credentials, recorded in “Preparing for the lab.”

4. On the virtual desktop system (Payroll-XP), verify that no printers are installed. Disconnect and log out of the Payroll-XP desktop. In the menu bar, select Options > Disconnect and log off.

5. On the client A system (cla-<ESXi_host_name>), install the doPDF printer from the classroom share. Use the UNC for the course files network share, recorded in “Preparing for the lab.”

6. Set the doPDF printer as the default printer.

7. Connect to the Payroll-XP desktop system and verify that the doPDF printer has been installed. After the printer is installed on the client, it will be visible on the virtual desktop system.

8. On the virtual desktop system, open a Web page. Print the page to the default printer (it will be the desktop of the client system). When prompted, use the Browse button to store the print file on the desktop of the client. After the print operation has completed, a PDF file should appear on the desktop of the client system. Minimize the Payroll-XP desktop, open the new file, and confirm that it is the Web page that you selected.

Task 2: Configure a virtual printer instance on the virtual desktop

In this task, you will explore the configuration options for the virtual printer that you installed on the virtual desktop.

1. Return to the virtual desktop and open the printer dialog box (Start > Printers and Faxes). Right-click the doPDF printer (the printer name is of the form doPDF v7#:1) and select Properties. The Print Properties window associated with the virtual printer is displayed.

2. Click the ThinPrint Device Setup tab. These properties are set by the client, so overriding them requires administrator-level privileges.

3. Click the General tab and click Printing Preferences. These properties can be modified by a normal user. The user can edit the page orientation and color appearance. The default values are acquired from the printer configuration on the client machine (cla-<ESXi_host_name>).


5

Lab 5 Configuring and Using Virtual Printing 27

4. Click the Advanced tab. To preview each printout on the client, select Preview on client before printing. While in the preview, you can use any printer with all its available properties.

5. Click the Adjustment tab to view the automatic print adjustment options. Keep the default settings.

6. Click Cancel to close the Printing Properties page. Click OK to close the print properties window.

7. Close the Printers and Faxes window.

8. Disconnect and log out of the Payroll-XP desktop.


Task 1, step 8: If students experience a problem trying to print a page, have them disconnect and log out, and reconnect to the desktop.


28 Lab 5 Configuring and Using Virtual Printing


6

Lab 6 Modifying Global Settings and Managing Users and Sessions 29

Lab 6

Modifying Global Settings and Managing Users and Sessions :

Objective: Use View Administrator to configure global View parameters and manage users and sessions


1. Modify three global settings values.

2. Limit vCenter Server provisioning operations.

3. Use View Administrator to disconnect a logged-in user and reset a virtual desktop.

4. Retrieve information about specific users.

5. Examine recent connection server events.


VMware View™ Connection Server FQDN

View Connection Server remote FQDN:port




30 Lab 6 Modifying Global Settings and Managing Users and Sessions

Task 1: Modify three global settings values

In this task, you will change the client-desktop session timeout to 120 minutes, enable automatic status updates, and change the default logout warning time to 2 minutes.

1. Log in to View Administrator with the View administrator user name and password that you recorded in “Preparing for the lab.” Use this URL: cs-<ESXi_host_name>/admin.

You can also log in to View Administrator from your classroom’s physical desktop by using the View Connection Server remote FQDN:port/admin, as recorded in “Preparing for the lab.”

2. In View Administrator, select View Configuration > Global Settings.

3. On the Global Settings page, click Edit.

4. In the Global Settings dialog box:

a. Change Session timeout from 600 minutes to 120 minutes.

b. Select Enable automatic status updates.

c. Change the logout warning time to 2 minutes and edit the message in the text box to agree with the change in warning time.

5. Click OK.

Task 2: Limit vCenter Server provisioning operations

In this task, you will limit VMware vCenter Server™ provisioning operations.

1. In the navigation pane, select View Configuration > Servers.

2. In the vCenter Servers panel, select your vCenter Server system. The line should turn blue when selected.

3. Click Edit and click Advanced.

4. In Max concurrent provisioning operations, type 4.

5. In Max concurrent power operations, type 4.

6. Click OK.

Administrator password for client A virtual machine

View user name A



6

Lab 6 Modifying Global Settings and Managing Users and Sessions 31

Task 3: Use View Administrator to disconnect a logged-in user and reset a virtual desktop

In this task, you will use View Administrator to disconnect a logged-in user and reset a virtual desktop.

1. If necessary, log in to the cla-<ESXi_host_name> client virtual machine as Administrator with the password that you recorded in “Preparing for the lab.”

2. Start the View Client. Log in to the View Connection Server, using the View user name A and password that you recorded in “Preparing for the lab.”

3. Connect to the Payroll-XP desktop so that you will have an active user and desktop session for the next steps.

4. Switch to the window displaying View Administrator. If necessary, log in to View Administrator with your View administrator credentials.

5. In View Administrator, select Inventory > Desktops to display the Desktops page. This page shows the correlation between the virtual machine name (Desktop column), the pool, the DNS name, and the assigned user. The Status column indicates which desktops are connected or are available. The Mode column shows whether it is a remote session (a View Client connection) or a local session (a local-mode desktop).

6. Because the connected desktop is in Remote mode, select Monitoring > Remote Sessions to see more session-oriented information.

7. Select the active session. The row is highlighted.

How long has the session been active? _____________________________________

8. Click Send Message to send a warning-type message to the user that the desktop will have to be disconnected. Return to the client A system and verify receipt of the message.

9. Return to View Administrator and click Disconnect session to disconnect the user. Click OK. Refresh the Remote Sessions pane and verify the disconnect.

10. Return to the client A system and verify that the desktop is disconnected.

11. Reconnect to the Payroll-XP desktop.

12. Return to the VMware vSphere® Client™ and open a remote console to the dt1-<ESXi_host_name> desktop so that you can confirm that it resets in the next steps. The remote console is black.

13. Return to View Administrator and select Inventory > Desktops. The Desktops page should show the dt1-<ESXi_host_name> desktop as Connected. Refresh the display, if necessary.


32 Lab 6 Modifying Global Settings and Managing Users and Sessions

14. Select the desktop and click Reset. Click OK to confirm the reset. Quickly return to the dt1-<ESXi_host_name> remote console to observe the virtual desktop rebooting. After the desktop resets, refresh the Desktops page and confirm that the status of the desktop is now Available.

15. Close the console window for dt1-<ESXi_host_name>.

Task 4: Retrieve information about specific users

In this task, you will use View Administrator to retrieve information about specific users.

1. In View Administrator, select Users and Groups. In the User Name column, double-click ViewUsers/vmeduc.com twice.

How many users are in this group? ________________________________________

2. Click Find Desktops.

Are any desktops dedicated to View user A? ________________________________

3. Click OK to close the Find Desktops page.

4. Click the Entitlements tab.

Are users in ViewUsers group entitled to access desktops? _____________________

Task 5: Examine recent connection server events

In this task, you will examine recent View Manager events by filtering all events associated with your View administrator credentials.

1. In View Administrator, select Monitoring > Events.

2. Use the Filter text box to search for all events containing your View administrator user name, recorded in “Preparing for the lab.” Review the event list to determine whether you have performed these actions in earlier labs. Find the event that recorded the message that you sent to the user in task 1. Click the ellipsis (...) icon to see the full message.

3. Use the Filter text box to review all events with a Severity of Audit Success.

4. Assume that your security administrator needs to know when a specific user logged in to a specific desktop. Can you provide that information using the event database? Assume that the user is View user A and that the desktop is dt1-<ESXi_host_name>. What steps would produce the information? Hint: Start by using the Find text box to limit the events list to those involving dt1-<ESXi_host_name>.


Task 3, step 5: If the User column displays the user’s SID, rather than the user name, click the ID. This action displays the user information page. Click Update General User Information. Click Back.


7

Lab 7 Creating and Using an Automated Pool 33

Lab 7

Creating and Using an Automated Pool :

Objective: Create and use an automated pool


1. Set up a vCenter Server folder for virtual desktops in a pool.

2. Create an automated pool with dedicated-assignment desktops.

3. Verify the creation of the pool by connecting to a desktop.

4. Test a second concurrent connection to a desktop in the pool.

5. Delete the automated pool.






Datastore for desktop pools



34 Lab 7 Creating and Using an Automated Pool

Task 1: Set up a vCenter Server folder for virtual desktops in a pool

In this task, you will set up a VMware vCenter Server™ folder to group the virtual desktops into a vSphere resource pool. The resource pool enables better control over memory and CPU allocation and use.

1. If it is not already active, use the VMware vSphere® Client™ to log in to your assigned vCenter Server system as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Change the vCenter Server inventory view to VMs and Templates (View > Inventory > VMs and Templates).

3. Create a folder under the Training datacenter named Sales-Desktops. View Connection Server will use this folder to group the desktops that are in a pool.

Task 2: Create an automated pool with dedicated-assignment desktops

In this task, you will create an automated pool with dedicated desktops. The desktops will be full clones that are provisioned from a template that was created in an earlier lab. The pool will be entitled for the View users group.

1. If the View Administrator window is not already active, start Internet Explorer and connect by typing cs-<ESXi_host_name>/admin. Log in as the View administrator.


3. On the Pools page, click Add to start the Add Pool wizard.

4. On the Type page, select Automated Pool.

5. On the User Assignment page, select Dedicated and select Enable automatic assignment.

6. On the vCenter Server page, select Full virtual machines and verify that your vCenter Server system name is highlighted.


View user name A


View user name B

View user B password


7


7. On the Pool Identification page, use the following values.

8. On the Pool Settings page, select Yes for Allow users to reset their desktops. Accept all other defaults.

9. On the Provisioning Settings page, use the following values.

Field/Setting Value

ID Type Pool-Sales-XP.

Display name Type Sales-XP.

View folder Select Sales desktops.

Description Type Automated pool of dedicated desktops for Sales.

Field/Setting Value

Virtual Machine Naming Select Use a naming pattern and type <ESXi_host_name>-Sales in the Naming Pattern box.

Max number of desktops Type 2.

Number of spare (powered on) desktops Verify that it is 1.

Provision desktops on demand Select, and accept the default of 1 desktop as the minimum.

Click Next. If the Add Pool wizard reports that the virtual machine naming pattern is too long, truncate your VMware ESXi™ host name to six characters, including the host number. For example, ocelot03 becomes ocel03.



10. On the vCenter Settings page, use Browse to select these values.

11. On the Guest Customization page, select Use this customization specification and then select Windows XP Customization Specification.

12. On the Ready to Complete page, review the settings and click Finish.

13. On the Pools page, select the pool with an ID of Pool-Sales-XP.

14. Click Entitlements and entitle this pool for the View users domain group that you recorded in “Preparing for the lab.”

15. Minimize the View Administrator window and switch to your vSphere Client. You should see vCenter Server begin to create a virtual machine named <ESXi_host_name>-Sales1 in the Sales-Desktops/Pool-Sales-XP folder. These folders are visible in the VMs and Templates inventory view. Wait for the virtual machine creation to complete. The virtual machine will go through multiple reboots because of Sysprep.

16. Return to View Administrator and select Inventory > Desktops. Wait for the status of the virtual machine to show Available. You might have to refresh the page periodically.

Field/Setting Value

Template dt-<ESXi_host_name>-template

VM Folder Sales-desktops

Hosts or Cluster Your ESXi host

Resource Pool Desktops

Datastores Select the datastore that you recorded in “Preparing for the lab.” The datastore to select might be different than the local datastore. Verify that only this datastore is selected.

Click Next.


7


Task 3: Verify the creation of the pool by connecting to a desktop

In this task, you will verify the creation of the pool by connecting to a provisioned desktop. Each desktop is dedicated to the first user who connects.

1. If necessary, log in to the cla-<ESXi_host_name> virtual machine as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Open the View Client and connect to the View Connection Server as View user A, as recorded in “Preparing for the lab.”

3. Connect to Sales-XP. If a message appears stating that there are currently no desktop sources available, wait a minute and try again.

4. Switch to the vSphere Client. You should soon see vCenter Server begin to create a second virtual machine, named <ESXi_host_name>-Sales2, to keep the available number of virtual desktops in the pool at one. Be patient: it might take a minute or so before you see activity in the Recent Tasks pane.

Task 4: Test a second concurrent connection to a desktop in the pool

In this task, you will test a second, concurrent connection to another desktop in the pool. After both connections are confirmed, you will disconnect and log out of the desktops.

1. Open a remote console to your second client virtual machine (clb-<ESXi_host_name>) and log in as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Open View Client and connect to the View Connection Server.

3. Log in as View user B, as recorded in “Preparing for the lab.”

4. Try to connect to Sales-XP. If vCenter Server has not finished deploying the second virtual machine from the template, you will see a message that the desktop is not available. Retry the connection after verifying that the desktop is available.

5. After you confirm that both desktops are active—a desktop appears in each client virtual machine—log out of both virtual desktops (Start > Log Off). Logging out disconnects the desktop.

6. Switch to the View Administrator window and select Inventory > Desktops. The <ESXi_host_name>-Sales desktops are present and their status is Available. Notice the association of each user to each desktop. Each desktop in Pool-Sales-XP is dedicated to a specific user.



Task 5: Delete the automated pool

In this task, you will delete the automated pool that was created in task 2.

1. Use View Administrator to disable provisioning on the persistent desktop pool that you created in task 2:

a. In View Administrator, select Inventory > Pools.

b. Select the Pool-Sales-XP row. Click Status and select Disable Provisioning. Click OK when prompted. This operation does not affect current provisioning but will halt future provisioning. The pool will remain enabled and users can log in to existing desktops.

c. Verify this action by double-clicking Pool-Sales-XP in the ID column and reviewing its Settings tab. Provisioning is disabled.

d. Click the back arrow (in the upper left of the View Administrator window, not in Internet Explorer) to return to the Pools page.

2. Use the following steps to delete the pool and its virtual machines:

a. Select the Pool-Sales-XP row and click Delete.

b. Select Delete VMs from disk and click OK. After you click OK, the deletion cannot be stopped.

3. Monitor the task sequence in the Recent Tasks pane of the vCenter Server system. The two virtual machines are deleted and then the Pool-Sales-XP folder is deleted.

Estimated time: 25 minutes. This lab is long, mostly because it is template-based cloning. The Windows XP template has a 4GB virtual disk.

Task 2, step 10: Remind students to use the datastore specified in the configuration sheets (for example, SharedVMs).


8

Lab 8 Role-Based Delegated Administration 39

Lab 8

Role-Based Delegated Administration :

Objective: Create View user permissions


1. Create a View folder.

2. Move a pool into a new folder.

3. Modify permissions on a folder.

4. Verify permissions on a folder.

5. Use global permissions to allow a user or group limited access to the View environment.

6. Remove all administrator permissions.

Preparing for the lab

Record the following information:



View user name A


View user name B



40 Lab 8 Role-Based Delegated Administration

Task 1: Create a View folder

In this task, you will create a View folder. Role-based delegated administration applies to a folder of pools, so one or more folders must exist. A unique folder is created in this task so that a role can be associated with a specific pool.

1. Connect to View Administrator, by typing cs-<ESXi_host_name>/admin and the View administrator credentials that you recorded in “Preparing for the lab.”

2. In View Administrator, select View Configuration > Administrators.

3. On the Global Administrators page, click the Folders tab.

4. Click Add Folder. Use these values to complete the entries in the Add Folder dialog box. Click OK when finished.

5. Verify that the folder was created and appears beneath the root (/) folder.

Task 2: Move a pool into a new folder

In this task, you will move a pool into the Consultant desktops folder. When the pool was created, it was placed in the Marketing desktops folder.


2. On the Pools page, in the ID column, double-click Marketing-XP to display the details about the pool.

3. On the Marketing-XP page, click the Settings tab and click Edit.

4. On the Edit Marketing-XP page, click the General tab. In the View Folder drop-down menu, select Consultant desktops. Click OK.

5. Verify in the General pane of the Settings tab that View Folder shows Consultant desktops.

6. Click the back arrow to return to the Pools page.

Field/Setting Value

Name Type Consultant desktops.

Description Type Folder for desktops assigned to Consultants.


8


Task 3: Modify permissions on a folder

In this task, you will modify permissions on the Consultant desktops folder. Permissions are assigned to a user name by associating the user name with a folder and selecting a role for the user-folder combination. The role must already exist and must include the appropriate permissions.


2. On the Global Administrators View page, click the Folders tab.

3. Select the Consultant desktops folder that is shown below the root (/) folder.

4. On the Global Administrators View page, click Add Permission.

5. On the Add Permission page, click Add.

6. On the Find User or Group page, in the Name/User name text box, enter the View user name A that you recorded in “Preparing for the lab.” Click Find.

7. Select the user name and click OK.

8. On the Add Permission page, click Next.

9. On the Add Permission (Select a Role) page, select Inventory Administrators. All the roles shown on this page apply to folders. Click Finish.

10. Verify that the Consultant desktops folder now has your View user name A in the Administrator column and has the Inventory Administrator role assigned to it.

Task 4: Verify permissions on a folder

In this task, you will verify permissions on a folder. When granting the permissions in the role associated with View user A, certain pool operations will be dimmed. You are not allowed to perform these operations.

1. Log out of View Administrator if you are currently logged in. Click Logout in the upper-right corner of the View Administrator page.

2. Log in to View Administrator with the View user A credentials that you recorded in “Preparing for the lab.”


4. In the list of pools on the Pools page, verify that only the Marketing-XP pool is displayed. You see only the pools that were moved into the Consultant desktops folder. Select the pool and review the operations that you are allowed to perform on the pool.

Are any options dimmed? _______________________________________________

Are all View objects, such as ThinApps, visible in the left navigation pane? _______



Can you select the View Configuration options? ____________________________

5. Log out of View Administrator.

Task 5: Use global permissions to allow a user or group limited access to the View environment

In this task, you will use global permissions to limit the access that a user or group has in the View environment. This task shows that some permissions and roles apply to the entire View inventory rather than to just a folder. A role that has global administrator permissions will be added to a View user.

1. Log in to View Administrator with the View administrator credentials that you recorded in “Preparing for the lab.”


3. On the Global Administrators View page, click the Administrators and Groups tab.

4. In the Administrators and Groups tab, click Add User or Group.

5. On the Add Administrator or Permission page, click Add.

6. On the Find User or Group page, in the Name/User name text box, enter the View user name B that you recorded in “Preparing for the lab.” Click Find.

7. Select the user name and click OK.

8. On the Add Administrator or Permission page, select the user and click Next.

9. Select the Global Configuration and Policy Administrators (Read Only) role and click Finish.

10. On the Global Administrators page, compare the permissions information for View user A and View user B.


12. Log in to View Administrator with the View user B credentials that you recorded in “Preparing for the lab.”

13. Explore the effect of this global administrator role in the View Administrator interface. For example, are you able to see and review any of the pools?

Can you add or modify a pool? ___________________________________________

Can you update the View license serial number? _____________________________

Are you able to select all the options under View Configuration? If you cannot, what is missing?_____________________________________________________________



8


Task 6: Remove all administrator permissions

In this task, you will remove all role-based administrator permissions so that they will not cause an unexpected result in later labs.

1. Log in to View Administrator with the View administrator credentials that you recorded in “Preparing for the lab.”


3. In the Global Administrators View page, select each View user name and click Remove User or Group. Click OK when asked to confirm the remove operation.

Estimated time: 15 minutes.

Task 5, step 13: This global role is read-only and does not apply to any folders. So pools, desktops, and other Inventory objects are not visible. The missing items under View Configuration are Administrators, ThinApp Configuration, and Transfer Server Repository.




9

Lab 9 Installing View Composer 45

Lab 9

Installing View Composer :

Objective: Install View Composer on the vCenter Server system


1. Prepare the vCenter Server system for View Composer.

2. Install View Composer on the vCenter Server system.






46 Lab 9 Installing View Composer

Task 1: Prepare the vCenter Server system for View Composer

In this task, you will prepare the vCenter Server system for View Composer by creating a system data source name (DSN).

1. Start a Remote Desktop Connection session to your vCenter Server system and log in as Administrator. You recorded the FQDN of the vCenter Server system and the Administrator password in “Preparing for the lab.”

2. Create a DSN for the View Composer database (Start > Programs > Administrative Tools > Data Sources (ODBC)).

3. Click the System DSN tab. Verify that there is already a DSN for the vCenter Server database. Click Add.

4. Select SQL Native Client from the list and click Finish. The Create a New Data Source to SQL Server wizard appears.

5. On the Create a New Data Source to SQL Server page, use the following values.

6. For How should SQL Server verify the authenticity of login ID, accept the default With Integrated Windows authentication. Click Next.

7. Select Change default database to and then select ViewComposerDB from the drop-down menu. Accept all other defaults and click Next.

8. On the last page of the wizard, accept all defaults and click Finish.

9. In the ODBC Microsoft SQL Server Setup dialog box, click Test Data Source. A dialog box that says, “TESTS COMPLETED SUCCESSFULLY!” should appear. If it does not, back up through the pages of the ODBC Add wizard and verify that you entered the information correctly.

10. Click OK to return to the ODBC Data Source Administrator page. Verify that your new data source appears in the list of system DSNs. If it does appear, click OK to close the window. Do not close the Remote Desktop session. You will to use it in the next task.

Field/Setting Value

Name (ODBC identifier) Type ComposerDB.

Description Type View Composer Database.

SQL Server Select (local). Click Next.


9

Lab 9 Installing View Composer 47

Task 2: Install View Composer on the vCenter Server system

In this task, you will install View Composer on the vCenter Server system.

1. Select Start > Run and enter the UNC for the course files network share, as recorded in “Preparing for the lab.”

2. Copy VMware-viewcomposer-<build>.exe from the shared folder to the desktop. Open the copy on the desktop to start the installation.

View Composer requires Microsoft .NET 3.5 SP1. If necessary, the View Composer installer will prompt you to install this application before it continues.

3. On the End User Patent Agreement page, click Next.

4. On the License Agreement page, accept the VMware license terms and click Next.

5. On the Destination Folder page, accept the destination folder path and click Next.

6. On the Database Information page, enter the data source name (the ODBC ID) that you created in task 1. Type Administrator for the user name and vmware for the password. Click Next.

7. On the VMware View Composer Port Settings page, accept the default SOAP port. A default SSL certificate is created. Click Next.

8. On the Ready to Install the Program page, click Install to begin the installation. Because Windows Firewall has been disabled, you might see a warning from the installer that it cannot open the firewall. If so, click OK. After the installation completes, click Finish.

9. Confirm that Windows Firewall is disabled.

10. Close the remote desktop connection to the vCenter Server system.


This lab might take longer than 20 minutes, depending on whether .NET 3.5 SP1 is already installed on the vCenter Server system and how much I/O contention exists on the local datastore because of the concurrent installation of three View Composer instances. The 3.5 version of .NET should be preinstalled on each of the vCenter Server virtual machines. If the lab progresses slowly, after the students click Install, you can ask them to monitor for completion while you return to lecturing.


48 Lab 9 Installing View Composer


10

Lab 10 Deploying Linked-Clone Desktops 49

Lab 10

Deploying Linked-Clone Desktops :

Objective: Create a parent virtual machine and deploy linked-clone desktops


1. Take a baseline snapshot from the parent virtual machine.

2. Enable View Composer and authorize the View administrator for use by QuickPrep.

3. Create an automated pool of linked-clone desktops.

4. Test an individual linked-clone desktop.





Active Directory (AD) domain name




50 Lab 10 Deploying Linked-Clone Desktops

Task 1: Take a baseline snapshot from the parent virtual machine

In this task, you will configure a Windows 7 virtual machine to be the parent virtual machine for a pool of linked-clone desktops. After completing the configuration of the parent virtual machine, you will take a snapshot, which View Composer uses to create the linked clones.

1. Use the VMware vSphere® Client™ to connect to the vCenter Server system. Log in as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Open a remote console to the par-<ESXi_host_name> virtual machine and log in as Administrator, using the password recorded in “Preparing for the lab.”


a. Click Start, right-click Computer, select Properties, and click Change settings. Click Change.

b. Select Member of Domain and specify the AD domain that you recorded in “Preparing for the lab.” When prompted, enter the View administrator user name and password that you recorded in “Preparing for the lab.”

c. When prompted, restart the virtual machine.

d. Log in to the domain with the View administrator user name and password that you recorded in “Preparing for the lab.”


Local datastore

Datastore for replica disks

AD container distinguished name


View user name A


View user name B



10


4. Install VMware View Agent:

a. Click Start. In the Search box, enter the UNC for the course files network share, recorded in “Preparing for the lab.”

b. Copy VMware-viewagent-<build>.exe from the shared folder to the desktop. Open the copy on the desktop to start the installation.

c. In the User Account Control window, click Yes to continue.

d. Click Next to continue the installation

e. Click Next to accept the end user patent agreement.

f. Accept the license agreement. Click Next.

g. Accept the default installation of five View Agent components: USB Redirection, View Composer Agent, Virtual Printing, PCoIP Server, and View Persona Management. Click Next.

h. If prompted, accept the default setting for Enable the Remote Desktop Capability on this computer. Click Next.

i. Click Install.

j. Click Finish when the installation is complete.

5. Verify that Windows Firewall is disabled. (Type services.msc in the Search box.)

6. Restart the parent virtual machine.

7. Log in again as the View administrator.

8. Verify that no profiles exist for either of your unprivileged View users. Delete folders in C:\Users for either View user A or View user B.

9. Release the DHCP-assigned IP address. Type ipconfig /release in the Search box.

10. Shut down the virtual machine (Start > Shut Down).

11. After the virtual machine has completely shut down, take a baseline snapshot. Click the snapshot icon at the top of the remote console window. In the Name box, type Baseline. Enter a description of your choice. The icon will change color for a few seconds while the snapshot is taken.

12. Click the snapshot manager icon to verify that the snapshot was successful.

13. Close the remote console window.



Task 2: Enable View Composer and authorize the View administrator for use by QuickPrep

In this task, you will enable View Composer and authorize a View administrator account for use by QuickPrep. The View administrator account must have domain join and remove permissions.

1. If you are not already connected to View Administrator, start Internet Explorer and log in to View Administrator with your View administrator credentials.

2. In View Administrator, select View Configuration > Servers.

3. In the vCenter Servers pane, select your vCenter Server system and click Edit.

4. In the View Composer Settings pane of the Edit vCenter Server page, click Enable View Composer.

5. Click Add to add the View administrator account that QuickPrep should use. Enter the full domain name, the View administrator user name, and the password that you recorded in “Preparing for the lab.”

6. After the credentials are verified and appear in the Domains list, click OK to close the Edit vCenter Server page.

Task 3: Create an automated pool of linked-clone desktops

In this task, you will create an automated pool of linked-clone desktops and entitle the desktops for all View users.


2. On the Pools page, click Add to start the Add Pool wizard.

3. On the Type page, select Automated Pool.

4. On the User Assignment page, select Dedicated and then select Enable automatic assignment.

5. On the vCenter Server page, select View Composer linked clones and verify that your vCenter Server system name is highlighted and that Yes appears in the View Composer column.


10


6. On the Pool Identification page, use the following values.

7. On the Pool Settings page, select Yes for Allow users to reset their desktops. Accept all other defaults and click Next.

8. On the View Composer Disks page, use the following values.

Field/Setting Value

ID Type Pool-Marketing.

Display name Type Marketing-Win7.

View folder Select Marketing desktops.

Description Type Automated pool of dedicated, linked-clone desktops for Marketing.

Field/Setting Value

Persistent Disk pane Select Redirect Windows profile to a persistent disk.

Type 512 in Disk size and select E for Drive Letter.

Disposable File Redirection pane Select Redirect disposable files to a non-persistent disk.

Type 1536 in Disk size.



9. On the Provisioning Settings page, use the following values.

10. On the vCenter Settings page, use Browse to select the following values.

Field/Setting Value

Virtual Machine Naming pane Select Use a naming pattern and type <ESXi_host_name>-{n:fixed=2}-Mkt in the Naming Pattern box.

Pool Sizing pane Type 2 in Max number of desktops box.

Select Provision desktops on demand.

Type 1 in the Min number of desktops box.

If the Add Pool wizard reports that the virtual machine naming pattern is too long, truncate your VMware ESXi™ host name to six characters, including the host number. For example, ocelot03 becomes ocel03.

Field/Setting Value

Default image For Parent VM, click Browse and select par-<ESXi_host_name>.

Select Baseline for snapshot.

VM Folder Select Training.

Hosts or Cluster Select your ESXi host.


10


11. In the AD Container box on the Guest Customization page, enter the AD container distinguished name that you recorded in “Preparing for the lab.” You must enter the AD container distinguished name exactly as recorded.

12. Verify that Use QuickPrep is selected. Click Next.

13. On the Ready to Complete page, review the settings and click Finish.

14. In the Pools page, select Pool-Marketing.

15. Click Entitlements and entitle this pool for the View users domain group that you recorded in “Preparing for the lab.”

16. Monitor the linked-clone provisioning in the Recent Tasks pane of the vSphere Client. Enable the Show View Composer virtual machines option in vCenter Server (select Edit > Client Settings) to review the activity in VMwareViewComposerReplicaFolder. This virtual machine folder is visible only in the VMs and Templates view. Examine the Pool-Marketing VM folder to confirm that the linked-clone virtual machine name conforms to the virtual machine naming pattern that you specified. Be patient: the process will take a few minutes because the replica virtual machine is created first and the Windows 7 virtual machine is large. Wait for the initial cloning to complete before going to the next task.

Resource Pool Select Desktops.

Datastores Select Use different datastore for View Composer replica disks.

Select the local datastore name that you recorded in “Preparing for the lab.” In the Use for column, select Linked clones in the drop-down menu.

Select the datastore name for replica disks that you recorded in “Preparing for the lab.” In the Use for column, select Replica disks in the drop-down menu.

Click OK.

Click Next.



Task 4: Test an individual linked-clone desktop

In this task, you will test an individual linked-clone desktop by logging in to it from the client A virtual machine.

1. Use the vSphere Client to determine how many linked-clone virtual machines have been provisioned. How many are there and is this what you expected to see?

2. Open a console to the cla-<ESXi_host_name> virtual machine and log in as Administrator.

3. Start the View Client and connect to the View Connection Server host.

4. When prompted, log in using View user name A, as recorded in “Preparing for the lab.” Select Marketing-Win7 desktop. Click Connect.

5. Verify that a user-specific folder exists on the E: drive and that the Documents shell folder has been mapped to the E: drive. (Click Start, right-click Documents, and select Properties.)

6. Change the background of your desktop so that it can be distinguished from the desktop connection to a second linked clone in the next steps. (Right-click the desktop and select Personalize.)

7. Have your partner repeat steps 1–5 with the clb-<ESXi_host_name> virtual machine and View user name B.

Keep both View desktop sessions connected. They will be used in the next lab.



11

Lab 11 Modifying Linked-Clone Desktops 57

Lab 11

Modifying Linked-Clone Desktops :

Objective: Use the recompose operation to install Foxit Reader on all linked-clone desktops in a pool


• Install Foxit Reader on all linked-clone desktops.






58 Lab 11 Modifying Linked-Clone Desktops

Task 1: Install Foxit Reader on all linked-clone desktops

In this task, you will make a global change for all linked-clone desktops. You will make the Foxit Reader application available to all users of the linked-clone pool. To minimize the effect on users who are logged in to their desktop, the new image will be incorporated into each user’s desktop only after the user has logged out.

1. In the VMware vSphere® Client™, power on the parent virtual machine.

2. Open a remote console to the parent virtual machine and log in as View administrator, using the user name and password that you recorded in “Preparing for the lab.”

3. On the parent virtual machine, open the network share for the course files, double-click the Foxit Reader MSI filename, and install the VMware ThinApp® version of Foxit Reader.

4. Start Foxit Reader to verify that it operates correctly. Close Foxit Reader.

5. Release the DHCP-assigned IP address. Type ipconfig /release in the Search box.

6. Shut down Windows 7 completely (Start > Shut down). Do not close the console window.

7. Create a second snapshot of the parent virtual machine and name it FoxitInstalled. When the snapshot completes, close the remote console window.

8. Return to View Administrator and select Inventory > Pools.

9. On the Pools page, double-click Pool-Marketing in the ID column to show the details for this pool.

10. On the Pool-Marketing page, click View Composer and select Recompose.

11. On the Image page, highlight the FoxitInstalled snapshot. Confirm that Change the default image for new desktops is selected and click Next.

12. On the Scheduling page, select Wait for users to log off, and click Next.

13. On the Ready to Complete page, click Show Details to see which users and virtual machines will be recomposed. Click Finish.

14. On the Pool-Marketing page, click the Tasks tab to see details about the recompose operation.

15. Log out from the desktop that you connected from the client B virtual machine.

16. Monitor the progress of the recompose operation in the vSphere Client. Notice that the active View Client session in client A is still running normally while the second virtual machine in the pool is being shut down and reconfigured. While you are waiting, review the activity in VMwareViewComposerReplicaFolder in the VMs and Templates inventory view. Confirm that a second replica virtual machine is created. Be patient: the process will take a few minutes because of the cloning. Also review the status of the linked-clone desktops in View Administrator. The desktop that is being reconfigured shows that it is in maintenance mode.


11

Lab 11 Modifying Linked-Clone Desktops 59

17. When the recomposed linked clone is ready for use (the desktop status will be Available), ask your partner to connect to a Marketing desktop from client B, using View user B credentials. After connecting, verify that Foxit Reader is installed and starts correctly.

18. In View Administrator, verify that the recompose operation was properly done by reviewing the Image column in the Inventory tab for Pool-Marketing.

a. On the Pools page, double-click Pool-Marketing.

b. Click the Inventory tab.

c. Click Desktops (View Composer Details). The recomposed desktop should show par-<ESXi_host_name>-FoxitInstalled as the image.

19. Return to client A and disconnect and log out of the desktop. The linked clone dedicated to View user A will be recomposed. Monitor the Recent Tasks pane in the vSphere Client to track the reconfiguration of the desktop. Notice what happens to the original replica virtual machine. Several reconfiguration steps occur, so be patient. Notice that the recompose time for this linked clone is much faster than the first one.

20. When the recompose operation completes, use client A (cla-<ESXi_host_name>) to reconnect to the Marketing desktop as View user A.

21. Verify that the desktop has Foxit Reader available. Display the contents of the Documents folder to verify that the persistent data disk was reattached to the recomposed desktop.

Keep both desktop connections open.



60 Lab 11 Modifying Linked-Clone Desktops


12

Lab 12 Managing Linked-Clone Persistent Disks 61

Lab 12

Managing Linked-Clone Persistent Disks:

Objective: Move a persistent disk from one linked clone to another linked clone


1. Detach a View Composer persistent disk from a linked-clone desktop.

2. Attach the detached persistent disk to another linked-clone desktop as a secondary disk.

3. Verify that the secondary disk is the persistent disk from the first linked-clone desktop.



VMware View™ user A name


View user B name





62 Lab 12 Managing Linked-Clone Persistent Disks

Task 1: Detach a View Composer persistent disk from a linked-clone desktop

In this task, you will detach the persistent disk from a linked-clone desktop. After the disk has been detached and moved to a datastore, the desktop will be deleted.

1. Both client A and client B should be connected to a linked-clone Marketing desktop as View user A and View user B, respectively. If they are not, establish connections to the desktops.

2. In client A, click Start and confirm that you are logged in as View user A.

3. Create a text file on the desktop and name it Testfile-A. The file is stored on the persistent disk (E:\) and will be used later to verify that you are accessing the correct persistent disk.

4. In View Administrator, select Inventory > Persistent disks.

5. On the Persistent Disks page, select the persistent disk for the first linked-clone desktop in the Marketing desktop pool. Verify that this desktop is assigned to View user A.

6. Click Detach.

7. In the Detach Persistent Disk dialog box, select Use Current datastore and click OK.

The connection to the desktop in client A closes. In View Administrator, the status for the persistent disk changes to Archiving and the status of the desktop changes to Deleting. The Recent Tasks pane in VMware vCenter Server™ displays a series of tasks as the disk is moved and the virtual machine is reconfigured and deleted. After the original desktop is deleted, a new linked clone is created to take its place.

8. Verify that the persistent disk is stored in the correct datastore:

On the Persistent Disks page, select the Detached tab and find the datastore name. Use the VMware vSphere® Client™ to browse the datastore. You will see a VMDK with “vdm-user-disk-E” in the filename. The first part of the filename corresponds to the name of the linked clone that was deleted.

Task 2: Attach the detached persistent disk to another linked-clone desktop as a secondary disk

In this task, you will attach a persistent disk to a linked-clone desktop as a secondary disk. The persistent disk has been detached and resides in the selected datastore. The disk is associated with View user A. You will attach the disk to a desktop that is dedicated to View user B, so the user assignment for the disk will have to be changed before it can be attached.

1. In View Administrator, select Inventory > Persistent disks.

2. On the Persistent Disks page, click the Detached tab. Which user is associated with the detached disk?


12

Lab 12 Managing Linked-Clone Persistent Disks 63

3. Select the persistent disk and click Edit.

4. In the Edit Persistent Disk dialog box, click Browse and find View user B. Select the row and click OK. The User box is updated. Click OK. Notice that the User column on the Persistent Disks page is updated. (This update changes the ownership of the persistent disk but does not change the user permissions on the disk. The permissions are for View user A.)

5. Select the persistent disk and click Attach.

6. On the Attach Persistent Disk page, only one choice is available: the desktop that is assigned to View user B. Select this desktop and click OK.

7. Return to client B. The desktop connection is still open from the previous lab. View Administrator has sent a message to warn that the desktop will be logged out after two minutes (the logout time configured on the Global Settings page). Close the message and disconnect and log out of the desktop. This action starts the attachment sequence.

8. On the Persistent Disks page, click the Attached tab. After a short wait, the disk appears. It is labeled SECONDARY in the Usage column. (You might need to refresh the display.) The vCenter Server Recent Tasks pane shows the tasks that are performed to attach the disk.

Task 3: Verify that the secondary disk is the persistent disk from the first linked-clone desktop

In this task, you will verify that the secondary disk is the persistent disk from the first linked-clone desktop. Although the ownership of the persistent disk was changed to View user B, the profile on the disk is still for View user A. In this task, View user B lacks permissions to access the drive contents (because they were created by View user A), so administrator credentials are initially required.

1. Return to client B and reconnect to a Marketing desktop. The desktop is the one that is assigned to View user B.

2. On the desktop, select Start > Computer and verify that two persistent disks are attached. The disk with the higher drive letter is the attached secondary disk.

3. Open the secondary disk and verify that the profile is for View user A (open the Users folder and then open the View user A folder). Access to this profile requires your View administrator credentials, as recorded in “Preparing for the lab.”


64 Lab 12 Managing Linked-Clone Persistent Disks

4. Open the Desktop folder and verify that Testfile-A is present and can be copied to the View user B desktop.

5. Disconnect and log out of the virtual desktop.


Task 3: If the second desktop does not automatically change status from Maintenance mode to Available after waiting a while, tell the students to select More Commands > Exit Maintenance Mode and then connect to the desktop.


13

Lab 13 Configuring a View Security Server 65

Lab 13

Configuring a View Security Server :

Objective: Configure a View security server and use it to connect to virtual desktops


1. Install and configure a View security server.

2. Test the operation of the View security server.

3. Configure a View security server for client access over the Internet.



VMware View™ security server IP address


View Connection Server fully qualified domain name (FQDN)

View security server FQDN

View user name A



66 Lab 13 Configuring a View Security Server

Task 1: Install and configure a View security server

In this task, you will configure a Windows 2008 virtual machine for use as a security server. The virtual machine named sec-<ESXi_host_name> in the VMware vCenter Server™ inventory will be used as the View security server.

1. Shut down the security server virtual machine: Right-click sec-<ESXi_host_name> and select Power > Shut Down Guest.

2. Use the Edit Settings wizard to configure the security server virtual machine for dual network access:

a. Confirm that network adapter 1 is adapter type E1000 and is connected to the Public port group.

b. Add a second network adapter and connect it to the Privnet port group. Select VMXNET 3 for Adapter Type. In the Device Status panel, select Connect at power on.

3. Power on the security server virtual machine, open a remote console, and log in as Administrator to confirm the network configuration. Use the password that you recorded in “Preparing for the lab.” Verify that the View security server is not a member of the domain.

4. Open a Command Prompt window and type ipconfig to determine both interface addresses.

The first network interface (the Public port group) should have an address that matches the IP address that you recorded in “Preparing for the lab.” The second network interface should be connected to the Privnet port group. It has a dynamic address on a subnet that is the Public subnet, minus 20.

5. Exit the Command Prompt window.


7. Copy VMware-viewconnectionserver-x86_64-<build>.exe from the shared folder to your desktop. Open the copy on the desktop to start the installation.

8. Click Yes in the User Account Control dialog box to proceed with the installation.



View security server remote FQDN:port

FQDN for the security server

Port number for the security server


13



12. On the Installation Options page, select View Security Server and click Next.

13. On the Paired View Connection Server page, enter your View Connection Server FQDN, as recorded in “Preparing for this lab.”

14. On the Paired View Connection Server Password page, you must enter a temporary password. Create the pairing password in View Administrator:

a. In View Administrator, select View Configuration > Servers.

b. In the View Connection Servers pane, select your connection server and click More Commands. Select Specify Security Server Pairing Password.

c. On the Specify Security Server Pairing Password page, type vmware as the password and click OK.

d. Return to the Security Server installation and enter the pairing password that you assigned (vmware). The password is a single-use password.

15. On the View Security Server Configuration page, verify that External URL is set to the host name of your security server. Verify that PCoIP External URL is the IP address of the security server with port 4172 appended. Click Next.

16. On the Firewall Configuration page, verify that Configure Windows Firewall automatically is selected and click Next.



19. Turn off Windows Firewall:

a. Select Start. Right-click Network and select Properties.

b. On the Network and Sharing Center page, select Windows Firewall (lower left corner).

c. On the Windows Firewall page, select Turn Windows Firewall on or off.

d. On the Customize Settings page, select Turn off Windows Firewall (not recommended) under Domain network location settings. Click OK.

e. Close the Windows Firewall page.

20. Close all windows on the desktop, log out, and close the remote console window.

21. In View Administrator, select View Configuration > Servers.

22. In the Security Servers pane, click the refresh icon and verify that your security server is present.

23. Select your security server and click Edit. Verify that Server name and External URL are correct. Click Cancel to close the dialog box.



Task 2: Test the operation of the View security server

In this task, you will use a client machine to test the operation of the View security server. First, tunneled connections between clients and desktops will be enabled. Then you will connect a client machine to the external Public network so that it can connect to the public side of the security server.

1. Confirm that tunneled connections are enabled between the client and entitled desktops:

a. In View Administrator, select View Configuration > Servers.

b. In the View Connection Servers pane, select your connection server and click Edit.

c. Select Use secure tunnel connection to desktop and click OK.

2. Use the VMware vSphere® Client™ to change the network connection for the client A virtual machine (cla-<ESXi_host_name>). Move the network interface from the Privnet network to the Public network. The virtual machine does not have to be powered off to make this change.

3. Log in to cla-<ESXi_host_name> as Administrator.

4. Open a Command Prompt window and type ipconfig /release. After the IP address is released, type ipconfig /renew to obtain a DHCP network address on the Public network. Minimize the Command Prompt window. You will use it later to return the network connection to Privnet.

5. Start the View Client.

6. Change the default connection server FQDN to the View security server FQDN that you recorded in “Preparing for this lab.”

7. Log in with your View user name A. You should be able to log in normally, as if you were directly connecting to your View Connection Server.

8. Connect to the Payroll-XP desktop.

9. After you verify connection to the desktop, disconnect and log out.

10. Reconnect the client machine to the Privnet port group. In the Remote Console window, select VM > Edit Settings and change the network connection for network adapter 1.

11. Maximize the Command Prompt window. Release and renew the IP address. Exit the Command Prompt window.


13


Task 3: Configure a View security server for client access over the Internet

In this task, you will configure a View security server for client access from your classroom physical desktop. The connection will be over the Internet. To enable remote access to the View security server, you must configure a suitable external URL for the security server system.

1. Return to View Administrator and select View Configuration > Servers.

2. In the Security Servers pane, select the security server and click Edit.

3. In the External URL box, enter the View security server remote FQDN:port that you recorded in “Preparing for the lab.” View users use this FQDN and port combination in the View Client to connect to the security server. Click OK.

4. Install View Client on your classroom physical desktop so that you can access View Connection Server remotely through the security server. Ask your instructor how to download the View Client installation file. You do not have to restart your system.

5. Do not enter a default connection server address during the View Client installation. You do not have to restart your system, because no new hardware is installed.

6. Start the View Client from the physical desktop.

7. In the opening window of the View Client, click Options so that you can specify the FQDN and port for the View security server.

8. Enter the FQDN and port number to access your View security server. These values are recorded in “Preparing for the lab.” Leave Use secure connection (SSL) enabled so that HTTPS will be used.

9. Click Connect and log in as View user A.

10. Select the Marketing desktop and change the display protocol to RDP. Click the circle with the down arrow and select Display Protocol > Microsoft RDP. Click Connect.

11. After you verify connection, disconnect and log out of the desktop.

12. Return to the vSphere Client and shut down the View security server virtual machine.


Task 3, step 3: You might note to the students that accessing the View security server by using the remote URL:port mimics their work environment. Typically, the only address that remote users can use to access a View Manager is an FQDN:port combination.

Task 3, step 10: For the VDC, Remote Desktop Protocol must be used to access the security server because the VDC firewall forwards inbound traffic on port 909x to sec-kitname0x:443. PCoIP would require port forwarding to sec-kitname0x:4172.




14

Lab 14 (Optional) Configuring a View Replica Server 71

Lab 14

(Optional) Configuring a View Replica Server :

Objective: Configure a View replica server and use it to connect to desktops


1. Install and configure a View replica server.

2. Test the View replica server.



Active Directory (AD) domain




View Connection Server fully qualified domain name (FQDN)


72 Lab 14 (Optional) Configuring a View Replica Server

Task 1: Install and configure a View replica server

In this task, you will configure a Windows 2003 virtual machine for use as a replica connection server. The virtual machine named rs-<ESXi_host_name> in the VMware vCenter Server™ inventory will be used to create a View replica server.

1. Power on the replica server virtual machine (rs-<ESXi_host_name>), open a remote console, and log in as Administrator.

2. Join this virtual machine to the domain, using the View administrator credentials that you recorded in “Preparing for the lab.”

3. After restarting the system, log in with the View administrator account.


5. Copy VMware-viewconnectionserver-<build>.exe (the 32-bit version) from the shared folder to the desktop. Open the copy on the desktop to start the installation.




9. On the Installation Options page, select View Replica Server and click Next.

10. For the message about requiring Windows 2008 to support the PCoIP gateway, click OK.

11. On the ADAM License Agreement page, accept the license agreement and click Next.

12. On the Source Server page, enter the View Connection Server FQDN in the Server box and click Next. The FQDN is recorded in “Preparing for the lab.” A View Connection Server group will consist of the existing View Connection Server and this replica.

13. On the Ready to Install the Program page, click Install. Monitor the database replication process.


15. Verify that Windows Firewall is disabled. If necessary, disable it.

16. Close all windows, log out, and close the remote console.

View replica server FQDN

Unprivileged View user name A

Unprivileged View user A password


14

Lab 14 (Optional) Configuring a View Replica Server 73

Task 2: Test the View replica server

In this task, you will test the View replica server by comparing View Administrator pages when you connect to the original connection server and then to the replica connection server. The pages will be identical, which verifies that, after you log in to View Administrator, the identity of the connection server that is in use is transparent.

1. Connect to View Administrator, using the View administrator credentials that you recorded in “Preparing for the lab.”

2. In View Administrator, select View Configuration > Servers. Refresh the View Connection Servers pane and notice that the replica server has been added to the list.

3. Select Inventory > Pools. Ensure that the pool with the display name of Payroll-XP has no active sessions.

4. Log in to the cla-<ESXi_host_name> virtual machine as Administrator. Use the password that you recorded in “Preparing for the lab.”

5. Start the View Client.

6. Change the address of the View Connection Server. Enter the FQDN of the View replica server, recorded in “Preparing for the lab.” You should be able to log in normally, as if you were connecting directly to the standard View Connection Server.

7. Log in as View user A and connect to the Payroll-XP virtual desktop.

8. From your Terminal Server desktop, start a second instance of Internet Explorer. Type rs-<ESXi_host_name>/admin to start a second instance of View Administrator. After you have logged in as the View administrator, notice the status for the Payroll-XP desktop in the Desktops page (Inventory > Desktops). The status is Connected.

9. In the first instance of View Administrator, verify that the Payroll-XP session information matches what you see with View Administrator connected to the replica server.

10. In the client A system, disconnect and log out of the Payroll-XP desktop.

11. Log out of both instances of View Administrator and close the Internet Explorer windows.



74 Lab 14 (Optional) Configuring a View Replica Server


15

Lab 15 Capturing Applications with VMware ThinApp 75

Lab 15

Capturing Applications with VMware ThinApp :

Objective: Use ThinApp to virtualize an application


1. Install ThinApp on a clean virtual machine

2. Do a preinstallation scan.

3. Install and configure the application.

4. Do a postinstallation scan.

5. Package the configuration.

6. Build the virtual application package.




VMware ThinApp® license key


76 Lab 15 Capturing Applications with VMware ThinApp

Task 1: Install ThinApp on a clean virtual machine

In this task, you will install ThinApp on a clean virtual machine. Applications that are to be captured by ThinApp should be installed on a clean version of the Windows operating system. The CnB virtual machine is a clean Windows XP installation and will be used as the capture-and-build machine. The ThinApp installation folder will be shared out so that certain ThinApp utilities can be accessed by test desktops. A separate shared folder will be created so that a captured application can be deployed to a test system.

1. Power on the cnb-<ESXi_host_name> virtual machine and open a remote console. Log in as Administrator, using the password that you recorded in “Preparing for the lab.”

2. Select Start > Run and enter the UNC for the course files network share, as recorded in “Preparing for the lab.” Open VMware-ThinApp-Enterprise-<build>.

3. When prompted, accept the end-user license agreement, enter the license key that you recorded in “Preparing for the lab,” and type View ICM Class in the License Display Name text box.

4. Complete the installation and exit the installer.

5. Verify that the installation was successful by checking that the ThinApp Setup Capture executable appears in Start > Programs > VMware.

6. Copy the ThinApp Setup Capture shortcut to the desktop.

7. While still in Windows Explorer (from step 2), change the folder settings to display hidden files and file extensions:

8. In Windows Explorer, share the ThinApp installation folder for access by the Windows 7 virtual machines:

a. Go to C:\Program Files\VMware\.

b. Right-click the VMware ThinApp folder and select Sharing and Security.

c. (If present) Click If you understand the security risks, but want to share files without running the wizard, click here.

d. (If present) In the Enable File Sharing window, select Just enable file sharing.

e. In the Sharing tab, select Share this folder on the network.

f. Click OK.

g. Click Yes to the warning about filename length.

h. Close all windows.


15


9. Create a shared folder named SharedApps on the CnB desktop:

a. Create a folder and name it SharedApps. Move the folder to the edge of the desktop.

b. Right-click the folder and select Sharing and Security.

c. Select Share this folder on the network. Click OK.

10. Click the Snapshot icon in the row of icons at the top of the remote console window (the clock icon with the asterisk) to take a snapshot of the virtual machine while it is still powered on. In the Name box, type CleanImage.

You should take a snapshot of the clean virtual machine before using the ThinApp Setup Capture wizard. A snapshot allows you to quickly restore the virtual machine to its clean state, preparing it to capture another application.

Leave the remote console open.

Task 2: Do a preinstallation scan

In this task, you will copy the Firefox installation file to the desktop and perform a preinstallation scan of the operating system. The Setup Capture wizard will take a baseline snapshot of your capture environment, including Registry, file system, and other environment attributes. Because the installation file will be present in both system scans, it will not be included in the final package.

1. If necessary, open a remote console to the cnb-<ESXi_host_name> virtual machine and log in as Administrator, with the password that you recorded in “Preparing for the lab.”

2. Copy the Firefox installation file from the network share for the course files:

a. Select Start > Run and enter the UNC for the course files network share, as recorded in “Preparing for the lab.”

b. Copy the Firefox installation file to the desktop. It will be used in the next task.

c. Close Windows Explorer.

3. Start the ThinApp Setup Capture wizard from the desktop.

4. On the welcome page, click Next.

5. On the Ready to Prescan page, click Prescan.

6. When the prescan completes (the wizard is at the Install Application page), minimize the Setup Capture wizard.



Task 3: Install and configure the application

In this task, you will install and configure Firefox. Applications installed at this step in the wizard will be discovered when the Setup Capture wizard compares ThinApp snapshots taken before and after this task.

1. Open the Firefox installation file on the desktop to install the Firefox browser. Keep all defaults and complete the setup wizard. Allow the installer to open the Firefox browser so that a complete installation is confirmed. Do not import settings or data from Internet Explorer.

2. Verify correct installation by going to http://www.vmware.com.

3. Close the Firefox browser. When prompted, do not save browser pages.

Task 4: Do a postinstallation scan

In this task, you will do a postinstallation scan of the operating system. The Setup Capture wizard takes another snapshot of the Registry, file system, and environment attributes. The Setup Capture wizard compares this snapshot with the snapshot taken in task 1. It stores the file system differences in the virtual file system and the Registry differences in the virtual registry. The virtual file system and the virtual registry are included in the final package.

1. Restore the Setup Capture-Install Application page that you minimized earlier.

2. Click Postscan.

3. When prompted to confirm the application installation, click OK.

Task 5: Package the configuration

In this task, you will save the Firefox configuration. After all the options have been configured, the Setup Capture wizard saves the files and Registry keys associated with the captured application to the project folder.

1. On the Entry Points page, ensure that only Mozilla Firefox.exe is selected. Click Next.

2. On the Groups page, click Next.

3. On the Isolation page, click Next.

4. On the Sandbox page, click Next.

5. On the Quality Assurance Statistics page, click Next.

6. On the Native Browser Redirection page, click Next.

7. On the Project Settings page, click Next.

8. On the Package Settings page, click Save. ThinApp will create and save the project.


15


Task 6: Build the virtual application package

In this task, you will build the virtual Firefox package. The Setup Capture wizard combines the files gathered in task 4 into an executable that will be distributed to end users.

1. On the Ready to Build page, click Open project folder to view the project folders and files created in the previous tasks. (If hidden files and file extensions are not already visible, change the Windows Explorer options to display them.)

Which Registry hives were changed during the Firefox installation?______________

Which folder in the project retains the changes to the Program Files folder on the native system? _____________________________________________________________

2. Close Windows Explorer and return to the Ready to Build page.

3. Click Build for ThinApp to create the bin folder and build the package.

4. When the message “Build Complete” appears in the Build output pane, click Finish to exit the Setup Capture wizard. The package, which is named Mozilla Firefox.exe in the bin folder, is ready to deploy.





16

Lab 16 Deploying an Application Captured with VMware ThinApp 81

Lab 16

Deploying an Application Captured with VMware ThinApp :

Objective: Deploy and update a virtualized application with ThinApp


1. Deploy the Firefox package to a desktop.

2. Use the sbmerge.exe utility to update the Firefox package.






82 Lab 16 Deploying an Application Captured with VMware ThinApp

Task 1: Deploy the Firefox package to a desktop

In this task, you will deploy the virtualized version of the Firefox application to a desktop.

1. If the bin folder for the VMware ThinApp® Firefox project is not open on the desktop of cnb-<ESXi_host_name>, navigate to the project folder and open the bin folder. The default location for project folders is C:\Program Files\VMware\VMware ThinApp\Captures\.

Record your project folder name: _________________________________________

2. Copy the Firefox executable from the bin folder of the project to the SharedApps folder.

3. In the SharedApps folder, rename the executable to Firefox.exe. Minimize the Windows Explorer windows. You will use them later.

4. From the client A machine (cla-<ESXi_host_name>), log in to the View Connection Server and connect to Payroll-XP, using your View user A credentials, as recorded in “Preparing for the lab.”

5. Verify that Firefox is not installed on this desktop.

6. Connect to the SharedApps folder, using a UNC of the form \\cnb-<ESX/ESXi_host_name>\SharedApps. If necessary, connect as Administrator, using the Administrator password that you recorded in “Preparing for the lab.”

7. In Windows Explorer, double-click Firefox.exe to start the Firefox browser. Accept the security warning. It might take a few moments for ThinApp to set up the sandbox folder the first time that it starts the application.

8. Verify that the Firefox browser starts successfully.

9. Close the browser.

Task 2: Use the sbmerge.exe utility to update the Firefox package

In this task, you will use the sbmerge.exe utility to update the Firefox application. The VMware support toolbar add-on will be installed and included in the ThinApp Firefox package. After the package is updated, it will be deployed to the end-user desktops.

1. Return to the desktop of cnb-<ESX/ESXi_host_name>.

2. Click Start and type %AppData%\Thinstall\ in the Run box. By default, the Thinstall folder holds all sandbox folders (Thinstall is the legacy name for ThinApp). ThinstallBuilder should be the only folder present. Delete any other folders.

3. Switch back to the Windows Explorer window that shows the bin folder for the project (C:\Program Files\VMware\VMware ThinApp\Captures\Mozilla Firefox (3.x)\bin). From the bin folder (not from SharedApps or the desktop), start Mozilla Firefox.exe. Return to the Windows Explorer window that you opened in step 2 that shows


16

Lab 16 Deploying an Application Captured with VMware ThinApp 83

the contents of the %AppData%\Thinstall folder. Notice that a sandbox folder has been created for the Firefox application.

4. Install the VMware support toolbar:

a. Bring the Firefox browser window to the front.

b. Go to vmwaresupport.toolbar.fm and download the add-on. Allow Firefox to download the file.

c. In the Software Installation window, click Install Now.

d. Restart the Firefox browser when prompted.

e. When prompted to configure settings, click Finish.

f. Confirm that the toolbar is installed.

g. Close the Firefox browser window and the Add-on window.

5. Open a Command Prompt window and edit the PATH variable to include the location of the ThinApp executables, which include sbmerge.exe. At the command prompt, type:

PATH=%PATH%;C:\Program Files\VMware\VMware ThinApp\

Type PATH to verify the correct entry of the change.

6. At the command prompt, change directory to the Firefox project folder in the Captures folder, which is C:\Program Files\VMware\VMware ThinApp\Captures\Mozilla Firefox (3.x)\.

7. To update the captured application with the changes recorded in the sandbox, run the following command:

sbmerge Apply

8. At the command prompt, type build.bat to re-create the executable. When the build completes, close the Command Prompt window. Return to the Windows Explorer window displaying the sandbox folders (%AppData%\Thinstall) and verify that the Mozilla Firefox sandbox folder has been deleted.

9. Return to the Windows Explorer window that shows the bin folder in your project. Notice that there is only one executable in the folder. The build.bat script overwrote the original when you built the new version. Copy this new executable from the bin folder of your project to the SharedApps folder.

10. Rename the updated copy in SharedApps to FirefoxToolbar.exe. In a production environment, the administrator would rename the new executable with the same name as the old one so that existing shortcuts remain valid for the end user.

11. Return to the virtual desktop that is displayed in cla-<ESX/ESXi_host_name>.


84 Lab 16 Deploying an Application Captured with VMware ThinApp

12. From the SharedApps folder, start the original executable, Firefox.exe.

13. Verify that the VMware support toolbar is not installed. Exit the browser.

14. Click Start and type %AppData%\Thinstall\ in the Run box. Delete the Mozilla Firefox sandbox folder. Close Windows Explorer.

15. Start the new executable, FirefoxToolbar.exe. In this version, the VMware support toolbar is installed. The Firefox executable has been updated.

16. Close all windows in the virtual desktop. Disconnect and log out.

17. Log out and close all client virtual machines, but leave the cnb-<ESX/ESXi_host_name> virtual machine active.


Task 2: Students might observe that it would be easier and quicker to recapture the Firefox application with the plug-in installed. For this lab, that is true. Indeed, the ease of capturing an application is one of the appealing features of ThinApp. But not all applications are so easily or quickly virtualized. If an application has multiple executables or many supplementary files, it might be easier to update it using this process. Also, there might not be a suitable snapshot of the capture machine that applies to this application. The purpose of this task is to demonstrate the sbmerge.exe utility. In a production environment, integer updating or the Application Sync utility would be used. These methods are more flexible than the sbmerge.exe utility.


17

Lab 17 Packaging Internet Explorer 6 with VMware ThinApp 85

Lab 17

Packaging Internet Explorer 6 with VMware ThinApp :

Objective: Use ThinApp to package Internet Explorer 6 and configure browser redirections


1. Package Internet Explorer 6 with ThinApp.

2. Install the VirtIE6 package on the Windows 7 parent virtual machine and confirm that it operates correctly.

3. (Optional) Recompose the linked-clone pool and verify the operation of the IE 6 package on a desktop.





View administrator user password

View user name A



86 Lab 17 Packaging Internet Explorer 6 with VMware ThinApp

Task 1: Package Internet Explorer 6 with ThinApp

In this task, you will package Internet Explorer 6 with VMware ThinApp®. ThinApp provides an option to package Internet Explorer 6 from the CnB machine. Automatic redirection of Web sites or Web pages from the native Internet Explorer browser to Internet Explorer 6 can also be configured.

1. If necessary, open a remote console to the cnb-<ESX/ESXi_host_name> virtual machine and log in as Administrator, with the password that you recorded in “Preparing for the lab.”

2. In the remote console window revert the CnB machine to the CleanImage snapshot so you start with a clean version of the system.

3. Start the ThinApp Setup Capture wizard from the desktop.

4. On the welcome page of the wizard, click Next.

5. On the Ready to Prescan page, click Prescan.

6. On the Install Application page, click Internet Explorer.

7. On the Internet Explorer Entry Points page, select Include an entry point for a fully virtualized Internet Explorer and click OK.

8. On the Install Application page, click Postscan. When prompted to confirm the application installation, click OK.

9. On the Entry Points page, click Next. The VirtIE6 entry point will be selected and cannot be deselected because of the choice that was made in step 7.

10. On the Groups page, click Next.

11. On the Isolation page, click Next.

12. On the Sandbox page, click Next.

13. On the Quality Assurance Statistics page, click Next.

14. On the Native Browser Redirection page, type the following addresses for redirection to Internet Explorer 6 and click Next:

www.vmworld.com

*.google.com

15. On the Project Settings page, click Next.

16. On the Package Settings page, click Save. ThinApp creates and save the project.

17. On the Ready to Build page, click Build for ThinApp to create the bin folder and build the package.


17


18. When the message “Build Complete” appears in the Build output pane, click Finish to close the Setup Capture wizard. The package is ready to deploy.

19. Copy VirtIE6.exe from the project bin folder to the SharedApps folder.

Task 2: Install the VirtIE6 package on the Windows 7 parent virtual machine and confirm that it operates correctly

In this task, you will install the VirtIE6 package on the Windows 7 parent virtual machine and confirm that it operates correctly. The parent Windows 7 virtual machine will be updated to include the VirtIE6 package so that the linked-clone pool can be recomposed to update all linked-clone desktops with this new capability. For the ThinDirect redirection to be properly set up, the thinreg.exe utility must be run with the VirtIE6 executable. This utility registers the application and installs the ThinDirect plug-in in the Windows 7 native Internet Explorer.

1. From the VMware vSphere® Client™, power on the parent Windows 7 virtual machine.

2. Open a remote console and log in with your View administrator credentials.

3. On the Windows 7 desktop, click Start. In the Search box, type \\<cnb-<ESX/ESXi_host_name>\SharedApps to connect to the folder.

4. Copy the VirtIE6 executable from the SharedApps folder to C:\Program Files\VMware on the Windows 7 system.

5. Map a network drive to the shared VMware ThinApp installation folder on the CnB machine to access the thinreg.exe utility from a command prompt:

a. Select Start > Computer.

b. On the menu bar, click Map network drive.

c. Select the Z:\ drive in the Drive drop-down menu.

d. In the Folder box, type \\<cnb-<ESX/ESXi_host_name>\VMware ThinApp.

e. Select Reconnect at logon.

f. Click Finish.

6. In a Command Prompt window, use the thinreg.exe utility to register VirtIE6 and install the ThinDirect plug-in:

a. Open a Command Prompt window.

b. Change directory to C:\Program Files\VMware.

c. Run Z:\Thinreg /a VirtIE6.exe to make the executable available for all users.

d. Close the Command Prompt window.



7. On the Windows 7 desktop, start Internet Explorer and verify that it is version 8 and that the ThinDirect plug-in has been installed. To confirm installation:

a. On the Internet Explorer toolbar, click Tools.

b. Select Manage Add-ons. ThinDirect Browser Helper is in the list.

c. Click Close.

8. Type www.google.com in the address box. You will see:

• A message from ThinDirect saying that it has been activated for the page that you entered and that is has opened the page in another browser instance. The browser instance will be Internet Explorer 6 because that was the browser that you captured earlier. You could have captured Firefox, Chrome, or another browser, instead.

• A dialog box asking if you want to make Internet Explorer your default browser. This question is from Internet Explorer 6 on the first startup. Click No. You will then see an Internet Explorer 6 window that displays http://www.google.com. Confirm that this browser is Internet Explorer 6.

9. Go to http://www.yahoo.com in the Internet Explorer 6 browser. This URL was not included in the ThinDirect list, so it will be redirected to Internet Explorer 8, the native browser (the window might be hidden).

10. Close all browsers and windows.

11. Close the remote console window. Shut down the parent virtual machine from the vSphere Client. (Right-click the virtual machine name and select Power > Shut Down Guest.)

12. After the parent virtual machine has shut down, take a snapshot of the Windows 7 parent virtual machine and name it virtIE6Installed.

Task 3: (Optional) Recompose the linked-clone pool and verify the operation of the IE 6 package on a desktop

In this task, you will recompose the linked-clone pool and verify the operation of the IE 6 package on a desktop. The Marketing automated pool (Pool-Marketing) will be recomposed to update all the linked-clone desktops to use the new version of the parent virtual machine, which includes the VirtIE6 package. The ThinDirect capability will be tested on a Windows 7 linked-clone desktop.


2. On the Pools page, double-click Pool-Marketing in the ID column to show the details for this pool.

3. Click View Composer and select Recompose.

4. On the Image page, highlight the virtIE6_installed snapshot, select Change the default image for new desktops, and click Next.


17


5. On the Scheduling page, select Wait for users to log off, and click Next.

6. On the Ready to Complete page, click Show Details to see which users and virtual machines will be recomposed. Click Finish.

7. Disconnect and log out any desktop sessions in either client A or client B. Monitor the progress of the recomposition in the vSphere Client.

8. Review the status of the linked-clone desktops: Select Inventory > Desktops and double-click the desktop name. A desktop that is being reconfigured shows a status of Maintenance mode.

9. When the recomposed linked clone is ready for use (the desktop status will be Available), connect to a Marketing desktop, using View user A credentials as recorded in “Preparing for the lab.”

10. In View Administrator, verify that the recompose operation was properly done by reviewing the Image column in the Inventory tab for Pool-Marketing:

a. Select Inventory > Pools.

b. On the Pools page, double-click Pool-Marketing.

c. Select Inventory and click Desktops (View Composer Details). The recomposed desktop should show parent-<ESX/ESXi_host_name>- virtIE6Installed as the image.

11. Start Internet Explorer from the Windows 7 desktop.

12. Type www.google.com in the address bar.

13. Verify that the home page is redirected to an Internet Explorer 6 browser.

14. Close all browsers. Disconnect and log out of the desktop.

Time estimate: 30 minutes.

Depending on your class timing, you can make task 3 optional. Tasks 1 and 2 are required. They illustrate a key feature of the VMware migration strategy for Windows 7.




18

Lab 18 Accessing VMware ThinApp Applications with View Desktops 91

Lab 18

Accessing VMware ThinApp Applications with View Desktops :

Objective: Configure virtual desktop access to ThinApp applications


1. Configure the ThinApp application repository.

2. Scan and install ThinApp MSI packages on selected desktops.

3. Confirm the installation of the virtualized Foxit Reader application.

4. Remove the virtualized Foxit Reader application from a desktop.









92 Lab 18 Accessing VMware ThinApp Applications with View Desktops

Task 1: Configure the ThinApp application repository

In this task, you will configure the VMware ThinApp® application repository. ThinApp MSI packages that will be installed using View Manager must reside in a network share that can be accessed by View Administrator and any desktop on which a ThinApp package will be installed.

1. If you are not already logged in to the cs-<ESXi_host_name> virtual machine, use Remote Desktop Protocol to log in with your View administrator credentials.

2. Create a folder named ThinAppRepository on the cs-<ESXi_host_name> desktop and share it:

a. Create a folder on the desktop and name it ThinAppRepository.

b. Right-click the folder and select Properties.

c. In the Sharing tab, click the Advanced Sharing button and select the Share this folder check box. Click OK.

d. Click the Security tab and click Edit. Add the Domain Computers and ViewUsers groups to the list of group and user names. Verify that both groups have read and execute permissions.

e. Close the Properties dialog box.

3. Copy the Foxit Reader and FileZilla files from the course files network share to the ThinAppRepository folder. Copy both the MSI and EXE files for each application.

4. Return to View Administrator and select View Configuration > ThinApp Configuration.

5. On the ThinApp Configuration page, click Add Repository.

6. In the Add Application Repository dialog box, enter the following values. Click Save when finished.

Field/Setting Value

Display name Type ThinApp applications.

Share path Type \\cs-<ESXi_host_name>\ThinAppRepository.

Description Type ThinApp repository.


18

Lab 18 Accessing VMware ThinApp Applications with View Desktops 93

Task 2: Scan and install ThinApp MSI packages on selected desktops

In this task, you will scan ThinApp MSI packages and install one on a desktop. The scanning step determines which ThinApp packages are suitable for installation by View Manager. In this task, the virtualized version of Foxit Reader will be installed to a desktop. As soon as the assignment is made to the desktop, the installation occurs. If the assignment is to a pool, View Manager installs the package on each desktop when the assigned user next logs in.

1. In View Administrator, select Inventory > ThinApps.

2. On the ThinApps page, click Scan New ThinApps.

3. On the Scan New ThinApps page:

a. In the ThinApp repository drop-down menu, select the ThinApp repository that you set up in task 1.

b. In the Folder to scan box, select the network share for the ThinAppRepository folder.

c. Click Next.

4. On the Scan New ThinApps page, select all MSI files and click Scan.

5. When scanning is complete, verify that the MSI files have been added. The Status column displays Added for each file. Click Finish.

6. On the ThinApps page, highlight Foxit Reader, click Add Assignment, and select Desktops.

7. On the Add Desktop Assignment – Foxit Reader page, select the dt1-<ESXi_host_name> desktop and click Add. Select Streaming for Installation type and click OK.

8. On the ThinApps page, double-click Foxit Reader.

9. On the Foxit Reader page, click the Assignments tab. Double-click the desktop name to review the installation status. The name of the assigned ThinApp is listed in the ThinApps pane, with the UNC of the repository and the installation status. Refresh the display to update the status.

10. On the ThinApps page (Inventory > ThinApps), double-click Foxit Reader.

11. On the Foxit Reader page, click the Desktops tab to see all desktops that have this application installed.


94 Lab 18 Accessing VMware ThinApp Applications with View Desktops

Task 3: Confirm the installation of the virtualized Foxit Reader application

In this task, you will confirm the installation of the virtualized Foxit Reader application by logging in to the designated desktop and starting it.

1. Return to the client A desktop and start View Client.

2. Log in to the View Connection Server as View user A and select the Payroll-XP desktop.

3. Select Start > All Programs and verify that Foxit Reader appears as a recently installed program. Right-click the shortcut, select Properties, and verify that the EXE file is located in the ThinAppRepository share.

4. Connect to the network share for the course files and double-click the PDF file. Does Foxit Reader display the file?

5. Close all windows on the Payroll-XP desktop.

Task 4: Remove the virtualized Foxit Reader application from a desktop

In this task, you will uninstall the ThinApp Foxit Reader application from the designated desktop. The uninstallation operation occurs a few minutes after you click Remove Assignment. If the remove operation is for a pool, View Manager uninstalls the application when the user logs in to the desktop in the pool.

1. Return to View Administrator and select Inventory > ThinApps.

2. On the ThinApps page, double-click Foxit Reader.

3. On the Foxit Reader page, click the Assignments tab.

4. Select the desktop name and click Remove Assignment.

5. Confirm that the application is uninstalled. Click the Desktops tab and monitor the status of the desktop for this application. Also monitor the desktop itself. The application is uninstalled while the desktop is connected. The Foxit Reader shortcut disappears.

6. Disconnect and log out of the virtual desktop.


Would it be a good practice to deploy ThinApp versions of applications to linked-clone pools? No, because they would be installed in the linked-clone system disk and would be lost on the first recompose, rebalance, or refresh operation. The only way to make the ThinApp application persist is to install it on the parent virtual machine and then recompose the linked-clone pool. Several automated systems exist for deploying applications to full desktops, such as Alteris or using GPOs.
