VMware VC-VLM4-C - vCenter Lab Manager User Manual

User guide

page of 180

/ 180
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual

Lab Manager User's Guide

vCenter Lab Manager 4.0

This document supports the version of each product listed and

supports all subsequent versions until the document is replaced

by a new edition. To check for more recent editions of this

document, see http://www.vmware.com/support/pubs.

EN-000173-01

Table of Contents

Need help?

Do you have a question about the VC-VLM4-C - vCenter Lab Manager and is the answer not in the manual?

Questions and answers

Summary of Contents for VMware VC-VLM4-C - vCenter Lab Manager

Page 1 Lab Manager User’s Guide vCenter Lab Manager 4.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs. EN-000173-01...
Page 2 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.
Page 3: Table Of Contents
Create an Organization 27 Create a Workspace 28 Setting Up Network Templates 29 Create a Network Template 29 Copy a Network Template 30 Share a Network Template 30 Setting Up Virtual Machine Templates 31 Create a Virtual Machine Template 31 Importing Virtual Machine Templates 32 Import a Virtual Machine Template from vCenter 33 Import a Virtual Machine Template from SMB Storage 33 Save a Virtual Machine as a Virtual Machine Template 34 Clone a Virtual Machine Template 35 Deploying Virtual Machine Templates 35 Deploy a Virtual Machine Template with Default Settings 35 Deploy a Virtual Machine Template with Custom Settings 36 Install a Guest Operating System 36 Installing VMware Tools 36 Install VMware Tools in a Windows Guest 36 VMware, Inc.
Page 4 Complete Guest Customization for Solaris Virtual Machine Templates 43 Working with the Guest Customization SID Generation Tool 43 Select the SID Generation Tool for Lab Manager 43 Change the SID Generation Tool for a Virtual Machine Template 44 Select the SID Generation Tool for a Virtual Machine 44 Disabling Guest Customization 44 Disable Guest Customization for a Virtual Machine Template 44 Disable Guest Customization for a Virtual Machine 45 Customize Guest Customization 45 Importing Virtual Machine Templates from Lab Manager 2.x with VMware Tools and LM Tools 45 Undeploy a Virtual Machine Template 46 Share a Virtual Machine Template 46 Publishing Virtual Machine Templates 47 Check VMware Tools Status Before Publishing Virtual Machine Templates 47 Disable VMware Tools Check Before Publishing Virtual Machine Templates 47 Publish a Virtual Machine Template 47 Working with Configurations 49 Adding Configurations to a Workspace 49 Create a Workspace Configuration 50...
Page 5 Export a Configuration to vCenter 71 Export a Configuration to an SMB Share 72 Working with Virtual Machines 73 Deploying and Undeploying Virtual Machines 73 Deploy a Virtual Machine 73 Undeploy a Virtual Machine 75 Accessing Virtual Machine Consoles 75 View a Virtual Machine Console 75 View All Virtual Machine Consoles 76 Stopping and Starting Virtual Machines 76 Suspend a Virtual Machine 76 Resume a Virtual Machine 76 Power Off a Virtual Machine 76 Power On a Virtual Machine 76 Reset a Virtual Machine 77 Shut Down a Virtual Machine 77 Working with Virtual Machine Snapshots 77 Take a Snapshot of a Virtual Machine 77 Revert to a Virtual Machine Snapshot 77 VMware, Inc.
Page 6 Lab Manager User’s Guide Delete a Virtual Machine Snapshot 78 Managing Virtual Machines 78 Install VMware Tools 78 Insert and Swap a CD 78 Eject a CD 79 Insert and Swap a Floppy Disk 79 Eject a Floppy Disk 79 Create a Remote Desktop Connection File 79 Connect Remotely to a Virtual Machine 80 Modify Virtual Machine Properties 80 Modifying Virtual Machine Hard Disks 82 Add a Virtual Machine Hard Disk 82 Edit a Virtual Machine Hard Disk 82 Delete a Virtual Machine Hard Disk 83 Modifying Virtual Machine Network Interfaces 83 Edit Network Interface Settings 83 Reset a Network Interface MAC Address 84 Add a Network Interface 84 Delete a Network Interface 85...
Page 7 Reassign Ownership of a Stranded User’s Objects 112 Managing Groups 112 Remove a Group from an Organization 112 Delete a Group from Lab Manager 112 Modify Group Properties 113 Managing Roles and Rights 113 Add a Role 113 Copy a Role 114 Delete a Role 114 Modify Role Properties 114 Managing Organizations and Workspaces 115 Modifying Organization Properties 115 Modify Default User Preferences 115 Modify Default Deployment Settings 116 Modify the Users and Groups in an Organization 116 Add Members or Groups to an Organization 116 Remove Members or Groups from an Organization 116 Add or Remove the Resource Pools in an Organization 117 Add or Remove the Datastores in an Organization 117 VMware, Inc.
Page 8 Modifying Virtual Machine Template Network Interfaces 132 Add a Network Interface to a Virtual Machine Template 132 Edit a Virtual Machine Network Interface 133 Delete a Network Interface from a Virtual Machine Template 133 Reset a Virtual Machine Template Network Interface MAC Address 133 Upgrade Virtual Hardware 134 Change Ownership of a Virtual Machine Template 134 Delete a Virtual Machine Template 134 Delete a Virtual Machine Template with Force 134 Managing Lab Manager Settings 135 Configuring General Preferences 135 Change vCenter Lab Manager Preferences 135 Set Email Preferences 137 Set System Alert Preferences 137 Set Configuration Change Summary Preferences 138 Configuring LDAP Settings 138 Locate an LDAP Server 138 Set Up an LDAP Connection 139 VMware, Inc.
Page 9 General Rights 150 Group Rights 150 High I/O Rights 150 Host Rights 151 Host Spanning Transport Networks 151 Library Configuration Rights 151 Machine Rights 152 Media Rights 153 Media Store Rights 153 Network Template Rights 153 Organization Rights 154 Physical Network Rights 154 Resource Pool Rights 154 Role Rights 155 Sharing Rights 155 User Rights 156 VM Template Rights 156 Workspace Configuration Rights 157 Workspace Rights 157 VMware, Inc.
Page 10 Lab Manager User’s Guide Client and Browser Support 159 Guest Operating System Support 161 Using SSMove 163 Before You Move a Datastore 163 Move a Datastore 164 Resolving Move Errors 164 Glossary 165 Index 173 VMware, Inc.
Page 11: About This Book
Intended Audience This book is intended for VMware vSphere administrators and current Lab Manager and Stage Manager administrators. Document Feedback VMware welcomes your suggestions for improving our documentation. If you have comments, send your feedback to docfeedback@vmware.com. Technical Support and Education Resources The following sections describe the technical support resources available to you. To access the current version of this book and other books, go to http://www.vmware.com/support/pubs. Online and Telephone Support To use online support to submit technical support requests, view your product and contract information, and register your products, go to http://www.vmware.com/support. Customers with appropriate support contracts should use telephone support for the fastest response on priority 1 issues. Go to http://www.vmware.com/support/phone_support. Support Offerings To find out how VMware support offerings can help meet your business needs, go to http://www.vmware.com/support/services. VMware Professional Services VMware Education Services courses offer extensive hands‐on labs, case study examples, and course materials designed to be used as on‐the‐job reference tools. Courses are available onsite, in the classroom, and live online. For onsite pilot programs and implementation best practices, VMware Consulting Services provides offerings to help you assess, plan, build, and manage your virtual environment. To access information about education classes, certification programs, and consulting services, go to http://www.vmware.com/services. VMware, Inc.
Page 12 Lab Manager User’s Guide VMware, Inc.
Page 13: Getting Started With Lab Manager
Getting Started with Lab Manager VMware vCenter Lab Manager is an application that provides a rapid provisioning portal and image library management system to automate the setup and teardown of multimachine software configurations and manage service transition activities. Lab Manager leverages VMware vSphere and VMware vCenter to provide virtual infrastructure resources to multiple teams, projects, and geographies from a central location. Using Lab Manager, you can create a shared virtual machine library that stores commonly used configurations and provide users with self‐service access to these configurations for application development, testing, support, training, software demonstrations, and more. Lab Manager administrators control access rights, storage quotas, and deployment policies. This chapter includes these topics:  “Lab Manager Components” on page 13  “Accessing the Lab Manager Web Console” on page 14  “View Performance, Usage, and Support Information” on page 15  “Setting User Preferences” on page 16  “Lab Manager Workflow” on page 17 Lab Manager Components Lab Manager requires VMware vSphere. VMware ESX/ESXi™ hosts provide the memory and CPU resources to run Lab Manager virtual machines. Lab Manager manages the ESX/ESXi hosts through a vCenter Server ...
Page 14: Accessing The Lab Manager Web Console
Lab Manager User’s Guide Figure 1‐1 illustrates the components of Lab Manager and how it works with VMware vSphere. Figure 1-1. Lab Manager Components Lab Manager Web Console or SOAP API VM Consoles: HTML TCP 902, 903 over HTTPS Lab Manager Server VIM API VMware vSphere vCenter Server ESX/ESXi servers FC, iSCSI, or NFS...
Page 15: Set Microsoft Internet Explorer Options
Log In to the Web Console Before you can log in to the Web console, you need a user name and password, and you must be a member of at least one organization in Lab Manager. To log in to the Lab Manager Web console Open a browser and navigate to https://<Lab_Manager_Server_domain_name_or_IP_address>. Type your user name and password and click Login. Lab Manager displays the Web console. If Lab Manager displays an error, check with a Lab Manager administrator to make sure you are using the correct user name and password and that you are a member of a Lab Manager organization. View Performance, Usage, and Support Information The Overview page is the default landing page in the Web console. It includes performance summary data, information about your quotas, usages, and leases, and links to additional resources to help you learn about Lab Manager. A Lab Manager system administrator must enable SupportLink if you want to view all statistics. See “Configuring SupportLink Settings” on page 142. VMware, Inc.
Page 16: Setting User Preferences
Manager can change their password. Set Display and Lease Alert Preferences You can set default display and lease alert preferences. To set display and lease alert preferences Click the Preferences link. Click the Defaults tab. Select the page to display when you log in to the Web console. The Overview page is the default setting. Deselect the Show Page Header check box to not display IP addresses, virtual machine descriptions, and snapshot thumbnails at the top of the each page. Removing the header gives you more room to view the console. Type the number of rows to display on pages with data in a table. The maximum number is 500. The default is 20. Select the number of days or hours before a deployment lease expiration that you want Lab Manager to send an email notification. When a deployment lease expires, Lab Manager undeploys the virtual machine template or configuration. Select the number of days or hours before a storage lease expiration that you want Lab Manager to send an email notification. When a storage lease expires, Lab Manager deletes the virtual machine template or configuration, or marks it for deletion (depending on how the system administrator has configured Lab Manager). Click OK. VMware, Inc.
Page 17: Change Your User Password
Chapter 1 Getting Started with Lab Manager Change Your User Password You can change the password only for a user account created in Lab Manager. You cannot use Lab Manager to change an LDAP account password. To change your user password Click the Preferences link. Click the Change Password tab. Type and confirm a new password and click Change Password. The next time you log in to the Web console, use your new password. Lab Manager Workflow When you install or upgrade Lab Manager, you connect Lab Manager to a vCenter Server and add resource pools, ESX/ESXi hosts, and a physical network to use with Lab Manager virtual machines. Your next steps might involve adding more resources to the system, setting up organizations and workspaces, and adding users and groups to those organizations and workspaces. When Lab Manager has resources and users, you can create or import virtual machine templates to serve as the basis for virtual machines. Use these virtual machine templates to create configurations composed of one or more virtual machines. You can work with a configuration and its virtual machines in a workspace and save a configuration to the Library to share it with other users. VMware, Inc.
Page 18 Lab Manager User’s Guide VMware, Inc.
Page 19: Adding Resources
 “Add a Media Store” on page 20  “Add a Physical Network” on page 20  “Add a Host Spanning Transport Network” on page 21 Attach a Resource Pool If you need additional CPU and memory resources for virtual machines, you can attach a resource pool. By default, only system administrators can attach resource pools. To attach a resource pool In the left pane, click Resources. Click the Resource Pools tab. In the Organization drop‐down menu, select the organization to which you want to add the resource pool. If you select Global, the added resource pool is available to all organizations but assigned to none. You can assign it to an organization later. Click Attach Resource Pool. Select the resource pool, cluster, or host from the vCenter inventory. (Optional) Type a name for the resource pool to display in Lab Manager. Click OK. If Lab Manager detects that a host is not prepared (for example, the host does not have an agent that Lab Manager installed on the host), a message appears. See “Prepare a Host” on page 91. VMware, Inc.
Page 20: Add A Media Store
To add a media store In the left pane, click Resources. In the Organization drop‐down menu, select the organization to which you want to add the media store. If you select Global, the added media store is available to all organizations but assigned to none. You can assign it to organizations later. On the Datastores tab, move the pointer over the datastore that you want to use as a media store and select Enable Media. On the Media Stores tab, click Add Media Store. Type a name. Select the datastore. Type the directory path to the media. For NFS datastores, type the path relative to the mount point. For VMFS datastores, type the path relative to the root. A media store and its NFS datastore cannot have the same NFS path root. Click OK. On the Media Stores tab, move the pointer on the media store name and select Synchronize. VMware supports one directory without subdirectories. Add a Physical Network By default, only system administrators can add a physical network. To add a physical network In the left pane, click Resources. In the Organization drop‐down menu, select the organization to which you want to add the physical network. If you select Global, the added physical network is available to all organizations but assigned to none. You can assign it to an organization later. On the Physical Networks tab, click New Physical Network. Type a name. (Optional) Type a description and a VLAN Identifier. Select the IP addressing modes for the network. If you selected Static ‐ IP Pool or Static ‐ Manual, type the static mode settings and add an IP pool. VMware, Inc.
Page 21: Add A Host Spanning Transport Network
Select the physical network bindings.  Bind to a Virtual Switch (per host) If you select this option, you must select a virtual switch from the drop‐down menu for each host.  Bind to a vNetwork Distributed Switch If you select this option, you must select the switch that spans multiple hosts from the drop‐down menu. Click OK. Add a Host Spanning Transport Network Before you can add a host spanning transport network, you must create a vNetwork Distributed Switch in vSphere. See the vSphere documentation for more information on creating a vNetwork Distributed Switch. By default, only system administrators can add host spanning transport networks. To add a host spanning transport network In the left pane, click Resources. In the Organization drop‐down menu, select the organization to which you want to add the host spanning transport network. If you select Global, the added host spanning transport network is available to all organizations but assigned to none. You can assign it to an organization later. On the Host Spanning Transport Networks tab, click Add Transport Network. Select a vNetwork Distributed Switch. Type a VLAN Identifier. Select Enabled if you want to enable the network for use in virtual/fence network Host Spanning. Select the Customize Name check box to modify the display name. Click OK. VMware, Inc.
Page 22 Lab Manager User’s Guide VMware, Inc.
Page 23: Adding Users And Groups
Users cannot log in to Lab Manager or access any resources until they are added to an organization. This chapter includes the following topics:  “Import a User” on page 23  “Create a User” on page 24  “Import an LDAP Group” on page 24 Import a User By default, only system administrators and administrators with rights at the organization level can import users. You can import users that exist on an LDAP server or users that you created from the Web console. See “Configuring LDAP Settings” on page 138 and “Create a User” on page 24 for more information. To import a user In the left pane, click Users and Groups. In the Organization drop‐down menu, select the organization to which you want to add the user. If you select Global, this user is available to all organizations. On the Users tab, click Import Users. Deselect the Show Existing Users/Groups check box. Deselecting this option allows you to search for users who are not members of the selected organization. Type the name (complete or partial) of the user that you want to add and click Search. Lab Manager searches for LDAP and non‐LDAP users and displays the first 200 results that match the search terms. Select the check box for each user that you want to import. Click Add. VMware, Inc.
Page 24: Create A User
On the Users tab, click New User. Type a user name. Type and confirm a password. Type a full name. This name is displayed for all objects owned by this user. Type an email address. (Optional) Type IM and phone information. Select a role for the user in the selected organization. If you are adding a user to the Global organization, you can only select No Role or System Administrator. If you select No Role, this user cannot log in to Lab Manager or access resources until the user is added to another organization. 10 Deselect the Is Enabled check box to prevent the user from accessing the Web console. 11 Type a stored virtual machine template and library configuration quota. 12 Type a deployed virtual machine template quota. If you are in the Global organization, the quota text boxes do not appear. 13 Click OK. Import an LDAP Group By default, only system administrators and administrators with rights at the organization level can import LDAP groups. Lab Manager does not support non‐LDAP groups. To add an LDAP group In the left pane, click Users and Groups. In the Organization drop‐down menu, select the organization to which you want to add the group. If you select Global, the added group is available to all organizations. On the Groups tab, click Import Groups. VMware, Inc.
Page 25 Chapter 3 Adding Users and Groups Deselect the Show Existing Users/Groups check box. Deselecting this option allows you to search for users and groups that are not in the selected organization. Type the name (complete or partial) of the group that you want to import and click Search. Lab Manager displays the first 200 results that match the search terms. Select the check box for each group that you want to add. Click Add. Assign a role to the added groups. All members of the group are assigned the selected role. If you are adding groups to the Global organization, you can only select No Role or System Administrator. You can change the roles of individual group members later. See “Modify User Properties” on page 110 for more information. Click OK. Repeat these steps to import groups with different roles. VMware, Inc.
Page 26 Lab Manager User’s Guide VMware, Inc.
Page 27: Setting Up Organizations And Workspaces
This chapter includes the following topics:  “Create an Organization” on page 27  “Create a Workspace” on page 28 Create an Organization Lab Manager includes an organization named Default. A system administrator can create additional organizations. For example, you can create an organization for IT, one for human resources, one for engineering, and so on. When you add a resource pool to a new organization, Lab Manager also adds all its hosts, datastores, and media stores to the organization. To add an organization In the left pane, click Organizations. Select Global from the Organization drop‐down menu. Click New Organization. Type a name. (Optional) Type a description. Select one or more resource pools from Available and move them to Selected. Select one or more host spanning transport networks from Available and move them to Selected. Select one or more physical networks from Available and move them to Selected. Click Import Members. 10 Select your search option from the Look for drop‐down menu. 11 Type your search terms and click Search. Lab Manager displays the first 200 results that match the search terms. VMware, Inc.
Page 28: Create A Workspace
14 Select a role for each added user or group. 15 Click OK. Lab Manager creates the organization and creates the Main workspace. Create a Workspace Every organization includes a Main workspace. System administrators and administrators with rights at the organization level can create additional workspaces. For example, you can create integration, testing, staging, and production workspaces to manage service transition activities. When you create a workspace, you can choose whether you want to share its configurations or keep them private. In a shared workspace, by default, all the users in that workspace can access the configurations. In a private workspace, by default, users can only access their own configurations. To create a workspace In the Organization drop‐down menu, select the organization in which you want to create a workspace. In the left pane, click Workspace(s). Click New Workspace. Type a name. (Optional) Type a description. Click Add Users and Groups. Select your search option from the Look for drop‐down menu. Type your search terms and click Search. Select the check box next to the users or groups you want to add. 10 Click Add and OK. 11 Select a role for each added user and group. 12 Decide whether you want the workspace to be shared or private. 13 Select one or more resource pools from Available and move them to Resource Pools used by this Workspace. 14 Click OK. VMware, Inc.
Page 29: Setting Up Network Templates
Manager creates a virtual network based on the network template and connects the NIC to that network. Network templates allow system administrators, administrators with rights at the organization level, and template creators to predefine virtual networks for other users. A network template provides a level of control and consistency across the Lab Manager installation. These templates are created and owned by a user, but they can be shared with other users in an organization or across the entire installation. This chapter includes the following topics:  “Create a Network Template” on page 29  “Copy a Network Template” on page 30  “Share a Network Template” on page 30 Create a Network Template By default, only system administrators, administrators with rights at the organization level, and template creators can create network templates. To create a new network template In the left pane, click Network Templates. Click New Network Template. Type a name. (Optional) Type a description. Select the IP addressing modes. If you selected Static ‐ IP Pool or Static ‐ Manual, type the static mode settings and add an IP pool. Click OK. Lab Manager creates the network template in the user’s organization. VMware, Inc.
Page 30: Copy A Network Template
If you are the owner of a network template, or if your user role includes the Administrator View and Control right, you can share a network template with other users. Sharing a network template grants access to other users. Depending on your rights, you can share a network template within or between workspaces, within or between organizations, or across the entire Lab Manager installation. When you share a network template, you can specify access rights for the users with whom you are sharing the configuration. Access rights combine with the rights provided by a user’s role to determine how that user can interact with the shared network template. Access rights cannot provide users with rights that they do not already have based on their role. To share a network template with other users In the left pane, select Network Templates. Move the pointer over a network template name and select Sharing. The Sharing Network Template dialog box displays the users and organizations that currently have access to the network template and their level of access control. Click Add Users. Select the organization containing the users with whom you want to share the network template or select Global to view users from all organizations. Select with whom you want to share the network template.  Everyone in Organization shares the network template with all users in the selected organization.  Everyone in Workspace shares the network template with all users in the selected workspace.  Selected Users shares the network template with specific users in the selected organization. Select the check box next to each user with whom you want to share the network template. Specify the access rights for the users and click OK. If you share a network template with users outside of the organization in which the template was created, you can only specify Read access. In addition, network templates created in Global can only be shared with Read access. Click OK and Done. VMware, Inc.
Page 31: Setting Up Virtual Machine Templates
“Create a Virtual Machine Template” on page 31  “Importing Virtual Machine Templates” on page 32  “Save a Virtual Machine as a Virtual Machine Template” on page 34  “Clone a Virtual Machine Template” on page 35  “Deploying Virtual Machine Templates” on page 35  “Install a Guest Operating System” on page 36  “Installing VMware Tools” on page 36  “Customizing the Guest Operating System” on page 40  “Undeploy a Virtual Machine Template” on page 46  “Share a Virtual Machine Template” on page 46  “Publishing Virtual Machine Templates” on page 47 Create a Virtual Machine Template The properties that you specify when you create a virtual machine template are the default properties for all virtual machines based on the template. After creating a virtual machine template, you can deploy the virtual machine template and install a guest OS, ...
Page 32: Importing Virtual Machine Templates
Type the memory. 10 In the Hard Disk panel, type the size and select the bus type. 11 In the Network Interface panel, select a network, and if applicable, select an IP address mode. 12 Select a storage lease. 13 Click OK. Lab Manager creates the virtual machine template in the current organization, and it appears on the VM Templates page as Undeployed and Unpublished. Importing Virtual Machine Templates Importing a virtual machine template involves copying an external virtual machine into the Lab Manager template library. You can import a virtual machine that is new to, or was previously exported by, Lab Manager. Lab Manager changes the MAC address of all imported virtual machines. Lab Manager supports these virtual machines types for import operations:  VMware Workstation  VMware Server  VMware ESX/ESXi  BEA LiquidVM Only LiquidVMs that use static IP mode and DHCP mode are supported. If importing takes longer than two hours, Lab Manager times out. To modify the timeout for vCenter and SMB imports, see “Configuring General Preferences” on page 135. You cannot import a virtual machine that uses raw device mappings (RDMs). VMware, Inc.
Page 33: Import A Virtual Machine Template From Vcenter
Specify the networking information for each NIC in the imported virtual machine template: Select the Connected check box. Choose a default virtual or physical network. Choose a default IP addressing mode. Select a storage lease. 10 Select a deployment lease. 11 Select the datastore to which you want to import the virtual machine template. 12 Select whether to copy or move the source virtual machine template. If you copy the virtual machine template, it continues to exist in the original location, but if you move the virtual machine template, it will not exist in this location. 13 Click Import. Lab Manager imports the virtual machine template into the current organization and displays it on the VM Templates page. Import a Virtual Machine Template from SMB Storage An SMB port needs to be open on the ESX host. Although Lab Manager opens the port during installation, you need to make sure that the port remains open after installation. To check the port status, run esxcfg-firewall -q smbClient on each host. By default, only a system administrator, an administrator with rights at the organization, and a template creator can import virtual machines as templates from an SMB share. Do not import virtual machine templates manually with ESX commands. MPORTANT VMware, Inc.
Page 34: Save A Virtual Machine As A Virtual Machine Template
13 Select the datastore to which you want to import the virtual machine template. 14 Click Import. Lab Manager imports the virtual machine template into the current organization and displays it on the VM Templates page. Save a Virtual Machine as a Virtual Machine Template You can create a virtual machine template from any virtual machine in Lab Manager. This new template is a linked clone of the original virtual machine. To create a virtual machine template from an active virtual machine In the left pane, click All Configurations. Move the pointer over a configuration name and select Open. Move the pointer over the virtual machine name and select Add To VM Templates. Type a name. (Optional) Type a description. Select a deployment lease. Select a storage lease. Click OK. In the left pane, click VM Templates. VMware, Inc.
Page 35: Clone A Virtual Machine Template
Select the type of clone that you want to create. If you select Full Clone of Virtual Machine Template, select a datastore. Click OK. Deploying Virtual Machine Templates Deploying a virtual machine template registers it with a resource pool and provides access to Lab Manager operations at the virtual machine console level. By default, system administrators, administrators, template creators, and application owners can deploy and undeploy virtual machine templates. You can only deploy unpublished templates. Deploy a Virtual Machine Template with Default Settings When you deploy a virtual machine template with default settings, Lab Manager uses:  Any Available resource pool option is used.  The Power On After Deployment check box is selected.  The deployment lease comes from the template properties. To deploy a virtual machine template with default settings Move the pointer over the virtual machine template name and select Deploy with defaults. VMware, Inc.
Page 36: Deploy A Virtual Machine Template With Custom Settings
Move the pointer over the tab with the virtual machine template name and select Insert CD. Select an ISO file and click OK. On the tab, move the pointer over the virtual machine template name and select Ctrl‐Alt‐Del to boot from the ISO image and launch the operating system installer. In the virtual machine console of the virtual machine template, enter the required information for the installation process. Installing VMware Tools Lab Manager depends on VMware Tools to customize the guest operating system in a virtual machine. VMware Tools also allows you to move the pointer in and out of the virtual machine console window. A virtual machine template must be deployed to install VMware Tools. This process takes several minutes and requires you to restart the virtual machine. Install VMware Tools in a Windows Guest By default, system administrators, administrators with rights at the organization level, and template creators can install VMware Tools. After you install VMware Tools, Windows 2000 and Windows XP guest operating systems must be rebooted to use the new driver. For more information about the installation, see VMware vSphere documentation. To install VMware Tools on a Windows Guest On the VM Templates page, move the pointer over the virtual machine template name and select View Console. Log in to the guest operating system inside the virtual machine console. Click Install VMware Tools. VMware, Inc.
Page 37: Install Vmware Tools On A Linux Guest Within X With The Rpm Installer
On some Windows operating systems, after the SVGA driver is installed, you are prompted to reboot to use this new driver. Reboot the virtual machine if necessary. Install VMware Tools on a Linux Guest Within X with the RPM Installer By default, only system administrators, administrators with rights at the organization level, and template creators can install VMware Tools. For more information about the installation, see VMware vSphere documentation. To install VMware Tools on a Linux guest within X with the RPM installer On the VM Templates page, move the pointer over the virtual machine template name and select View Console. Log in to the guest operating system. Click Install VMware Tools. The remaining steps are completed in the guest operating system. Complete one of the tasks. ...
Page 38 Lab Manager User’s Guide To install VMware Tools on a Linux guest with the tar installer or RPM installer On the VM Templates page, move the pointer over the virtual machine template name and select View Console. Log in to the guest operating system in the virtual machine console. Click Install VMware Tools. The remaining steps take place in the guest operating system. As root (su -), mount the VMware Tools virtual CD‐ROM image and change to a working directory (for example, /tmp). Some Linux distributions automatically mount CD‐ROMs. If your distribution uses automounting, do not use the mount and umount commands described in this procedure. You still must untar the VMware Tools installer to /tmp. Some Linux distributions use different device names or organize the /dev directory differently. If your CD‐ROM drive is not /dev/cdrom, or if the mount point for a CD‐ROM is not /mnt/cdrom, modify the following commands to reflect the conventions used by your distribution. mount /dev/cdrom /mnt/cdrom cd /tmp If you have an existing installation, delete the vmware-tools-distrib directory before you install. The ...
Page 39: Install Vmware Tools On A Solaris Guest
Press Enter to accept the default value. After the upgrade is complete, restart the network by running /etc/init.d/network restart. Type exit. Start your graphical environment. 10 In an X terminal, run vmware-toolbox &. Install VMware Tools on a Solaris Guest By default, only system administrators, administrators with rights at the organization level, and template creators can install VMware Tools. For more information about the installation, see VMware vSphere documentation. To install VMware Tools on a Solaris guest On the VM Templates page, move the pointer over the virtual machine template name and select View Console. Log in to the guest operating system in the virtual machine console. Click Install VMware Tools. The remaining steps take place in the virtual machine. Log in as root (su -) and, if necessary, mount the VMware Tools virtual CD‐ROM image. The Solaris volume manager vold mounts the CD‐ROM under /cdrom/vmwaretools. If the CD‐ROM is not mounted, restart the volume manager by running the following commands: /etc/init.d/volmgt stop /etc/init.d/volmgt start After the CD‐ROM is mounted, change to a working directory (for example, /tmp) and extract VMware ...
Page 40: Customizing The Guest Operating System
Access the machine.id from a Guest Operating System If you install VMware Tools, you can access the machine.id from the guest operating system of a deployed virtual machine. To access the machine.id line from the guest operating system In the left pane, click Workspaces. Move the pointer over the configuration name and select Open. Move the pointer over the deployed virtual machine name and select Show Console. Search for machine.id from inside the guest operating system.  From a Linux guest OS, type: # vmware-guestd --cmd machine.id.get  From a Windows guest OS, navigate to the directory where VMware Tools is installed (usually C:\Program Files\VMware\VMware Tools) and type: >VMwareService.exe -cmd machine.id.get VMware, Inc.
Page 41: Prerequisites For Guest Customization
Chapter 6 Setting Up Virtual Machine Templates The following is an example of a machine.id line: numnics=2&macaddr_0=00:50:56:3f:00:1c&bootproto_0=static&ip_0=10.115.127.10&netmask_0=255.255.248 .0&gateway_0=10.115.127.253&dns1_0=10.20.20.1&dns2_0=10.20.20.2&suffix_0=eng.vmware.com&macaddr_1 =00:50:56:3f:00:1d&bootproto_1=static&ip_1=1.1.1.100&netmask_1=255.255.0.0&gateway_1=1.1.1.1&dns1 _1=2.2.2.2&dns2_1=&suffix_1=BLUE.ORG&primaryNic=0&computerName=Config10VM1&UseSysPrep=No&bitMask= 11&markerid=504810238&reconfigToken=411678171 Prerequisites for Guest Customization Before you configure the template, complete or check these issues:  Specify the correct guest operating system on the Virtual Machine Template Properties page. Lab Manager uses this information to determine how to customize the operating system.  Install the version of VMware Tools packaged with ESX 3.5 or later. The Lab Manager Web console also provides the correct version for installation. If you import a virtual machine as a virtual machine template, you must deploy the virtual machine template. The deploy operation allows Lab Manager to detect the version of VMware Tools installed on the virtual machine template. If the virtual machine template has an outdated version or never had VMware Tools installed on it, you must install it. If you import a virtual machine template that was originally used in VMware Lab Manager version 2.x, see “Importing Virtual Machine Templates from Lab Manager 2.x with VMware Tools and LM Tools” on page 45.  Ensure that the virtual machine template is not part of a domain. ...
Page 42: Complete Guest Customization For Windows Nt And Solaris Virtual Machine Templates
Lab Manager provides a customized sysprep.inf file. When the Microsoft Sysprep package is AUTION being built, do not overwrite this file with the sysprep.inf file from the Windows CD. To build a Microsoft Sysprep package for guest customization Insert the Windows OS CD in the Lab Manager server. If you have an ISO, mount the ISO using a third‐party tool. Find the DEPLOY.CAB file in \Support\Tools. Expand the DEPLOY.CAB file with a tool that can read Microsoft CAB files. You can also use Windows Explorer in Windows XP or Windows 2003. Copy the files to the appropriate Lab Manager directory for Microsoft Sysprep support. For example, if you installed Lab Manager in C:\Program Files\VMware\VMware Lab Manager, copy the files to one of the following directories.  C:\Program Files\VMware\VMware Lab Manager\Tools\CustomizeGuest\Windows\Sysprep\win2k3  C:\Program Files\VMware\VMware Lab Manager\Tools\CustomizeGuest\Windows\Sysprep\win2k3_64 This location is for 64‐bit Windows 2003.  C:\Program Files\VMware\VMware Lab Manager\Tools\CustomizeGuest\Windows\Sysprep\win2000 ...
Page 43: Complete Guest Customization For Solaris Virtual Machine Templates
Working with the Guest Customization SID Generation Tool For guest operating systems that support multiple SID generation tools, you can set a global preference to use Microsoft Sysprep instead of SIDgen, which is packaged with Lab Manager. You can also select SIDgen or Microsoft Sysprep as the SID generation tool for a virtual machine or virtual machine template. For Windows 2003 (64 bit) and Windows XP (64 bit) guest operating systems, you must use Microsoft Sysprep. Windows Vista and Windows 2008 guest operating systems always use Microsoft Sysprep instead of SIDgen, because Microsoft Sysprep is already built into these operating systems. See Appendix C, “Guest Operating System Support,” on page 161 for more information on guest operating support for SIDgen and Microsoft Sysprep. Select the SID Generation Tool for Lab Manager You need to set the default SID generation tool to use with the new virtual machine templates that require Microsoft Sysprep and templates that support SIDgen or Microsoft Sysprep. To select the tool for Lab Manager In the left pane, click Settings. On the Guest Customization tab, select a default SID generation mechanism. This selection determines the default mechanism of new virtual machine templates. If you are not ready to use Sysprep, select Use Pre‐Installed SID Generation Tool (SIDgen). To change the SID mechanism for a virtual machine or virtual machine template, edit the properties of that virtual machine or virtual machine template. Click OK. Lab Manager sets the default SID generation mechanism. VMware, Inc.
Page 44: Change The Sid Generation Tool For A Virtual Machine Template
Disable guest customization in the following situations:  The software in the virtual machine or virtual machine template is configured to use specific network settings.  You have virtual machines that must remain untouched for specific security or integrity requirements.  You are not using one of the supported guest operating systems listed in Appendix C, “Guest Operating System Support,” on page 161. Disable Guest Customization for a Virtual Machine Template You can disable guest customization in the properties of virtual machine templates. The setting is stored when you export the virtual machine template to SMB storage and import it back to Lab Manager. If you create a virtual machine template based on an active virtual machine in a configuration, the virtual machine template inherits the customization setting of the active virtual machine. To disable guest customization for a virtual machine template In the left pane, click VM Templates. Move the pointer over an unpublished virtual machine template name and select Properties. Deselect the Perform customization check box. Click Update. VMware, Inc.
Page 45: Disable Guest Customization For A Virtual Machine
To add a customization script to a template In the left pane of the console, click VM Templates. Move the pointer over the virtual machine template name and select Customization Script. Click Browse to locate an existing script or type the script. Specify a batch script for Windows guests and a shell script for UNIX guests. The script can include text and cannot include binary data. Click OK. Importing Virtual Machine Templates from Lab Manager 2.x with VMware Tools and LM Tools If you import virtual machine templates from Lab Manager 2.x, the templates probably have an older version of VMware Tools, and the enforcement check prevents you from publishing the virtual machine templates. If you cannot publish the templates, do one of the following:  Upgrade VMware Tools to the current Lab Manager version. Upgrading allows guest customization and publishing to occur. ...
Page 46: Undeploy A Virtual Machine Template
Share a Virtual Machine Template If you are the owner of a virtual machine template, or if your user role includes the Administrator View and Control right, you can share a virtual machine template with other users. Sharing a virtual machine template grants access to other users. Depending on your rights, you can share a virtual machine template within or between workspaces, within or between organizations, or across the entire Lab Manager installation. When you share a virtual machine template, you can specify access rights for the users with whom you are sharing the template. Access rights combine with the rights provided by a user’s role to determine how that user can interact with the shared virtual machine template. Access rights cannot provide users with rights that they do not already have based on their role. To share a virtual machine template On the VM Templates page, move the pointer over the virtual machine template name and select Sharing. The Sharing Template dialog box displays the users and organizations that currently have access to the template and their level of access control. Click Add Users. Select the organization containing the users with whom you want to share the virtual machine template or select Global to view users from all organizations. Select with whom you want to share the virtual machine template.  Everyone in Organization shares the virtual machine template with all users in the selected organization.  Everyone in Workspace shares the virtual machine template with all users in the selected workspace.  Selected Users shares the virtual machine template with specific users in the selected organization. Select the check box next to each user with whom you want to share the virtual machine template. Specify the access rights for the users and click OK. If you share a virtual machine template with users outside of the organization in which the template was created, you can only specify Read access. In addition, virtual machine templates created in Global can only be shared with Read access. Click OK and Done. VMware, Inc.
Page 47: Publishing Virtual Machine Templates
Chapter 6 Setting Up Virtual Machine Templates Publishing Virtual Machine Templates Publishing a virtual machine template allows you to build configurations without reinstalling software or redoing setup tasks. Templates ensure that virtual machines are consistently configured with the correct operating systems, versions, system packs, and so on. Check VMware Tools Status Before Publishing Virtual Machine Templates Lab Manager depends on VMware Tools for guest customization. Before you publish a virtual machine template, check the status of VMware Tools on the virtual machine template and address any issues. To publish a virtual machine template without VMware Tools, see “Disabling Guest Customization” on page 44 for more information. To check VMware Tools status In the left pane, click VM Templates. Check the VMware Tools column on the VM Templates page. If the status is Installed (Requires Update) or Not Installed, you must deploy the virtual machine template and follow the prompts to update or install VMware Tools. See “Installing VMware Tools” on page 36. If the status is Unknown, you must deploy the virtual machine template and allow Lab Manager to check ...
Page 48 Lab Manager User’s Guide VMware, Inc.
Page 49: Working With Configurations
“Share a Configuration” on page 55  “Configuration Networking” on page 56  “Deploying and Undeploying Configurations” on page 60  “Stopping and Starting Configuration Virtual Machines” on page 62  “Working with Configuration Snapshots” on page 63  “Viewing Configuration Virtual Machines, Networks, and History” on page 64  “Modifying Configurations” on page 66  “Using LiveLink” on page 70  “Exporting Configurations” on page 71 Adding Configurations to a Workspace Before you can deploy a configuration and begin working with its virtual machines, you must add the configuration to a workspace. You can create a configuration that includes virtual machines based on virtual machine templates and virtual machines imported from vCenter. You can import entire configurations that you previously exported from VMware vCenter Lab Manager, vCenter Stage Manager, or vCenter Lab Manager. You can also copy a library configuration to a workspace. If you already have a workspace configuration that you want to use as the basis for a new configuration, you can clone it. VMware, Inc.
Page 50: Create A Workspace Configuration
10 Click OK. Add a Virtual Machine Based on a Virtual Machine Template Virtual machine templates provide the specifications for creating virtual machines, such as the guest operating system, number of virtual CPUs, and network interfaces. You can only add virtual machines based on published virtual machine templates. To add a virtual machine based on a template In the Source drop‐down menu, select a virtual machine template. You can select a virtual machine template that you created or a virtual machine template that is shared with you. Type a name. Specify the network information for the virtual machine. Your options are based on how the virtual machine template was defined. Select a primary NIC for virtual machines with multiple NICs. The primary NIC setting determines the default and only gateway for the virtual machine. The virtual machine can use any NIC to connect to other machines that are directly connected to the same network as the NIC, but it can only use the primary NIC to connect to machines on networks that require a gateway connection. Consider this behavior when selecting a primary NIC, especially if you plan to deploy configurations that use fencing or connect virtual networks to physical networks. Select a network. VMware, Inc.
Page 51: Add A Virtual Machine From Vcenter
Add a Virtual Machine from vCenter You can add a virtual machine created in vCenter to a configuration. The virtual machine must be powered off and not already under Lab Manager control. Add a vCenter virtual machine if you know its vCenter network settings and want to maintain those settings in Lab Manager. If you do not care about the network settings, import the virtual machine from vCenter as a virtual machine template instead. See “Import a Virtual Machine Template from vCenter” on page 33. To add a virtual machine from vCenter Click Import VM from vCenter. Select a virtual machine and click OK. Type a name. Specify the network information for the virtual machine. Specify a primary NIC for virtual machines with multiple NICs. The primary NIC setting determines the default and only gateway for the virtual machine. The virtual machine can use any NIC to connect to other machines that are directly connected to the same network as the NIC, but it can only use the primary NIC to connect to machines on networks that require a gateway connection. Consider this behavior when selecting a primary NIC, especially if you plan to deploy configurations that use fencing or connect virtual networks to physical networks. Select a network. If the virtual machine is connected to a network that is available to both vCenter and Lab Manager, you cannot change the network during import. If the virtual machine is connected to a network that is only available to vCenter, you must choose a new network. Select an IP addressing mode. Select a datastore. To add another virtual machine to this configuration, click Import VM from vCenter and specify the required information. VMware, Inc.
Page 52: Import A Configuration To A Workspace
In the Organization drop‐down menu, select the organization to which you want to import the configuration. Click Workspaces and click the name of the workspace to which you want to import the configuration. If you only have access to one workspace, click Workspace. Click Import Configuration. Type the UNC path of the directory (relative to the Lab Manager server system) where the configuration file is stored. Use English characters for the UNC path. A sample path is \\10.6.1.246\VMwareLM\ExportedConfigs. Type the user name and password for the import directory, if necessary. Click Next. Provide configuration details. Click Import. Copy a Workspace Configuration You can copy a workspace configuration by cloning some or all of its virtual machines to a new configuration. If you have access to more than one workspace, you can clone configurations from one workspace to another. You cannot clone configurations from one organization to another. When you create a clone, Lab Manager assigns the same network parameters to the cloned virtual machines. If you deploy the original and cloned configurations at the same time, duplicate IP address errors occur unless you deploy one of the configurations in fenced mode. Full Clones and Linked Clones When you clone configurations, you can consolidate the source configuration’s virtual machines during the cloning process to create full clones of the virtual machines. Typically, you do not need to create full clones unless you plan to dismantle the storage and move the configuration to a different server, or if you need to maximize the performance of specific virtual machines (for example, for certain production‐level virtual machines). A full‐clone operation copies all of a virtual machine’s delta disks and its base disk and consolidates them into a new base disk. The original base disk remains unchanged. A full‐clone operation takes longer than a linked‐clone operation. You cannot make a full clone of a deployed configuration. VMware, Inc.
Page 53: Clone A Library Configuration To A Workspace
Clone a Library Configuration to a Workspace The configuration library is the central location for storing commonly used or base configurations. Users with the necessary rights can clone a library configuration to a workspace and then modify and deploy it. The original configuration remains in the library where it can be cloned again. When you clone a captured library configuration to a workspace, Lab Manager creates a linked clone. Linked clones conserve storage space. Instead of copying the entire virtual disk for each virtual machine in the configuration, Lab Manager uses delta disks to track the differences between the original virtual machines and the cloned virtual machines. When you clone an archived library configuration to a workspace, you can create a linked clone or a full clone. You can clone all virtual machines in a configuration or selected machines. You can also combine configurations by cloning a library configuration to an existing workspace configuration. To clone a configuration to the workspace On the Library page, move the pointer over a configuration name and select Clone to Workspace. Specify the destination workspace, if applicable. Specify the destination. For a new configuration, type a name and description and specify a storage lease. For an existing configuration, select the configuration. (Optional) Type change summary text that will appear on the configuration’s History tab. Specify the type of clone. This option is only available for archived library configurations. When you clone a captured library configuration to a workspace, Lab Manager always creates a linked clone. Specify the virtual machines to clone. If you are creating a full clone and choose Selected Virtual Machines, you can specify a datastore. Click OK. After a brief time, an undeployed copy of the library configuration appears in the destination workspace. VMware, Inc.
Page 54: Adding Configurations To The Library
(Optional) Select the Gold Master check box to indicate an important or administrator‐approved configuration. (Optional) Type change summary text that will appear on the captured configuration’s History tab. Specify a time to delete the configuration from storage or mark the configuration for deletion. Click Capture. Archive a Workspace Configuration to the Library You can preserve the exact state of a configuration in the configuration library. Archived configurations are read‐only, but you can clone, export, and delete them. When you archive a configuration to the Library, it retains the sharing properties it had in the workspace. For example, if you archive a private workspace configuration, the library configuration is also private. You can modify a library configuration at any time to share it with members of other organizations and workspaces. To archive a configuration to the Library Move the pointer over the configuration name and select Archive to Library. Type a name for the configuration. Use a unique naming convention to simplify identification. (Optional) Type a description. (Optional) Type change summary text that will appear on the archived configuration’s History tab. Specify a time to delete the configuration from storage or mark the configuration for deletion. Select the clone type. If you select Full Clone, specify the destination datastore. Click OK. Lab Manager creates an archived configuration in the library. VMware, Inc.
Page 55: Clone A Library Configuration
Type a name. (Optional) Type a description. Specify a time to delete the configuration or mark the configuration for deletion. (Optional) Type change summary text that will appear on the configuration’s History tab. Specify the virtual machines to clone and select a datastore. Click OK. Share a Configuration If you are the owner of a configuration, or if your user role includes the Administrator View and Control right, you can share a workspace or library configuration with other users. Sharing a workspace configuration grants access to other users. Sharing a library configuration allows other users to clone their own copy of the configuration to a workspace. Depending on your rights, you can share a configuration within or between workspaces, within or between organizations, or across the entire Lab Manager installation. When you share a configuration, you can specify access rights for the users with whom you are sharing the configuration. Access rights combine with the rights provided by a user’s role to determine how that user can interact with the shared configuration. Access rights cannot provide users with rights that they do not already have based on their role. To share a configuration Move the pointer over a workspace or library configuration name and select Sharing. The Sharing Configuration dialog box displays the users and organizations that currently have access to the configuration and their level of access control. Click Add Users. Select the organization containing the users with whom you want to share the configuration or select Global to view users from all organizations. Select with whom you want to share the configuration.  Everyone in Organization shares the configuration with all users in the selected organization.  Everyone in Workspace shares the configuration with all users in the selected workspace.  Selected Users shares the configuration with specific users in the selected organization. Select the check box next to each user with whom you want to share the configuration. VMware, Inc.
Page 56: Configuration Networking
A vNetwork Distributed Switch functions like a single virtual switch across all associated hosts. This allows virtual machines to maintain consistent network configuration as they migrate across multiple hosts. When you bind, Lab Manager creates a portgroup on the vSwitch, or a dvPort group on the vNetwork Distributed Switch, names it based on the Lab Manager physical network name, and reports that as the Name in vCenter on the Network Properties page. If the Lab Manager physical network specifies a VLAN ID, Lab Manager sets this on the portgroup or dvPort group. Lab Manager does not use or affect existing portgroups on the vSwitch or vNetwork Distributed Switch. Fencing Virtual Machines When you deploy a configuration that includes a physical network, you can choose to isolate the configuration virtual machines from other machines on the network. This prevents IP and MAC address conflicts that could exist if multiple copies of the same machine are deployed at the same time. Fencing a configuration isolates the virtual machines that are defined to be connected to the physical network from the datacenter network using a virtual router (VR) and bidirectional network address translation (NAT). Typically, you want to enable network fencing under these circumstances:  You have a configuration with one or more servers, and you anticipate cloning the configuration numerous times.  You have a configuration involving a difficult and complex setup, and cloning the configuration is an easier route than repeating the setup. From a performance perspective, network fencing impacts the traffic flow between modules. Fencing requires a slightly higher number of resources on the host, such as memory, CPU, and networking. If you enable fencing but never use it, these resources are not consumed. Virtual machines in a configuration have preconfigured (internal) IP addresses. When you deploy virtual machines in fenced mode, Lab Manager assigns a unique external IP address to each of these machines. Through these external addresses, virtual machines both inside and outside the fence can communicate with each other. Lab Manager uses a virtual machine called a virtual router (VR) to route packets between these virtual machines. Lab Manager configures the virtual router when you deploy a fenced configuration and deletes it when you undeploy the configuration. VMware, Inc.
Page 57: Fencing Connectivity
IP address external IP address for fenced configurations virtual router Fencing a configuration does not require any changes to its virtual machines. Within a fenced configuration, virtual machines continue to use preassigned IP addresses to communicate with each other. Fencing Connectivity Three connectivity modes are available when you fence a configuration:  Allow In and Out – Virtual machines can communicate with machines outside the fence, and machines outside the fence can communicate with virtual machines inside the fenced configuration. Figure 7-2. Allow In and Out Fencing Mode ESX Server host fenced network configuration physical network VMware, Inc.
Page 58 Figure 7-3. Allow Out Fencing Mode ESX Server host fenced network configuration physical network  Block In and Out – Network traffic does not travel across the fence. Virtual machines in a fenced configuration cannot communicate with machines outside of the fence, and machines outside the fence cannot communicate with virtual machines in the fenced configuration. When you deploy a fenced configuration with this option, Lab Manager does not create a virtual router or assign external IP addresses. Figure 7-4. Block In and Out Fencing Mode ESX Server host fenced network configuration physical network VMware, Inc.
Page 59: Virtual Networks
Virtual to Physical Network Connectivity Two connectivity modes are available when you connect a virtual network to a physical network:  Allow In and Out – Virtual machines can communicate with machines on the selected physical network, and machines on the selected physical network can communicate with virtual machines inside the configuration.  Allow Out – Virtual machines in the configuration can initiate communication with machines on the selected physical network and can receive messages back on the same connection. Machines on the selected physical network cannot initiate communication with virtual machines inside the configuration. Host Spanning Host Spanning is a feature that enables the virtual machines in a configuration that uses fencing or virtual networks to be deployed on different ESX/ESXi hosts. When you deploy a configuration that uses Host Spanning, some of the virtual machines can get deployed to one ESX/ESXi host and some of the virtual machines can get deployed to a different host. For a configuration that is unfenced and does not include any virtual networks, Lab Manager can always deploy its virtual machines across multiple hosts. For a configuration that is fenced or includes a virtual network, you can enable Host Spanning, provided that the configuration has access to an enabled host spanning transport network. If you do not enable Host Spanning for a configuration that uses fencing or a virtual network, all of its virtual machines must deploy to the same host. In some cases, this restriction may prevent you from deploying a configuration. For example, for a large configuration, there might not be any single host available that has enough resources to deploy the configuration. In addition, Host Spanning is required in order to support VMware DRS and HA for configurations that use fencing or a virtual network. Host Spanning Networks Host spanning networks are logical overlay networks that use the resources of an underlying host spanning transport network to enable Host Spanning. Lab Manager creates a host spanning network when you deploy a configuration with Host Spanning enabled. Host spanning networks are not visible within Lab Manager. VMware, Inc.
Page 60: Host Spanning Transport Networks
73 for information about deploying an individual virtual machine in a configuration. You can only deploy workspace configurations. If you want to deploy a library configuration, clone it to a workspace first and then deploy it. The first time you deploy a configuration, all of its virtual machines with guest customization enabled go through a customization process, which might involve multiple reboots. Do not shut down the virtual machines until the customization is complete. When you deploy a configuration, you can either provide custom settings or use the default settings. Deploy a Configuration with Custom Settings When you deploy a configuration with custom settings, you can specify various deployment options that determine the configuration’s network connectivity, deployment lease, resource pool, and so on. To deploy a configuration with custom settings Move the pointer over the configuration name and select Deploy. If you have already partially deployed the configuration, you can only modify certain settings. Select the Fence Virtual Machines check box to deploy the configuration in fenced mode. This option is only available if the configuration allows fencing and includes a physical network that also allows fencing. Use the Connectivity drop‐down menu to select a connectivity mode for each physical network. See “Fencing Connectivity” on page 57 for more information. Select the Connect Virtual Networks to Physical Networks check box to connect virtual networks to physical networks. This option is only available if the configuration includes a virtual network. Select a physical network to connect to and use the Connectivity drop‐down menu to select a connectivity mode. See “Virtual to Physical Network Connectivity” on page 59 for more information. VMware, Inc.
Page 61: Deploy A Configuration With Default Settings
To deploy a configuration with default settings Move the pointer over the configuration name and select Deploy with defaults. If the configuration is already partially deployed, Lab Manager only deploys the configuration’s undeployed virtual machines. Understanding Default Deployment Settings Table 7‐1 provides information about how Lab Manager determines default deployment settings. Table 7-1. Default Deployment Settings Setting Name Setting Value Fence Virtual Machines If the configuration or any of its physical networks has a Fenced Only fencing policy, then all physical networks in the configuration are fenced and network connectivity is set to Allow In and Out, unless one of the physical networks requires a different connectivity setting. If the configuration and physical network policies conflict (one is set to Fenced Only and the other is set to Unfenced Only), Lab Manager displays an error and prevents deployment. If both the configuration and physical network properties are set to Allow Fenced or Unfenced, the default is determined by the deployment setting specified in the organization properties. Connect Virtual Networks Not selected. to Physical Networks VMware, Inc.
Page 62: Undeploy A Configuration
Suspend a Configuration Suspending a deployed configuration freezes the CPU of the virtual machines, but the virtual machines remain registered with vCenter. To suspend a configuration Move the pointer over the deployed configuration name and select Suspend. Resume Operation of a Suspended Configuration You can reverse a suspended state. To resume operation of a suspended configuration Move the pointer over the deployed configuration name and select Resume. Power Off a Configuration Powering off a deployed configuration turns the virtual machines off. It is the virtual equivalent of powering off physical machines. The virtual machines remain registered with vCenter. To power off a configuration Move the pointer over the deployed configuration name and select Power Off. VMware, Inc.
Page 63: Power On A Configuration
See “Working with Virtual Machine Snapshots” on page 77 for information about working with snapshots for a specific virtual machine in a configuration. Take a Configuration Snapshot When you take a configuration snapshot, Lab Manager captures the state of the configuration’s virtual machines. You can revert the configuration to that snapshot at a later time. To take a configuration snapshot Move the pointer over the configuration name and select Snapshot. Lab Manager changes the status of the configuration to Setting the Revert Point while it takes a snapshot of each virtual machine. Revert to a Configuration Snapshot When you revert a configuration to a snapshot, all virtual machines in the configuration lose their current state. If you revert to a configuration snapshot, Lab Manager retains the snapshot so that you can revert to it again later. To revert to a configuration snapshot Move the pointer over the configuration name and select Revert. Lab Manager changes the status of the configuration to Reverting while it reverts each virtual machine to its snapshot. VMware, Inc.
Page 64: Delete A Configuration Snapshot
To view details about the virtual machines in a configuration Move the pointer over the configuration name and select Open. Click the Virtual Machines tab. For each virtual machine in the configuration, Lab Manager displays the following information:  Console – Displays a thumbnail icon of the virtual machine console.  VM Name – Displays the virtual machine name.  Status – Lists the status (deployed or undeployed) of the virtual machine.  NIC – Lists a number for each NIC in the virtual machine. An asterisk (*) indicates a virtual machine’s primary NIC.  Network – Lists the network to which each NIC connects.  IP Address – Provides the IP address of each NIC in the virtual machine.  External IP – Provides the external IP address for the virtual machine if it requires one.  Template – Indicates the virtual machine template that the virtual machine is based on.  Host – Indicates the ESX/ESXi host for a deployed virtual machine. This column only appears for workspace configurations.  Connectivity – Indicates whether a deployed virtual machine uses fencing or has a virtual network connected to physical network.  Messages – Messages or alerts about vCenter activity that could raise errors in Lab Manager. View Configuration Networks You can view basic information about each network in the configuration. You can interact with the networks and add networks to the configuration. VMware, Inc.
Page 65: View A Configuration Diagram
To view a configuration diagram Move the pointer over the configuration name and select Open. Click the Configuration Diagram tab. View Configuration History You can view change summaries for a configuration. Lab Manager records certain configuration operations, such as adding or removing a network and deploying or undeploying the configuration, as change summaries. Other operations, such as cloning, moving, and archiving, allow you to input change summary text. Change summaries can be helpful for tracking and auditing purposes. To view configuration history Move the pointer over the configuration name and select History. Add a Note to Configuration History You can add a note to a configuration to provide users with additional information or to expand upon the change summaries. To add a note to configuration history Move the pointer over the configuration name and select Open. Click the History tab. Click Add Note. Type the note text and click OK. Lab Manager displays the note text in the Change Summary column. VMware, Inc.
Page 66: Modifying Configurations
To remove a virtual machine from a workspace configuration Move the pointer over the configuration name and select Open. In the Virtual Machines tab, move the pointer over the virtual machine name and select Delete from the menu. Click OK to confirm the deletion. Lab Manager records the removal on the configuration’s History tab. Move Virtual Machines Between Workspace Configurations You can move virtual machines from one configuration to another. A move operation removes the selected virtual machines from the source configuration and adds them to the destination configuration. If you have access to more than one workspace, you can move virtual machines from a configuration in one workspace to a configuration in another workspace. To move virtual machines to another configuration Move the pointer over the configuration name and select Move. Specify the destination workspace, if applicable. Specify the destination. For a new configuration, type a name and description and specify a storage lease. For an existing configuration, select the configuration. (Optional) Type change summary text that will appear on the configuration’s History tab. Specify the virtual machines to move. If you move all the virtual machines in a configuration, Lab Manager deletes the original configuration by default. Deselect the Delete Empty Configuration check box to save the empty configuration. Click OK. VMware, Inc.
Page 67: Combine Workspace Configurations
To combine workspace configurations Move the pointer over the configuration name and select Clone. Specify the destination workspace, if applicable. Select Existing Configuration and select a destination configuration. (Optional) Type change summary text that will appear on the History tab of the source and destination configurations. Specify the type of clone. If the configuration is deployed, you can only create linked clones. Specify the virtual machines to clone. If you are creating full clones, select a datastore. Click OK. Add a Network to a Workspace Configuration Virtual machines in a configuration can connect to any network in the configuration. If you want to connect a virtual machine NIC to a different network, you must first add the network to the configuration. A configuration can include a network to which no virtual machines connect. To add a network to a configuration Move the pointer over the configuration name and select Open. Click the Networks tab. The page displays the networks currently available to virtual machines in the configuration. Click Add Network. Select a network. The list of networks includes the available physical networks and virtual networks. VMware, Inc.
Page 68: Remove A Network From A Workspace Configuration
The page displays the networks currently available to virtual machines in the configuration. Move the pointer over a configuration network name and select Remove. Click OK to confirm. If none of the virtual machines in the configuration connect to the network, the network is removed from the configuration. If the network is being used by any virtual machines, Lab Manager displays an error message stating that the network is in use. You can reassign the NICs of virtual machines to use a different network and try again, or use the Force Remove command to remove the network and disconnect the virtual machine NICs that used the network. Replace a Workspace Configuration Network You can change the network to which a configuration’s virtual machines are connected. For example, if you move or clone a configuration from a development workspace to a production workspace, you could replace a virtual network (used by the virtual machines in the development workspace) with the physical production network. To replace a configuration network Move the pointer over the configuration name and select Open. Click the Networks tab. Move the pointer over a configuration network name and select Replace. Select a compatible replacement network or create a new virtual network based on the current network. If you have the necessary rights, you can also create a network template using the specifications of the new virtual network. (Optional) Type change summary text that will appear on the configuration’s History tab. Click OK. Modify Configuration Properties You can modify configuration properties in the workspace or library. You can also change a configuration’s owner. See “Change Ownership of a Configuration” on page 69 for more information. VMware, Inc.
Page 69: Change Ownership Of A Configuration
To change ownership of a configuration Move the pointer over the configuration name and select Properties. Click Change Owner. Select an organization and user and click OK. If you assign an owner in an organization other than the one in which the configuration was created, make sure that the new organization has the resources required to deploy the configuration. Click OK. Lab Manager reassigns the configuration to the new owner in the primary workspace of the selected organization. Upgrade Virtual Hardware in a Configuration Lab Manager configurations can include version 4 and version 7 virtual machines. If a configuration includes version 4 virtual machines, you can upgrade these virtual machines to version 7. Version 4 virtual machines can run on hosts with ESX 3.5 and above, while version 7 virtual machines require hosts with ESX 4.0 and above. Before you can upgrade a virtual machine to version 7, you must install the latest version of VMware Tools. See “Install VMware Tools” on page 78 for more information. When you upgrade virtual hardware, Lab Manager discards state information and deletes any snapshots associated with the virtual machines. To upgrade configuration virtual hardware, you must first undeploy the configuration. To upgrade configuration virtual hardware Move the pointer over the configuration name and select Upgrade Virtual Hardware. Click OK. Lab Manager deploys the configuration, upgrades the virtual hardware, and undeploys the configuration. VMware, Inc.
Page 70: Discard State For A Configuration
Delete a Configuration You can delete a workspace or library configuration if you no longer need it or to free up disk space on a datastore. You must undeploy a configuration before you can delete it. To delete a configuration Move the pointer over the configuration name and select Delete. Click OK to confirm the deletion. Using LiveLink A LiveLink is the HTTPS URL of a library configuration. You can create a LiveLink and email its URL to another Lab Manager user, who can click it to deploy a copy of the configuration exactly as it was when it was saved to the library. For example, if you are testing software in a workspace configuration and encounter a bug, you can capture the configuration to the library and then create a LiveLink to that configuration. Create a LiveLink You can only create LiveLinks for shared library configurations. See “Share a Configuration” on page 55 for more information. You cannot create a LiveLink of a configuration that includes any virtual machines using DHCP. To create a LiveLink to a configuration On the Library page, move the pointer over a configuration name and select LiveLink. Lab Manager displays the LiveLink URL for the library configuration. Click Copy URL to copy the URL to your Windows clipboard. If you are using the Mozilla Firefox browser, the Copy URL button might not appear. In this case, copy the URL manually. VMware, Inc.
Page 71: Deploy A Livelink
Click Deploy to deploy the configuration in the workspace. The configuration uses its library configuration name with “LiveLink” prefixed to it. For example, “Oracle Linux Bob” becomes “LiveLink – Oracle Linux Bob (n),” where “n” indicates the number of times the LiveLink has been deployed. Exporting Configurations You can export an undeployed workspace or library configuration and all its virtual machine files to vCenter or to an SMB share. When you export a configuration, Lab Manager copies all of its virtual machines to the destination as full clones. The original configuration and all of its virtual machines remain available in Lab Manager. Exported configurations might require a significant amount of disk space on the destination depending on the size of their consolidated virtual disks. Export a Configuration to vCenter You can export a configuration to vCenter if you want to access copies of its virtual machines that are not under Lab Manager control. You cannot import configurations from vCenter, although you can import virtual machines. To export a configuration to vCenter Move the pointer over the configuration name and select Export. Select vCenter. Type an export name. During the export operation, vCenter copies the configuration virtual machines to a folder with the name you specify here. Select a datastore. Click OK. Lab Manager creates consolidated copies of the configuration virtual machines and registers them in vCenter. VMware, Inc.
Page 72: Export A Configuration To An Smb Share
Export a Configuration to an SMB Share You can export a configuration to an SMB share if you want to be able to import a configuration back into Lab Manager at a later time, or if you want to import it into a separate Lab Manager installation. This operation requires that you have a shared folder with full control permissions at the share and file system level. In addition, this operation requires that the datastore on which the configuration virtual machines reside be connected to an ESX host with an open SMB port. Although Lab Manager opens the port during installation, make sure that the port was not closed after the install. To check the port status, run esxcfg-firewall -q smbClient on each host. If the datastore on which the configuration resides is only connected to ESXi hosts, you cannot export to an SMB share. To export a configuration to an SMB share Move the pointer over the configuration name and select Export. Select SMB File Server. Type the UNC path of the directory (relative to the Lab Manager server system) where you want your configuration files stored. Use English characters for the UNC path. A sample path is \\10.6.1.246\VMwareLM\ExportConfigs. Type the user name and password for the export directory, if necessary. Click OK. Lab Manager creates consolidated copies of the configuration virtual machines on the destination. VMware, Inc.
Page 73: Working With Virtual Machines
 “Working with Virtual Machine Snapshots” on page 77  “Managing Virtual Machines” on page 78  “Working with BEA LiquidVMs” on page 87 Deploying and Undeploying Virtual Machines Deploying a virtual machine registers it with vCenter and provides access to Lab Manager operations at the virtual machine console level. Undeploying a virtual machine unregisters it from vCenter. Deploy a Virtual Machine When you deploy a virtual machine from a configuration, Lab Manager deploys all physical and virtual networks associated with the configuration using the network connectivity options that you select, regardless of whether the deployed virtual machine is connected to them. These connectivity settings remain in effect when you deploy other virtual machines in the configuration. To modify the settings, you must undeploy and redeploy the virtual machines. When you a deploy a virtual machine from a configuration that uses fencing or that has a virtual network connected to a physical network, the Lab Manager server requires IP connectivity to the physical network on which the virtual machine is stored. To deploy a virtual machine Move the pointer over a configuration name and select Open. On the Virtual Machines tab, move the pointer over a virtual machine name and select Deploy. VMware, Inc.
Page 74 Select the Connect Virtual Networks to Physical Networks check box to connect virtual networks to physical networks. This option is only available if the virtual machine has a NIC connected to a virtual network. Select a physical network. Select a connectivity mode.  Allow In and Out – Virtual machines can communicate with machines on the selected physical network, and machines on the selected physical network can communicate with virtual machines inside the configuration.  Allow Out – Virtual machines in the configuration can initiate communication with machines on the selected physical network and can receive messages back on the same connection. Machines on the selected physical network cannot initiate communication with virtual machines inside the configuration. Specify the Host Spanning setting. This option is only available if Host Spanning is enabled and the configuration uses fencing or a virtual network. To boot the virtual machine in the sequence specified during the configuration creation, select the Use Server Boot Sequence check box. To prevent Lab Manager from powering on a virtual machine immediately after deployment, deselect the Power On Machines After Deployment check box. Use this option when you need to manually bring up a virtual machine. For example, you might need to ensure a database, application, and Web server are working individually rather than all at once. To recustomize the virtual machine, select the Force Re‐customization check box. If customization failed in a previous deploy operation, or if you changed the network settings for a virtual machine in the guest operating system, you might have to force recustomization. See “Customizing the Guest Operating System” on page 40. Specify a resource pool on which to deploy the configuration or select Any Available. 10 Specify a time to undeploy the configuration. 11 (Optional) Type change summary text that will appear on the configuration’s History tab. 12 Click OK. VMware, Inc.
Page 75: Undeploy A Virtual Machine
From the virtual machine console page, you can view information about a virtual machine, work with the guest operating system, and perform operations that affect the guest operating system. For a configuration that includes multiple virtual machines, you can view a virtual machine’s console page or view a page that displays the consoles of all the virtual machines. View a Virtual Machine Console You can view the virtual machine console for a deployed virtual machine or virtual machine template from a workspace or from the VM Templates pages. The virtual machine console provides access to the guest operating system that is running on a virtual machine and to operations that affect the guest operating system. To view a virtual machine console, you must install either the ActiveX control (for Internet Explorer) or the VMware Remote MKS Plugin (for Firefox). If the Active X control or VMware Remote MKS Plugin is not installed, you are prompted to install it the first time that you try to view a virtual machine console. To view a virtual machine console in a configuration Move the pointer over the configuration name and select Open. Move the pointer over the virtual machine name and select View Console or Pop Out Console. The virtual machine console page displays the internal and external (if applicable) IP addresses of a virtual machine. If the virtual machine has a revert point, Lab Manager displays a thumbnail icon of the snapshot. For a configuration that includes multiple virtual machines, the Configuration drop‐down menu provides access to other virtual machines in the same configuration. To view the virtual machine console of a virtual machine template In the left pane, click VM Templates.
Page 76: View All Virtual Machine Consoles
Lab Manager User’s Guide View All Virtual Machine Consoles You can view the virtual machine consoles for all virtual machines in a configuration. The consoles page provides access to the guest operating systems that are running on the virtual machines and to operations that affect the guest operating systems. To view virtual machine consoles, you must install either the ActiveX control (for Internet Explorer) or the VMware Remote MKS Plugin (for Firefox). If the Active X control or VMware Remote MKS Plugin is not installed, you are prompted to install it the first time that you try to view all virtual machine consoles. To view all virtual machine consoles in a configuration Move the pointer over the configuration name and select Show Consoles. Lab Manager displays the consoles for all the virtual machines in the configuration. Stopping and Starting Virtual Machines You can stop a virtual machine from running by using the suspend, power off, or shut down operations. Undeploying a virtual machine also stops it from running. Suspend a Virtual Machine Suspending a deployed virtual machine freezes its CPU. Suspend a machine when you need to step away from ...
Page 77: Reset A Virtual Machine
Take a Snapshot of a Virtual Machine When you take a virtual machine snapshot, Lab Manager captures the state of the virtual machine. You can revert the virtual machine to that snapshot at a later time. You can only take a snapshot of a deployed virtual machine. Only one snapshot of a virtual machine can exist at a time. Taking a new snapshot replaces the previous one. To take a virtual machine snapshot From the virtual machine console page, move the pointer over the virtual machine name and select Snapshot. Lab Manager powers off the virtual machine for a short time and then displays the console. A thumbnail icon of the snapshot appears on the console page. Revert to a Virtual Machine Snapshot When you revert a virtual machine to a snapshot, the virtual machine loses its current state. If you revert to a virtual machine snapshot, Lab Manager retains the snapshot so that you can revert to it again later. To revert to a snapshot From the virtual machine console page, move the pointer over the virtual machine name and select Revert. Click OK to revert to the last snapshot of the machine and lose the current state of the machine. Lab Manager turns off the virtual machine for a short time and then displays the console. VMware, Inc.
Page 78: Delete A Virtual Machine Snapshot
Delete a Virtual Machine Snapshot Virtual machine snapshots take up space on datastores. You can free up space by deleting snapshots. To delete a snapshot From the virtual machine console window, move the pointer over the virtual machine name and select Delete Revert Point. Click OK to confirm. Lab Manager deletes the snapshot and removes its thumbnail icon from the console page. Managing Virtual Machines Managing virtual machines involves a number of tasks, including installing VMware Tools, accessing media files, modifying virtual machine properties, and consolidating virtual machines. Install VMware Tools Lab Manager uses VMware Tools to customize the guest operating system. VMware Tools also allows you to move the pointer into and out of the virtual machine console window. Without VMware Tools, you can lose the pointer when navigating in and out of the console window. Installing VMware Tools takes several minutes and requires you to restart the virtual machine. For more information about the installation, see vSphere documentation. To install VMware Tools From the virtual machine console page, click in the console to work with the guest operating system. Log in to the guest operating system inside the virtual machine console. Click Install VMware Tools. The rest of the procedure depends on the guest operating system. For more information, see: ...
Page 79: Eject A Cd
Floppy. Select a floppy file from the media library and click OK. Eject a Floppy Disk After you finish using a floppy disk you can eject it. To eject a floppy disk from a virtual machine From the virtual machine console page, move the pointer over the virtual machine name and select Eject Floppy. Create a Remote Desktop Connection File You can create a Remote Desktop Connection file to connect to a virtual machine from your desktop. The virtual machine must be running a Windows guest operating system and have customization enabled. Before you create a Remote Desktop Connection file, enable Remote Desktop in the virtual machine guest operating system. To create a Remote Desktop Connection file On the virtual machine console page, click Remote Desktop and save the Remote Desktop Connection file. VMware, Inc.
Page 80: Connect Remotely To A Virtual Machine
To modify other properties, see “Modifying Virtual Machine Hard Disks” on page 82, “Modifying Virtual Machine Network Interfaces” on page 83, “Enable Memory Hot Add” on page 85, and “Enable Virtual CPU Hot Add” on page 86. To modify virtual machine properties Move the pointer over the configuration name and select Open. On the Virtual Machines tab, move the pointer over the virtual machine name and select Properties. Change any of the following properties.  Name – Can only contain alphanumeric characters (a–z, A–Z, 0–9), hyphens, underscores, or periods. Maximum length is 20 characters.  Description – (Optional) Maximum number of characters is 128.  Guest OS – If you select a 64‐bit guest operating system, the datastore must be connected to an ESX/ESXi host that provides the required 64‐bit processor for that guest OS. You can proceed without fulfilling this requirement, but you cannot deploy the virtual machine until you attach a host with the correct processor. If you have some but not all 64‐bit hosts, Lab Manager limits the number of hosts on which the virtual machine can be deployed. For information on enabling a host to provide 64‐bit support, see the vSphere documentation.  32‐bit Virtual CPU – By default, the virtual CPU type assumes the physical host CPU type. Select this check box to override the default behavior and ensure that the virtual CPU type is 32‐bit. For example, you might have 64‐bit ESX/ESXi hosts that do not have the required software (kernel or drivers) for a Solaris guest operating system. Another example involves a mixed (32‐bit and 64‐bit) ESX/ESXi host environment where you need to complete a testing process specifically on a 32‐bit guest operating system, and the operating system accommodates both 32‐bit and 64‐bit CPU architecture. VMware, Inc.
Page 81  Memory Reservation (MB) – Minimum amount of memory set aside for the virtual machine.  Memory Priority – Priority for shares of memory.  Memory Shares – Relative amount of memory for a virtual machine compared to other virtual machines in the same configuration.  Memory Limit (MB) – Maximum amount of memory available for the virtual machine. See the vSphere documentation for details on memory priorities, shares, reservations, and limits.  Use Time Synchronization – Enables time synchronization between the guest (virtual machine) and ESX/ESXi host operating systems. You must install VMware Tools to use this option.  Perform Customization – Specifies whether guest customization is enabled.  Boot Sequence – Integer (0‐n) indicating the boot sequence for the virtual machine. You do not need to use sequential numbers. Lab Manager can determine the relative order.  Boot Delay – Delay in seconds between the bootup process of this machine and the next machine.  SID mechanism – Specifies the mechanism Lab Manager uses to change the SID. You can switch the default tool Lab Manager uses to change the SID, or select None. To use Microsoft Sysprep, you must first create a Microsoft Sysprep package for guest customization. See “Build a Microsoft Sysprep Package” on page 41.  Deployment Lease or Storage Lease – Depending on whether the virtual machine is deployed or not, this option allows you to update a time to undeploy the virtual machine or delete the virtual machine (or mark it for deletion).  System Messages – Messages or alerts about vCenter activity that could raise errors in Lab Manager. Click Clear All to remove system messages. Click Update. VMware, Inc.
Page 82: Modifying Virtual Machine Hard Disks
You can add one or more virtual hard disks (.vhd files) to an undeployed virtual machine. To add a virtual hard disk Move the pointer over the configuration name and select Open. On the Virtual Machines tab, move the pointer over the virtual machine name and select Properties. In the Hard Disks section, click Add Hard Disk. Type the disk size (GB). Select the disk bus type. Select a bus number. Select a bus ID and click OK. Click Update. You can now deploy the virtual machine and use the guest operating system tools to partition and format the new disk. If you add a SCSI hard disk to a virtual machine, the guest operating system might generate an error message about missing drivers the next time that you power on the virtual machine. If this error occurs, download and install the appropriate driver, and contact VMware for further support. Edit a Virtual Machine Hard Disk You can update the bus number and bus ID of a virtual machine hard disk. To edit a virtual machine hard disk Move the pointer over the configuration name and select Open. On the Virtual Machines tab, move the pointer over the virtual machine name and select Properties. In the Hard Disks section, click Edit. Modify the bus number and bus ID and click OK. Click Update. VMware, Inc.
Page 83: Delete A Virtual Machine Hard Disk
To edit network interface settings Move the pointer over the configuration name and select Open. On the Virtual Machines tab, move the pointer over the virtual machine name and select Properties. In the Network Interfaces section, change any of the following settings:  Deselect the Connected check box to disconnect a virtual NIC.  Select a network from the Network drop‐down menu. The available options are based on the networks in the virtual machine template. If you have access to other networks in Lab Manager, you can add them to the configuration and they will appear here. See “Add a Network to a Workspace Configuration” on page 67.  Specify a primary NIC. The primary NIC setting determines the default and only gateway for the virtual machine. The virtual machine can use any NIC to connect to other machines that are directly connected to the same network as the NIC, but it can only use the primary NIC to connect to machines on networks that require a gateway connection. Consider this behavior when selecting a primary NIC, especially if you plan to deploy configurations that use fencing or connect virtual networks to physical networks.  Select an IP addressing mode for the network. The available options are based on the IP addressing modes available to the selected network.  Static ‐ IP Pool pulls static IP addresses from the IP address pool.  DHCP pulls IP addresses from a DHCP server. This option avoids the preparation and specification of an IP address or IP range. However, you cannot use Lab Manager fencing or connect virtual networks to physical networks with DHCP.  Static ‐ Manual allows you to specify an IP address.  If you selected Static ‐ Manual, type an IP address in the IP Address text box. Click Update. VMware, Inc.
Page 84: Reset A Network Interface Mac Address
To add a network interface Move the pointer over the configuration name and select Open. On the Virtual Machines tab, move the pointer over the virtual machine name and select Properties. In the Network Interfaces section, click Add Interface. Lab Manager adds and connects a new virtual NIC. (Optional) Edit the virtual NIC settings. Deselect the Connected check box to disconnect the virtual NIC. Select a network from the Network drop‐down menu. The available options are based on the networks in the virtual machine template. If you have access to other networks in Lab Manager, you can add them to the configuration and they will appear here. See “Add a Network to a Workspace Configuration” on page 67. Specify a primary NIC. The primary NIC setting determines the default and only gateway for the virtual machine. The virtual machine can use any NIC to connect to other machines that are directly connected to the same network as the NIC, but it can only use the primary NIC to connect to machines on networks that require a gateway connection. Consider this behavior when selecting a primary NIC, especially if you plan to deploy configurations that use fencing or connect virtual networks to physical networks. Select an IP addressing mode for the network. The available options are based on the IP addressing modes available to the selected network.  Static ‐ IP Pool pulls static IP addresses from the IP address pool.  DHCP pulls IP addresses from a DHCP server. This option avoids the preparation and specification of an IP address or IP range. However, you cannot use Lab Manager fencing or connect virtual networks to physical networks with DHCP.  Static ‐ Manual allows you to specify an IP address. If you selected Static ‐ Manual, type an IP address in the IP Address text box. Click Update. VMware, Inc.
Page 85: Delete A Network Interface
When you upgrade virtual hardware, Lab Manager discards state information and deletes any snapshots associated with the virtual machine. Before you can upgrade a virtual machine to version 7, you must install the latest version of VMware Tools. To upgrade virtual machine virtual hardware, you must first undeploy the virtual machine. To upgrade virtual machine virtual hardware Move the pointer over the configuration name and select Open. On the Virtual Machines tab, move the pointer over the virtual machine name and select Upgrade Virtual Hardware. Click OK. Lab Manager deploys the virtual machine, upgrades the virtual hardware, and undeploys the virtual machine. Enable Memory Hot Add For a version 7 virtual machine running a guest OS that supports it, you can enable memory hot add. This feature allows you to add memory to a deployed and powered on virtual machine. See “Guest Operating System Support” on page 161 for information about which guest operating systems support memory hot add. To enable memory hot add Move the pointer over the configuration name and select Open. On the Virtual Machines tab, move the pointer over an undeployed virtual machine name and select Properties. Select Memory Hot Add. Click Update. VMware, Inc.
Page 86: Enable Virtual Cpu Hot Add
You can only discard state for undeployed virtual machines with saved state. To discard state for a virtual machine Move the pointer over the configuration name and select Open. On the Virtual Machines tab, move the pointer over the undeployed machine name and select Discard State. Click OK to confirm. Consolidate a Virtual Machine Each time you create a linked clone of a virtual machine, Lab Manager freezes the virtual hard disk associated with the original virtual machine and creates delta disks to store future changes to the clone and its source. Over time, the increasing number of delta disks stored across the directories of a datastore can affect performance. You do not need to consolidate virtual machines until Lab Manager generates an error requesting this operation. You can also use this operation to move a virtual machine to a different datastore. Consolidating a virtual machine can take an extended period of time, depending on the disk size and storage performance. Consolidation reduces the free space on datastores because the virtual machine no longer benefits from delta disks. You can consolidate virtual machines in both workspace and library configurations. To consolidate a virtual machine Move the pointer over the configuration name and select Open. If the virtual machine is deployed, undeploy it. On the Virtual Machines tab, move the pointer over the virtual machine name and select Consolidate. Select a datastore for the consolidated virtual machine and click OK. VMware, Inc.
Page 87: Working With Bea Liquidvms
Chapter 8 Working with Virtual Machines Working with BEA LiquidVMs Lab Manager supports importing BEA LiquidVMs as virtual machine templates from vCenter or an SMB file server. See “Importing Virtual Machine Templates” on page 32. Before you can work with a LiquidVM, you must do the following:  Make sure that the media library includes all the versions of the WLS‐VE ISO that you need. Different versions are available for different versions of LiquidVM. See “Managing Media Stores” on page 100.  Deploy the LiquidVM, view the console, and use the Insert CD command to insert the WLS‐VE ISO. Although you can add multiple NICs to a LiquidVM, Lab Manager only uses the primary NIC. VMware, Inc.
Page 88 Lab Manager User’s Guide VMware, Inc.
Page 89: Managing Resources
 “Managing Datastores” on page 94  “Managing Media Stores” on page 100  “Managing Physical Networks” on page 102  “Managing Host Spanning Transport Networks” on page 103 Managing Resource Pools Lab Manager provides access to VMware vCenter resource pools. Resource pools provide the CPU and memory resources for Lab Manager virtual machines. Enable or Disable a Resource Pool By default, only system administrators can enable and disable resource pools. To enable or disable a resource pool In the left pane, click Resources. Move the pointer over the resource pool and select Enable or Disable. Click OK. Lab Manager enables or disables the resource pool. VMware, Inc.
Page 90: Modify Resource Pool Properties
To undeploy all virtual machines in a resource pool In the left pane, click Resources. Move the pointer over the resource pool and select Disable. Click OK. Move the pointer over the resource pool and select Undeploy All VMs. For the Global organization, Lab Manager undeploys all the virtual machines deployed on hosts in the resource pool. For other organizations, Lab Manager undeploys only the virtual machines from configurations deployed by users in the selected organization. Click OK. Lab Manager undeploys the virtual machines in the resource pool. Detach a Resource Pool Before you can detach a resource pool, you must disable it and undeploy all virtual machines associated with it. See “Enable or Disable a Resource Pool” on page 89 and “Undeploy All Virtual Machines on a Host” on page 93 for more information. By default, only system administrators can detach resource pools. To detach a resource pool In the left pane, click Resources. Click the Resource Pools tab. Move the pointer over the resource pool and select Disable. Click OK. Move the pointer over the resource pool and select Detach. Click OK. Lab Manager detaches the resource pool. VMware, Inc.
Page 91: Managing Hosts
To prepare a host In the left pane, click Resources. On the Hosts tab, move the pointer over the host name and select Prepare. Select or deselect the check box that specifies whether to use the same user name and password for all hosts. If you selected the check box, type the user name and password. Select the check boxes next to the hosts that you want to prepare. Type user names and passwords, if necessary. Click Next. Select the datastores that you want to enable for virtual machine use. Click Finish. Enable and Disable Hosts When you disable a host, Lab Manager prevents the deployment of new virtual machines on the host. Virtual machines that are already deployed on the host are unaffected. To perform maintenance on a host, you need to undeploy the virtual machines. See “Undeploy All Virtual Machines on a Host” on page 93. To unprepare a host, you must first disable it. By default, only system administrators can enable and disable hosts. To enable or disable a host In the left pane, click Resources. On the Hosts tab, move the pointer over the host and select Enable or Disable. Click OK. Lab Manager enables or disables the host. VMware, Inc.
Page 92: Disable And Enable Host Spanning For A Host
Unprepare a Host Unpreparing a host allows you to remove it from the Lab Manager environment. By default, only system administrators can unprepare hosts. To unprepare a host In the left pane, click Resources. In the Hosts tab, move the pointer over the host name and select Unprepare. Click Unprepare. During this process, Lab Manager tries to uninstall the agent. If this attempt fails, Lab Manager continues to unprepare the host and an error message appears. Modify Host Properties By default, only system administrators can modify host properties. To modify host properties In the left pane, click Resources. On the Hosts tab, move the pointer over the host and select Properties. After you have modified the properties, click OK. Lab Manager updates the host’s properties. The Maximum Number of VMs field is only available for a cluster without DRS and applies to the machines deployed in this installation. If this option is managed by DRS, you cannot modify it. The maximum quota for deployed virtual machines on a host can increase in these circumstances:  A VMotion or VMware HA failover.  Switching a DRS cluster to a cluster without DRS, where the default quotas associated with the non‐DRS cluster can negate the Lab Manager quota. VMware, Inc.
Page 93: View Deployed Virtual Machines On A Host
System administrators can select this option in the Global organization to view all the virtual machines deployed on the host across the entire Lab Manager installation.  Deployed Machines in Other Organizations – View all your deployed machines in organizations other than the selected organization. This option is not available from the Global organization or for users who are members of one organization. Undeploy All Virtual Machines on a Host System administrators can undeploy all the virtual machines associated with a host, which is useful when you want to complete maintenance on a host. Undeploying these virtual machines can result in partially deployed configurations, and the undeployed virtual machines must be manually redeployed. When you select Undeploy all VMs, the virtual machines are suspended, but their state is saved. To undeploy all virtual machines on a host In the left pane, click Resources. In the Hosts tab, move the pointer over the host name and select Undeploy All VMs. In the Global organization, Lab Manager undeploys all the virtual machines deployed on the host. For the other organizations, only the virtual machines deployed by users in the selected organization are undeployed. Click OK. Lab Manager undeploys the virtual machines. If the undeploy operation does not work, move the pointer over the host name and select Force Undeploy. VMware, Inc.
Page 94: Redeploy All Virtual Machines On A Different Host
In the Hosts tab, move the pointer over the host name and select Disable. Click OK. Move the pointer over the host name and select Redeploy All VMs. In the Global organization, Lab Manager undeploys all the virtual machines deployed on the host. For the other organizations, only virtual machines deployed by users in the selected organization are undeployed. Click OK. Lab Manager redeploys the virtual machines. When you select Redeploy all VMs, the virtual machines are suspended, but their state is saved. Repair a Host If the agent cannot be contacted, if the service VM is powered off, or if a host cannot be enabled or disabled for Host Spanning, you can repair the host. To repair the host In the left pane, click Resources. In the Hosts tab, move the pointer over the host name and select Repair. Lab Manager completes the repair and enables Host Spanning. See “Host Spanning” on page 59 for information. Managing Datastores Lab Manager supports VMFS and NFS datastores, which it accesses through vCenter. You can add datastores by attaching them to ESX/ESXi hosts in vCenter. VMware recommends shared storage (NFS, iSCSI, or Fiber Channel). If you store virtual machine files on local (not shared) storage, you can only deploy the virtual machines on the local ESX/ESXi host. Datastores can also be enabled as media stores. See “Managing Media Stores” on page 100. There is a limit of eight managed servers (hosts) per LUN. If you exceed this limit, an error message appears. See http://kb.vmware.com/kb/1003319 for more information. VMware, Inc.
Page 95: Delete A Datastore
In the left pane, click Resources. On the Datastores tab, move the pointer over the datastore and select Delete. Click OK. Lab Manager deletes the datastore. Remove a Datastore You can only remove a datastore from an organization other than Global. Removing a datastore deletes the datastore as a resource from just that organization. The datastore is available to the other organizations in Lab Manager. To remove a datastore In the Organization drop‐down menu, select an organization other than Global. In the left pane, click Resources. On the Datastores tab, move the pointer over the datastore and select Remove. Click OK. Enable and Disable Datastores As the system administrator, you can enable and disable datastores. When you disable a datastore, you cannot deploy the configurations associated with the datastore, create virtual machines on the datastore, or create a media store on the datastore. To enable or disable a datastore In the left pane, click Resources. In the Datastores tab, move the pointer over the datastore and select Enable or Disable. Click OK. Lab Manager enables or disables the datastore. VMware, Inc.
Page 96: Disable Virtual Machine Creation In A Datastore
Click OK. Lab Manager disables virtual machine creation on the datastore. Disable Media Store Creation in a Datastore If you do not want to completely disable a datastore, you can disable it for media store creation only. To disable media store creation in a datastore In the left pane, click Resources. In the Datastores tab, move the pointer over the resource and select Disable Media. Click OK. Lab Manager disables media store creation in a datastore. Modify Datastore Properties By default, only system administrators can modify datastore properties. To modify datastore properties In the left pane, click Resources. On the Datastores tab, move the pointer over the datastore and select Properties. Change the display name and disk space thresholds. If necessary, clear messages about vCenter activity. Click OK. Datastore properties have been modified. VMware, Inc.
Page 97: View Virtual Machine Datastore Usage
Cleanup Date – Displays the date that the virtual machine’s storage lease expires. Depending on the resource cleanup settings specified by the system administrator, Lab Manager deletes the virtual machine or marks it for deletion. See “Configuring Resource Cleanup Settings” on page 143. Using the pop‐up menu, you can view the high‐level topography of the virtual machine directories, consolidate and delete virtual machines, and access virtual machine properties. View Virtual Machine Datastore Directories In the Context view, the chain of virtual machine and internal node directories are to the right of the ancestor directories. The boxes with thick borders represent virtual machines that you can see in the Web console. The boxes with lighter borders represent the hidden internal directories associated with the virtual machines. Deletion of internal nodes only occurs as a side effect of deleting the virtual machines associated with those nodes. To view virtual machine datastore directories In the left pane, click Resources. On the Datastores tab, click View Datastore Usage. To view the usage on a single datastore, move the pointer over the datastore name and select Open. Click Refresh Disk Space to ensure that the data is current. Move the pointer over the virtual machine name and select Context. To move data from one datastore to another, you can use SSMove, which is a utility installed on the Lab Manager server. The SSMove utility is found in: C:\Program Files\VMware\VMware Lab Manager Server\Tools\SSMove. See Appendix D, “Using SSMove,” on page 163 for more information. VMware, Inc.
Page 98: Understanding Virtual Machine Datastore Directories
Deleting a virtual machine deletes the storage occupied by the virtual machine node and ancestor nodes that can be safely deleted. Lab Manager does not delete an ancestor node in the following situations:  The ancestor directory has other child directories that depend on it.  A virtual machine (for example, a virtual machine template or virtual machine in the configuration library) is associated with the ancestor node.  Another node is using the ancestor node as a revert point. For example, a full clone operation might consolidate and create a new disk but refer to the revert point of the original chain. Figure 9‐1 shows a basic example of a tree of related virtual machines and the internal nodes affected by a delete operation. Figure 9-1. Example of Nodes Affected by a Delete Operation If you delete node D, node B stays intact because node C and E depend on it. If you delete node E, the space for node E and node C becomes available because the deletion affects all nodes up to a directory with child dependencies (node B). If you move the pointer over a box, details, such as the owner’s name, the configuration in which this virtual machine is located, chain length, and the amount of space the virtual machine or internal node consumes, are displayed. Previously deployed and currently deployed virtual machines display information about when they were previously deployed. Internal nodes do not display this information. A turquoise box indicates a revert reference, which means that another directory (created by a full clone operation on a different datastore) exists outside the displayed directory tree but uses a directory linked to this revert reference as a revert point. To delete a directory linked to a revert reference, you need to delete the virtual machine associated with the revert reference and the descendants of the directory. VMware, Inc.
Page 99: Delete Expired Virtual Machines
143. You can renew the storage lease for virtual machines that are marked for deletion in the Virtual Machine Datastore Usage page. By default, only a system administrator and an administrator with rights at the organization level can review storage leases. To renew the storage lease for an expired virtual machine In the left pane, click Resources. On the Datastores tab, click View Datastore Usage. To view the usage on one datastore, move the pointer over the datastore name and select Open. Click Refresh Disk Space to ensure the data is current. Move the pointer over the expired virtual machine name and select Renew Storage Lease. Click OK. Lab Manager renews the storage lease for the selected virtual machine and all other virtual machines in its configuration (if applicable) and updates the Cleanup Date column to reflect the new lease expiration date. Expired leases are renewed for the same period as the original lease (for example, 30 days). Delete Revert Points Revert points take up space on datastores so deleting them frees up space. To delete a revert point In the left pane, click Resources. On the Datastores tab, click View Datastore Usage. To view the usage on one datastore, move the pointer over the datastore name and select Open. The Revert Point Datastore lists the datastore on which the revert point is stored. VMware, Inc.
Page 100: Consolidate A Virtual Machine Based On Datastore Usage
To delete a virtual machine or configuration based on datastore usage In the left pane, click Resources. On the Datastores tab, click View Datastore Usage. To view the usage on one datastore, move the pointer over the datastore name and select Open. Move the pointer over an undeployed virtual machine name and select Delete (virtual machine) or Delete Configuration (configuration with the virtual machine). Click OK. Lab Manager deletes the machine or configuration. Managing Media Stores A media store is an NFS or VMFS datastore that contains a directory for media. Use media stores to store CD, DVD, and floppy images of operating systems and applications that you need to install on Lab Manager virtual machines. You must add media files to media stores outside of the Lab Manager environment and then synchronize the Lab Manager media library with the media stores. Add Media Stores To add a media store, you must enable an NFS or VMFS datastore for media. You can use different directories on the same datastore for media and virtual machines. For information on NFS and VMFS datastore requirements, see the Lab Manager Installation and Upgrade Guide. By default, only system administrators can add media stores. To add a media store Click Resources in the left pane. Select the organization to which you want to add the media store from the Organization drop‐down menu. Select Global to add the media store as a resource available to all organizations, but assigned to none. You can assign it to organizations later. VMware, Inc.
Page 101: Synchronize A Media Store
Enable and Disable a Media Store By default, system administrators can enable and disable media stores. When you disable a media store, you cannot access the media files stored on the media store. Use the disable operation to block the use of a media store. To enable or disable a media store In the left pane, click Resources. On the Media Stores tab, move the pointer over the media store and select Enable Media Store or Disable Media Store. Click OK. Lab Manager enables or disables the media store. Change the Name of a Media Store By default, only system administrators can change the name of a media store. To change the name of a media store In the left pane, click Resources. On the Media Stores tab, move the pointer over the media store and select Properties. Change the name of the media store and click OK. VMware, Inc.
Page 102: Managing Physical Networks
Add or Remove IP Addresses to the IP Pool of a Physical Network Only system administrators can add IP addresses to a physical network. To add or remove IP addresses to the IP pool of a physical network In the left pane, click Resources. On the Physical Networks tab, move the pointer over a physical network name and select Properties. Click the General tab. Type an IP address or IP address range in the Static IP Address Pool text box and click Add or select an IP address or IP address range and click Remove. Click Update. Modify Physical Network Properties By default, only system administrators can modify a physical network. To modify a physical network In the left pane, click Resources. On the Physical Networks tab, move the pointer over a physical network name and select Properties. VMware, Inc.
Page 103: Delete A Physical Network
View Host Spanning Transport Networks In the Organization drop‐down menu, select an organization to see the transport networks available to that organization. Selecting Global displays all the available host spanning transport networks in Lab Manager. To view host spanning transport networks In the left pane, click Resources. Click the Host Spanning Transport Network tab. Lab Manager displays the available host spanning transport networks in the selected organization. In Global, in the In Use By column, the number of networks that are using a host spanning transport network is displayed. Disable or Enable Host Spanning By default, only system administrators can disable and enable Host Spanning. You can disable and enable Host Spanning for an organization or for the entire installation. To disable or enable Host Spanning In the left pane, click Resources. On the Host Spanning Transport Networks tab, deselect or select the Enable Host Spanning check box. Click OK. Lab Manager disables or enables Host Spanning for the selected organization. When you disable Host Spanning, currently deployed configurations are unaffected and continue to use Host Spanning until you undeploy or redeploy them. VMware, Inc.
Page 104: Enable Or Disable A Host Spanning Transport Network
To remove a host spanning transport network In the left pane, click Resources. On the Host Spanning Transport Networks tab, move the pointer over the network name and select Remove. Click OK. Modify Host Spanning Transport Network Properties Only a system administrator can modify transport network properties. To modify transport network properties In the left pane, click Resources. On the Host Spanning Transport Networks tab, move the pointer over the transport network name and select Properties. Modify the properties.  Select a vNetwork Distributed Switch.  Type a VLAN identifier.  Select the check box to enable the network for Host Spanning.  Update the maximum transmission unit (MTU). MTU is the maximum amount of data (packet size) that can be transmitted in one packet before it has to be split into smaller packets.  Select the check box to and type a display name for the transport network in Lab Manager. Click OK. Lab Manager modifies the transport network’s properties. VMware, Inc.
Page 105: Managing The Media Library
“Restrict Access to Media Files” on page 106  “Modify Media Properties” on page 107 Synchronize the Media Library with Media Store Files You can synchronize the contents of the Lab Manager media library with the contents of the media store directories on all your datastores. Synchronizing adds files to or deletes files from the library. When you synchronize the media library, you become the owner of the added media. See “Synchronize a Media Store” on page 101 to synchronize the contents of a media store with the Lab Manager media library. Media files have the following requirements:  CD and DVD files must end with .iso.  Floppy disk files must end with .img, .vfd, or.flp. To synchronize the media library with media store content Select the organization that contains the media stores you want to synchronize. Select Global to synchronize all media stores. Click Synchronize Media and click OK. Lab Manager synchronizes the media library with media store content. VMware, Inc.
Page 106: Change Ownership Of Media Files
Restrict Access to Media Files When you add media files to the Lab Manager media library, the files are shared with all Lab Manager users in all organizations. If you are the owner of a media file, or if your user role includes the Administrator View and Control right, you can limit access to a media file by modifying its sharing properties. Depending on your rights, you can restrict access to users in a specific workspace or organization. When you share a media file, you can specify access rights for the users with whom you are sharing the media. Access rights combine with the rights provided by a user’s role to determine how that user can interact with the shared media file. Access rights cannot provide users with rights that they do not already have based on their role. Users can only access media that resides on media stores that are available to their organization and workspace. To modify media sharing properties In the left pane, click Media. Move the pointer over the media name and select Sharing. The Sharing Media dialog box displays the users and organizations that currently have access to the media and their level of access control. Click Remove to stop sharing the media with a user or group. Click Add Users to share the media with a user or group. Select the organization containing the users with whom you want to share the media or select Global to view users from all organizations. Select with whom you want to share the media.  Everyone in Organization shares the media with all users in the selected organization.  Everyone in Workspace shares the media with all users in the selected workspace.  Selected Users shares the media with specific users in the selected organization. Select the check box next to each user with whom you want to share the media. Specify the access rights for the users and click OK. Click OK and Done. VMware, Inc.
Page 107: Modify Media Properties
Chapter 10 Managing the Media Library Modify Media Properties You can change the display name and add comments for media files in the properties information. You can also change the media file owner. See “Change Ownership of Media Files” on page 106. To modify media properties In the left pane, click Media. Move the pointer over a media filename and select Properties. Change the display name for the media file. Type your comments about the media file. Click OK. Lab Manager modifies the properties of the media file. VMware, Inc.
Page 108 Lab Manager User’s Guide VMware, Inc.
Page 109: Managing Users, Groups, And Roles
Users cannot log in to the Lab Manager system or access any resources until they are added to an organization. This chapter includes the following topics:  “Managing Users” on page 109  “Managing Stranded Users” on page 111  “Managing Groups” on page 112  “Managing Roles and Rights” on page 113 Managing Users By default, only a system administrator or an administrator with rights at the organization level can manage users. Disable or Enable Users By default, only the system administrator can disable and enable users in the Global organization. When you disable users, they are logged out of the Web console and cannot log in until they are enabled. To disable or enable a user In the left pane, select Users and Groups. In the Organization drop‐down menu, select Global. Click the Users tab. Move the pointer over the user name and select Disable or Enable. Click OK. Lab Manager disables or enables the user. VMware, Inc.
Page 110: Remove A User From An Organization
When system administrators delete a user from the entire installation, Lab Manager removes the user from all organizations, deletes all the private objects (for example, media, undeployed configurations, and virtual machine templates) of the user, and reassigns the shared objects to the system administrator who is currently logged in. To delete a user from Lab Manager In the left pane, select Users and Groups. Select Global. Click the Users tab. Move the pointer over the user name and select Disable. Click OK. Move the pointer over the user name and select Delete. Click OK. Lab Manager deletes the user from the entire installation. Modify User Properties By default, only system administrators and administrators with rights at the organization level can modify user properties. For LDAP users, you can only modify the user’s role, stored virtual machine template and library configuration quota, and deployed virtual machine template quota. Because these properties are specific to an organization, a user who is a member of two organizations can have a different role or quota in each organization. To modify user properties In the left pane, select Users and Groups. Select the organization for which you want to modify the user properties. Select Global to modify the user properties for all organizations. Click the Users tab. Move the pointer over the user name and select Properties. VMware, Inc.
Page 111: View User Roles And Organizations
In the left pane, select Users and Groups. Click the Users tab. Move the pointer over the user name and select Properties. Send User Notifications You can send an email notification to all the users in a workspace, organization, or the entire installation. You can also send an email to users with deployed virtual machines in a specific resource pool or with virtual machines stored on a specific datastore. Before you can send an email notification, you need to verify your SMTP settings in the Web console. See “Set Email Preferences” on page 137. To send an email notification In the left pane, select Users and Groups. Click the Users tab. In the Organization drop‐down menu, select an organization. Select Global if you want to send an email to users with deployed virtual machines in a specific resource pool or with virtual machines stored on a specific datastore. Click Send Notification. Select the recipients. Type the subject and message and click Send. Lab Manager sends an email notification. Managing Stranded Users When a user who owns objects (such as virtual machine templates, configurations, or media) is removed from an organization, the user is stranded. When you disable an organization, all its users are stranded. All the Lab Manager objects (media, virtual machine templates, and so on) owned by a stranded user are saved. A system administrator or administrator with rights at the organization level can assign these objects a new owner. You must reassign ownership of a stranded user’s objects before you can delete the user. VMware, Inc.
Page 112: Reassign Ownership Of All Stranded Users' Objects
Remove a Group from an Organization When you remove a group from an organization, other than Global, the group is still available to the other organizations. Removing groups can result in stranded users. See “Managing Stranded Users” on page 111. To remove a group In the left pane, select Users and Groups. Select the Groups tab. In the Organization drop‐down menu, select the organization from which you want to remove the group. Move the pointer over the group name and select Remove. Click OK. Lab Manager removes the group from the organization. Delete a Group from Lab Manager By default, only a system administrator can delete a group from Lab Manager. When you delete a group from Global, the group is no longer available in Lab Manager. To delete a group from Lab Manager In the left pane, select Users and Groups. Select the Groups tab. In the Organization drop‐down menu, select Global. VMware, Inc.
Page 113: Modify Group Properties
Lab Manager includes the following predefined roles:  System Administrator – Includes all rights across Lab Manager. System administrators can access all organizations and perform all operations. They are the only users who can access the Global organization. This is the only role that cannot be modified.  Administrator – Can do almost anything in an organization or a workspace, except add or delete organization resources (datastores, media stores, resource pools, or physical networks). A user can be an administrator at the organization or workspace level.  Template Creator – Can create virtual machine templates, network templates, and configurations in an organization.  Application Owner – Can create configurations in an organization.  User – Can deploy and edit configurations in an organization and check out and view LiveLink Library configurations.  View Only – Can only display workspace configurations. See Appendix A, “Roles and Rights,” on page 149 for more information about the rights assigned to predefined roles. System administrators can create new roles or modify existing roles. Add a Role By default, only system administrators can add new roles. You can also create a new role by copying an existing one. See “Copy a Role” on page 114. To add a role In the left pane, select Roles and Rights. Click New Role. VMware, Inc.
Page 114: Copy A Role
Move the pointer over a role name and click Copy. Type a name. (Optional) Type a description. Expand the check boxes and select and deselect the rights you want to include. See Appendix A, “Roles and Rights,” on page 149 for more information. Click OK. Lab Manager copies the role to the Roles and Rights page. You can now assign it to users and groups. Delete a Role By default, only system administrators can delete a role. You cannot delete the system administrator role or a role that is currently being used. To delete a role In the left pane, select Roles and Rights. Move the pointer over the role name and select Delete. Click OK. Lab Manager deletes the role. Modify Role Properties Only system administrators can change the name, description, or rights of a role. The system administrator cannot be modified. To modify role properties In the left pane, select Roles and Rights. Move the pointer over the role name and select Properties. Change the name, description, or rights and click OK. Lab Manager modifies the role properties. VMware, Inc.
Page 115: Managing Organizations And Workspaces
“Enable or Disable an Organization” on page 118  “Delete an Organization” on page 118  “Using the Primary Workspace” on page 119  “Modify Workspace Properties” on page 120  “Disable a Workspace” on page 121  “Delete a Workspace” on page 121 Modifying Organization Properties By default, system administrators can modify the properties of all organizations. As an administrator with rights at the organizational level, you can edit properties of the organizations of which you are the administrator. Modify Default User Preferences You can set the default use preferences for all users in an organization. To set default user preferences In the left pane, click Organizations. Move the pointer over an organization name and select Properties. Type a default quota for the number of stored virtual machine templates and library configurations. Type a default quota for the number of deployed virtual machine templates. Click OK. VMware, Inc.
Page 116: Modify Default Deployment Settings
To add members or groups to an organization In the left pane, click Organizations. Move the pointer over an organization and select Users and Groups. Click Import Members. In the Look for drop‐down menu, select a search option. Type your search terms and click Search. Select the check box for the users or groups that you want to add. Click Add and OK. Select a role for each user or group and click OK. Lab Manager adds the specified users or groups to an organization. Remove Members or Groups from an Organization By default, only a system administrator and an administrator with rights at the organization level can delete users or groups. To remove members or groups from an organization In the left pane, click Organizations. Move the pointer over an organization and select Users and Groups. Click Remove next to the users or groups that you want to remove from the organization. Click OK. Lab Manager removes the user or group from the organization. VMware, Inc.
Page 117: Add Or Remove The Resource Pools In An Organization
To add or remove datastores in an organization In the left pane, click Organizations. Move the pointer over an organization and select Properties. In the Datastores panel, click Edit. Select a datastore and click an arrow to add it to or remove it from the organization. Click OK and OK. Lab Manager modifies the datastores available to an organization. Add or Remove the Media Stores in an Organization By default, only a system administrator can add or remove media stores. To add or remove media stores in an organization In the left pane, click Organizations. Move the pointer over an organization and select Properties. In the Media Stores panel, click Edit. Select a media store and click an arrow to add it to or remove it from the organization. Click OK and OK. Lab Manager modifies the media stores available to the organization. VMware, Inc.
Page 118: Add Or Remove The Physical Networks In An Organization
Click OK and OK. Lab Manager modifies the host spanning transport networks available to the organization. Enable or Disable an Organization By default, only system administrators can enable or disable organizations. When you disable an organization, all of its users become stranded. See “Managing Stranded Users” on page 111. To enable or disable an organization In the left pane, click Organizations. Move the pointer over an organization name and select Enable or Disable. Click OK. Lab Manager enables or disables the organization. Delete an Organization By default, only system administrators can delete an organization. Before you can delete an organization, you must disable it and reassign the objects owned by any stranded users. See “Managing Stranded Users” on page 111. To delete an organization In the left pane, click Organizations. In the Organization drop‐down menu, select Global. Move the pointer over the organization name and select Disable and click OK. In the left pane, click Users and Groups. VMware, Inc.
Page 119: Using The Primary Workspace
You can delete the primary workspace if you do not want Lab Manager to automatically add users, groups, and resource pools to a workspace in the organization. To delete the primary workspace In the left pane, select an organization. Select Workspace(s). Move the pointer over the primary workspace and select Delete. Click OK. Lab Manager deletes the primary workspace and sets the primary workspace for the organization to None. You can select an existing workspace to be the new primary workspace; otherwise, the next workspace that you create is set as the new primary workspace. Set the Primary Workspace for an Organization In the Organization Properties page, you can select a workspace to be the primary workspace. To set another workspace as the primary workspace In the left pane, select Organizations. Move the pointer over the organization name and select Properties. In the Primary Workspace drop‐down menu, select a workspace. Lab Manager sets this workspace as the primary workspace. When you add users, groups, and resource pools to this organization, they are added to the primary workspace. If you select None, the organization has no primary workspace, so you must add users, groups, and resource pools to each workspace. VMware, Inc.
Page 120: Modify Workspace Properties
In the left pane, select Workspace(s). Move the pointer over a workspace name and select Properties. In the Users and Groups panel, click Edit. Click Add Users and Groups. In the Look for drop‐down menu, select one of the options. Type your search term and click Search. Select the check boxes for the users or groups that you want to add and click Add. Click OK. Select a role for the user. 10 Click OK and OK. Lab Manager adds the specified users or groups to the workspace. Remove Users and Groups from a Workspace By default, system administrators and administrators with rights at the organization and workspace levels can remove users and groups from a workspace. To remove users and groups from a workspace In the left pane, select Workspace(s). Move the pointer over a workspace name and select Properties. In the Users and Groups panel, Click Edit. Click Remove next to the user or group that you want to delete. You cannot remove the system administrator role. Click OK and OK. Lab Manager removes the selected users or groups. VMware, Inc.
Page 121: Add Or Remove The Resource Pools Available To A Workspace
In the left pane, click Workspace(s). Move the pointer over the organization name and select Properties. In the Resource Pools panel, click Edit. Select a resource pool and click an arrow to add or remove it from the workspace. Click OK and OK. Lab Manager modifies the resource pools available to the workspace. Disable a Workspace By default, only system administrators can enable or disable workspaces. When you disable a workspace, all of its users become stranded. See “Managing Stranded Users” on page 111 for more information. To disable a workspace In the left pane, click Workspace(s). Move the pointer over the workspace name and select Disable. Click OK. Lab Manager disables the workspace from the organization. You can now reassign stranded users and objects and delete a workspace. Delete a Workspace By default, only system administrators and administrators with rights at the organization level can delete workspaces. Before you can delete an workspace, you must disable it and reassign the objects owned by any stranded users. To delete a workspace In the left pane, click Workspace(s). Move the pointer over the workspace name and select Disable. Click Delete and OK. Lab Manager deletes the workspace from the organization. VMware, Inc.
Page 122 Lab Manager User’s Guide VMware, Inc.
Page 123: Managing Network Templates
Modify Network Template Properties By default, only system administrators, administrators with rights at the organization level and template creators can edit network template properties. For information on the properties, see “Create a Network Template” on page 29. To modify network template properties In the left pane, select Network Templates. Move the pointer on the network template name and select Properties. Modify the properties and click Update. Lab Manager updates the network template properties. Change Ownership of a Network Template The owner of a network template is the user who created it. If you have sufficient rights, you can change the owner. To change ownership of a network template In the left pane, select Network Templates. Move the pointer over the network template name and select Properties. Click Change Owner. Select an organization and user and click OK. Click Update. Lab Manager reassigns the network template to the new owner. VMware, Inc.
Page 124: Delete Network Templates
To monitor a virtual network’s IP pool In the left pane, select All Configuration(s). Move the pointer over a configuration name and select Open. Click the Networks tab. Move the pointer over a virtual network name and select IP Pool. Add IP Addresses to the IP Pool of a Virtual Network By default, system administrators, administrators with rights at the organization level, and template creators can add IP addresses to a virtual network. Configuration owners and users with the right to edit configurations can also add IP addresses to a virtual network. To add IP addresses to a virtual network Move pointer over a configuration name and select Open. Click Networks tab. Move pointer over a virtual network name and select IP Pool. Click the General tab. Enter an IP address or IP address range in the Static IP Address Pool text box and click Add. Click Update. VMware, Inc.
Page 125: Remove Ip Addresses From The Ip Pool Of A Virtual Network
Chapter 13 Managing Network Templates Remove IP Addresses from the IP Pool of a Virtual Network Only system administrators, administrators with rights at the organization level and template creators can remove IP addresses from a virtual network. To remove IP addresses from a virtual network Move pointer over a configuration name and select Open. Click the Networks tab. Move the pointer over a virtual network name and select IP Pool. Click the General tab. Enter an IP address or IP address range in the Static IP Address Pool text box, or select an existing IP address or IP address range, and click Remove. Click Update. VMware, Inc.
Page 126 Lab Manager User’s Guide VMware, Inc.
Page 127: Managing Virtual Machine Templates
“Consolidate a Virtual Machine Template” on page 129  “Discard the State for a Virtual Machine Template” on page 129  “Modify Virtual Machine Template Properties” on page 129  “Modifying Virtual Machine Template Hard Disks” on page 131  “Modifying Virtual Machine Template Network Interfaces” on page 132  “Upgrade Virtual Hardware” on page 134  “Change Ownership of a Virtual Machine Template” on page 134  “Delete a Virtual Machine Template” on page 134 Unpublish a Virtual Machine Template Unpublish a virtual machine template to make it unavailable for configuration use. To unpublish a virtual machine template In the left pane, click VM Templates. Move the pointer over the published template name and select Unpublish. Click OK. VMware, Inc.
Page 128: Export A Virtual Machine Template To An Smb Share
To export a virtual machine template In the left pane, click VM Templates. Move the pointer over the template name and select Export. Provide the location and user credentials:  Type the UNC path of the SMB share (relative to the Lab Manager server system) where you want to store the files. Use English characters for the UNC path, for example, A sample path is \\10.6.1.246\VMwareLM\ExportTemplates.  If the UNC folder requires authentication, type the user name and password to access the files. Click OK. Export a Virtual Machine Template to vCenter By default, system administrators, administrators with rights at the organization and workspace levels, and template creators can export virtual machine templates to vCenter. To export a virtual machine template to vCenter In the left pane, click VM Templates. Move the pointer over a template name and select Export. Select vCenter. Type a display name for the exported template. Select a datastore. Select a network. Click OK. Lab Manager exports the template to vCenter. VMware, Inc.
Page 129: Consolidate A Virtual Machine Template
To discard state for a virtual machine template In the left pane, click VM Templates. Move the pointer over the undeployed template name and select Discard State. Click OK. Lab Manager discards the template’s state. Modify Virtual Machine Template Properties By default, only system administrators, administrators with rights at the organization level and template creators can modify the properties of a template. Before you modify the properties of a template, undeploy the template. If it is deployed, the number of properties you can modify is limited. See “Modifying Virtual Machine Template Hard Disks” on page 131 and “Modifying Virtual Machine Template Network Interfaces” on page 132 for information about modifying virtual machine template hard disks and network interfaces. See “Change Ownership of a Virtual Machine Template” on page 134 For information about changing the owner of a template. To modify virtual machine template properties In the left pane, click VM Templates. Move the pointer over the template name and select Properties. Modify the name. VMware, Inc.
Page 130 For example, you might have a virtual machine template with a 32‐bit guest operating system that does not have the requires software (kernel or drivers) to run on a 64‐bit processor. Another example involves a mixed (32‐bit and 64‐bit) ESX/ESXi host environment where you need to complete a testing process specifically on a 32‐bit guest operating system, and the operating system accommodates both 32‐bit and 64‐bit CPU architecture. See the VMware Infrastructure documentation for details on priorities, shares, reservations, and limits. Select the number of virtual CPUs. The maximum number of processors is four. The datastore must be connected to a host that provides the required SMP technology for the guest operating system. If you choose a CPU number not currently compatible with the CPU of the host, you cannot deploy the virtual machine template until you attach a host with the appropriate SMP support. If you have some but not all hosts that provide the required SMP technology, Lab Manager limits the number of hosts on which the virtual machine template can be deployed. 10 Modify the CPU reservation. 11 Select a CPU priority. 12 Select a CPU limit. If you select Maximum, type a value. 13 Modify the memory value. 14 Modify the memory reservation value. 15 Select a memory priority. 16 Select a memory limit. If you select Maximum, type a value. 17 Select or deselect the Use Time Synchronization check box. Enables time synchronization between the guest (virtual machine template) and ESX/ESXi host operating systems. 18 Check whether the Perform Customization is selected. It specifies whether guest customization is enabled. VMware, Inc.
Page 131: Modifying Virtual Machine Template Hard Disks
To add a virtual hard disk to a template In the left pane, click VM Templates. Move the pointer over the virtual machine template name and select Properties. In the Hard Disks section, click Add Hard Disk. Type the disk size (GB). Select the bus type. Select a bus number. Select a bus ID. Click OK and Update. You can deploy the virtual machine template and use the guest operating system tools to partition and format the new disk for use. If you add a SCSI hard disk to a virtual machine template, the guest OS might generate an error message about missing drivers the next time you power on the template. If this error occurs, download and install the appropriate driver, and contact VMware for further support. Edit a Virtual Machine Template Hard Disk You can update the bus number and bus ID of a virtual machine hard disk. To edit a virtual machine template hard disk In the left pane, click VM Templates. Move the pointer over the virtual machine template name and select Properties. In the Hard Disks section, click Edit next to one of the listed disks. Modify the bus number and bus ID and click OK. Click Update. VMware, Inc.
Page 132: Delete A Virtual Machine Template Hard Disk
Add a Network Interface to a Virtual Machine Template You can add one or more virtual NICs to an undeployed virtual machine template. Depending on your virtual machine version, a template can have up to four NICs. To add a network interface In the left pane, click VM Templates. Move the pointer over the template name and select Properties. In the Network Interfaces panel, click Add Interface. Lab Manager adds and connects a new virtual NIC. Edit the virtual NIC settings, if necessary. Deselect the Connected check box to disconnect the virtual NIC. Choose a network from the Network drop‐down menu. The available options are based on the network templates that you own or share and the physical networks available to your organization. Specify a primary NIC. The primary NIC setting determines the default, and only gateway, for the virtual machines based on the template. These virtual machines can use any NIC to connect to other machines that are directly connected to the same network as the NIC, but it can only use the primary NIC to connect to machines on networks that require a gateway connection. Consider this behavior when selecting a primary NIC, especially if you plan to deploy configurations that use fencing or connect virtual networks to physical networks. Select an IP addressing mode for the network. The available options are based on the IP addressing modes available to the selected network. If you selected Static ‐ Manual as the IP addressing mode, type an IP address in the IP Address text box. Click Update. Lab Manager generates a MAC address for the network interface. VMware, Inc.
Page 133: Edit A Virtual Machine Network Interface
Delete a Network Interface from a Virtual Machine Template You can delete virtual NICs from an undeployed template. To delete a network interface In the left pane, click VM Templates. Move the pointer over the template name and select Properties. In the Network Interfaces panel, click Delete. Click Update. Lab Manager deletes the network interface. Reset a Virtual Machine Template Network Interface MAC Address You can reset a network interface MAC address for an undeployed template. Reasons to reset include having a MAC address conflict or discarding the saved state quickly and easily. To reset the MAC address for a network interface In the left pane, click VM Templates. Move the pointer over the template name and select Properties. In the Network Interfaces panel, select Reset from the MAC Address drop‐down menu. Click Update. VMware, Inc.
Page 134: Upgrade Virtual Hardware
Delete a Virtual Machine Template To delete a template, it must be undeployed and unpublished. If you are unable to unpublish a template, you can force delete it. See “Delete a Virtual Machine Template with Force” on page 134. To delete a virtual machine template In the left pane, click VM Templates. Move the pointer over the virtual machine template name and select Delete. Click OK. Delete a Virtual Machine Template with Force If an ESX/ESXi host failure or some other event prevents you from unpublishing and deleting a template, Lab Manager system administrators can still forcefully delete a published template. The Force Delete command removes the template from the Lab Manager database but not from the vCenter inventory. You can manually remove the virtual machine from the vCenter inventory. To delete a published virtual machine template In the left pane, click VM Templates. Move the pointer over the published template name and select Force Delete. Click OK. VMware, Inc.
Page 135: Managing Lab Manager Settings
“Configuring Guest Customization Settings” on page 142  “Configuring SupportLink Settings” on page 142  “Configuring Resource Cleanup Settings” on page 143  “Configuring vCenter Settings” on page 144 Configuring General Preferences You can configure preferences for settings related to Lab Manager, email, system alerts, and recording change summaries. Change vCenter Lab Manager Preferences The Lab Manager preferences include settings that you entered during installation as well as prepopulated default values. If needed, you can change the settings. To change Lab Manager preferences In the left pane, click Settings. Click the General tab. Modify the Lab Manager preferences and click OK. You can modify any of the preferences described in Table 15‐1, “vCenter Lab Manager Preferences,” on page 136. VMware, Inc.
Page 136 For example, importing a virtual machine template from an SMB share. Import from vCenter Time to wait before a vCenter import fails. The default is 120 minutes. Timeout When Lab Manager imports a virtual machine from vCenter, vCenter clones the virtual machine. The timeout value applies to this cloning task. Datastore Garbage Frequency of garbage collection on datastores. The default is 120 seconds. Collection Frequency Garbage collection is the automatic detection and freeing of images that are no longer in use. Lab Manager does not immediately delete files associated with a deleted virtual machine. Lab Manager stores virtual machine files in a tree of related linked clones. Each pass of the garbage collector involves an attempt to delete nodes that no longer have dependencies. Several passes over time might be required to free up the space associated with a deleted virtual machine. Activity Log History to Keep Days of log history to keep before deleting it. The default is 90 days. Type 0 to never delete logs. Activity Log History Shown Days of log history to display in the Web console. The default is 30 days. Type 0 to show all activity. Display Background Image Choose whether to display the background image. on Login Screen If you have a slow or remote connection to Lab Manager, you can turn off the background image to speed up loading time. Provide Default Choose whether you want Lab Manager to generate default names for configurations Configuration and Machine and virtual machines. Names VMware, Inc.
Page 137: Set Email Preferences
Type the destination email address to test SMTP settings. Click Test SMTP Settings to verify that the server connection works. Click OK. Set System Alert Preferences Lab Manager can send system alert emails to all Lab Manager system administrators or to a specified list of email addresses. Lab Manager sends system alert emails to the specified recipients under these conditions:  Status of a host or datastore changes.  Disk threshold (yellow or red) of a host or datastore is crossed.  Lab Manager loses or resumes the connection to the vCenter Server.  Lab Manager detects that an ESX/ESXi host is not responding or starts responding. To set system alert, preferences In the left pane, click Settings. Click the General tab. Select the recipients of system alert emails:  All vCenter Lab Manager Administrators – Select this option to send system alerts to all system administrators.  These Email Addresses – Select this option to send system alerts to a specified list of email addresses. Click OK. VMware, Inc.
Page 138: Set Configuration Change Summary Preferences
To provide Lab Manager access to LDAP users, you must specify the LDAP settings and then add LDAP users or groups to a Lab Manager organization (see “Create an Organization” on page 27). When an LDAP user who has been added to an organization logs into Lab Manager, Lab Manager checks the credentials of the user against the LDAP directory. If the credentials are accepted, Lab Manager creates a new user account and logs the user into the system. Lab Manager cannot modify the information in your LDAP directory. You can add, delete, or modify LDAP users or groups only in the LDAP directory itself. Lab Manager regularly synchronizes user and group information with the LDAP directory. Locate an LDAP Server Before typing a host name and port information for your LDAP server, you can have Lab Manager try to locate an available LDAP server. To locate an LDAP server In the left pane, click Settings. Click the LDAP tab. Click Locate LDAP Server. Lab Manager looks for LDAP servers registered with the DNS server for the local computer. If Lab Manager finds an LDAP server, it populates the Server and Port text boxes. If Lab Manager finds multiple LDAP servers, it chooses one based on the DNS LDAP priority and weight. VMware, Inc.
Page 139: Set Up An Ldap Connection
Manager server is in the same domain as the Active Directory domain controller. Type a port number or leave blank to use the default ports. If the LDAP server is listening on a nondefault port, type the port number. For LDAP, the default port is 389; for LDAPS, the default port is 636. Type the base distinguished name (DN). The base DN is the location in the LDAP directory where Lab Manager connects. Lab Manager can detect the base DN if your LDAP server supports this. Leave this text box blank and click Test LDAP Settings to determine if your server supports base DN detection. VMware recommends connecting at the root. You need to type the domain components only, for example, DC=vmware,DC=com. To connect to a node in the tree, type the distinguished name for that node, for example, OU=LabManager,DC=vmware,DC=com. Connecting at a node limits the scope of the directory available to Lab Manager. If you specify an OU, only LDAP users in that OU can log in to Lab Manager. In some cases, AUTION this restriction can block access to users that you do not want to block. For example, consider the following scenario:  Domain Name: mydomain.com  Top Level OUs: DublinOffice and HeadOffice  Groups: LabMan group that includes users from both the DublinOffice and HeadOffice OUs. If your binding string is OU=HeadOffice,DC=mydomain,DC=com, and you add the LabMan group to a Lab Manager organization, only members of the LabMan group who are also members of the HeadOffice OU can log in to Lab Manager and access the organization. Members of the LabMan group from the DublinOffice OU are excluded. Select the Use LDAPS check box if you have an LDAP server set up to support LDAPS. LDAPS makes LDAP traffic confidential and secure by using LDAP over Secure Sockets Layer (SSL). VMware, Inc.
Page 140: Specify The Ldap Connector And Schema
10 Specify how often Lab Manager synchronizes with the LDAP server. Synchronizing updates Lab Manager user and group information based on changes to the LDAP directory. To synchronize immediately, click the Synchronize LDAP button. Specify the LDAP Connector and Schema Lab Manager supports Microsoft Active Directory and OpenLDAP, as well as the most common schemas associated with each. To specify the LDAP connector and schema In the left pane, click Settings. Click the LDAP tab. Select a connector. Lab Manager supports Active Directory and OpenLDAP. Certain options are enabled or disabled based on your selection. For example, only Active Directory supports serverless binding. Select an LDAP schema. The LDAP schema defines the required and optional attributes for an LDAP directory entry. If you select Active Directory as the connector, select Active Directory, unless you are using a custom schema. If you select OpenLDAP as the connector, select OpenLDAP(1), OpenLDAP(2), or OpenLDAP(3), unless you are using a custom schema. OpenLDAP(1), (2), and (3) represent the most common implementations of OpenLDAP. OpenLDAP(1) should work in most environments that are not significantly customized. Check with your OpenLDAP administrator to determine which schema to choose or if you need a custom schema. The combination of connector and schema populates the text boxes in LDAP User Attributes and LDAP Group Attributes. VMware, Inc.
Page 141: Customize Ldap User And Group Attributes
Lab Manager tries to connect to the LDAP server and look up information about the user in the User Name text box. For anonymous read, you must provide a valid user name to test. Review the test results and modify your connection information or attribute values, if necessary. Detach an LDAP Server To stop using LDAP to authenticate Lab Manager users, you can detach the LDAP server. To detach an LDAP server In the left pane, click Settings. Click the LDAP tab. Click Detach LDAP Server. Lab Manager detaches the LDAP server and LDAP users are prevented from logging in to the Web console. Synchronize Lab Manager with the LDAP Server Lab Manager regularly synchronizes its user and group information with the LDAP server. You can manually synchronize with the LDAP server at any time. To synchronize with an LDAP server In the left pane, click Settings. Click the LDAP tab. Click Synchronize LDAP. VMware, Inc.
Page 142: Configuring Lab Manager Licenses
Type the serial number and click OK. Configuring Guest Customization Settings For virtual machines created from templates, Lab Manager can customize the network settings of the guest operating system. Guest customization requires VMware Tools.  For information about building a Microsoft Sysprep package, see “Build a Microsoft Sysprep Package” on page 41.  For information about choosing the default SID generation mechanism, see “Select the SID Generation Tool for Lab Manager” on page 43.  For information about virtual machine template publishing, see “Disable VMware Tools Check Before Publishing Virtual Machine Templates” on page 47. Configuring SupportLink Settings Lab Manager SupportLink provides the performance statistics displayed on the Overview page and sends usage data to VMware that helps improve the product. VMware does not share this data with other organizations or trace any data back to individual users. SupportLink also allows you to collect support information to troubleshoot issues with VMware Support. Enable SupportLink During the Lab Manager installation and initialization process, you can decide whether to enable SupportLink. If you did not enable SupportLink at that time you can enable it later. To enable SupportLink In the left pane of the console, click Settings. Click the SupportLink tab.
Page 143: Collect Support Information
Chapter 15 Managing Lab Manager Settings Type your company name and Lab Manager administrator email address. Do not alter the SupportLink server unless instructed to change the name by VMware support. If the Lab Manager server uses a proxy server to connect to the Internet, enter the proxy server information. If VMware support requests a test of SupportLink, click Test Settings to verify the connection to the Lab Manager SupportLink Server. Click OK. Collect Support Information If VMware Support requests that you collect information about your Lab Manager environment for troubleshooting, you can collect support information from the SupportLink tab. To collect support information On the SupportLink tab, click Collect. After Lab Manager collects support information, click the link to download a .zip file that contains the support logs. Configuring Resource Cleanup Settings You define the maximum deployment lease and storage lease times for virtual machine templates and configurations. The values you type are also used as the default settings for new virtual machine templates and configurations. You can override these defaults (up to the maximum) when you create or edit individual virtual machine templates and configurations. If a Lab Manager system administrator changes the maximum value after the initial setting, a user can only extend an existing lease to the original value.
Page 144: Set Deployment And Storage Lease Maximums
To reconnect Lab Manager to vCenter Server In the left pane, click Settings. Click the vCenter tab. Click OK. Lab Manager attempts to re‐establish a connection with the vCenter Server. Change the vCenter Server User Name and Password If the user name and password for your vCenter Server changes or if the account you are currently using does not have the necessary vCenter privileges, you can change the log in information. For more information about the required vCenter privileges, see the VMware vCenter Lab Manager Installation and Upgrade Guide. To change the vCenter Server log in information In the left pane, click Settings. Click the vCenter tab. Type a new user name and password for the vCenter Server connection. Click OK. Lab Manager attempts to establish a connection with the vCenter Server using the new credentials. VMware, Inc.
Page 145: Monitoring Lab Manager
Monitoring Lab Manager Operations Information about all recent Lab Manager operations appears in the Activity Log. In addition, you can view detailed information about each job in the log. View the Activity Log View the Activity Log to monitor operations that are in progress, to find and troubleshoot failed jobs, and to view jobs by owner or organization. Lab Manager system administrators can see all entries. Other users can see entries about their own operations. To specify how long to retain Activity Log entries and how many days worth of history to display, see “Change vCenter Lab Manager Preferences” on page 135. To view the Activity Log In the left pane, click Activity Log. The log lists activities for the currently selected organization. If you select Global, the log lists activities for the entire Lab Manager installation. On this page, a table includes this information:  The Status column indicates the success, failure, or in progress status of a job. A failed job includes a short description in the Details column.  The Activity column includes a brief description of the operation. Click the activity description to view details about the job.  The Owner and Location columns provide information about who initiated a job and from which organization and workspace they initiated it. VMware, Inc.
Page 146: View Activity Details
You can view information about the CPU and memory resources used by each resource pool across the entire installation or within an organization. To view resource pool usage information In the left pane, click Resource Usage and click the Resource Pools tab. Select the organization for which you want to view resource pool usage information from the Organization drop‐down menu. Select Global to view usage information across the entire installation. Lab Manager displays resource usage information for all the resource pools in the selected organization or across the entire installation. If you select an organization, Lab Manager displays only the resources being used by that organization. View Workspace Resource Usage You can view information about the CPU and memory resources used by each workspace across the entire installation or within a specific organization. To view workspace resource usage information In the left pane, click Resource Usage and click the Organizations and Workspaces tab. Select the organization for which you want to view workspace resource usage information from the Organization drop‐down menu. Select Global to view usage information for all workspaces in all organizations. Lab Manager displays resource usage information for all the workspaces in the selected organization or across the entire installation. If you select an organization, Lab Manager displays only the resources being used by workspaces in that organization. VMware, Inc.
Page 147: View Deployed Virtual Machines
The page displays a list of deployed machines for the currently selected organization. If you select Global, the page lists deployed machines for the entire Lab Manager installation. On this page, a table includes this information:  Console – Provides access to the virtual machine console through the thumbnail icon.  Virtual Machine – Provides a pop‐up menu to view the virtual machine console or undeploy the virtual machine.  Status – Indicates that the virtual machine is deployed. If there is an error associated with a virtual machine, it appears as a link. Click the link to view job details.  Configuration – Specifies whether the virtual machine is a virtual machine template (indicated by a dash) or part of a configuration.  NIC – Displays a number for each NIC associated with the virtual machine.  IP Address – Displays the IP address of the virtual machine or specifies DHCP.  External IP – Displays the external IP address for the virtual machine if it requires one.  Template – Shows the virtual machine template that serves as the basis of the virtual machine. This is useful when you plan on retiring a virtual machine template and need to evaluate its usage. When a virtual machine template is removed from a configuration or is deployed, a dash appears in the Template column.  Host – Displays the ESX/ESXi host name.  Deployed By – Indicates the user who deployed the virtual machine.  Location – Shows the organization and workspace from which the virtual machine was deployed.  Sharing – Indicates whether the configuration is accessible for others to use.  Date Deployed – Displays the date and time of deployment.  Messages – Messages about the virtual machine. VMware, Inc.
Page 148 Lab Manager User’s Guide VMware, Inc.
Page 149: Roles And Rights
 System Administrator  Administrator The system administrator can assign the administrator role rights at the organization or workspace level.  Template Creator  Application Owner  User  View Only Datastore Rights By default, only system administrators can create, delete, and edit datastores. The create right is required to add a datastore to an organization. Other users can access datastores that are added to their organization as resources. Table A-1. Datastore Rights for Predefined Roles Delete Edit Properties System Administrator Administrator Template Creator Application Owner User View Only VMware, Inc.
Page 150: General Rights
View Only High I/O Rights Lab Manager restricts certain high I/O operations based on user roles. Table A-4. High I/O Rights for Predefined Roles Consolidate Export Full Clone Import from SMB Import from vCenter System Administrator Administrator Template Creator Application Owner User View Only When an owner shares an object with another user, the user’s ability to perform high I/O operations on that object is based on the intersection of the rights of their role and the access rights assigned by the owner sharing the object. VMware, Inc.
Page 151: Host Rights
Application Owner User View Only Library Configuration Rights This table lists the rights that the predefined roles have for library configurations in Lab Manager. Table A-8. Library Configuration Rights for Predefined Roles Clone to Discard Edit Workspace Create Delete State Properties LiveLink View System Administrator Administrator Template Creator Application Owner User View Only VMware, Inc.
Page 152: Machine Rights
App. Owner User View Only The Edit Properties column refers to all virtual machine properties, except those called out in their own column. For example, a user can edit a virtual machine name but not its memory or network information. When an owner shares a configuration or virtual machine template with another user, the user gets rights to the virtual machine template or configuration’s virtual machines. Those rights are determined based on the intersection of the rights of their role and the access rights assigned by the owner sharing the object. Table A-11. Machine Rights for Sharing Roles Edit Boot Seq. Edit Edit Edit Access and Delay Edit CPU Edit Hard Disk Memory Network Properties Full Control Change Read VMware, Inc.
Page 153: Media Rights
System Administrator Administrator Template Creator Application Owner User View Only Network Template Rights By default, system administrators, administrators with rights at the organization level, and templates creators can create, delete, and edit network templates. Table A-15. Network Template Rights for Predefined Roles Create Delete Edit Properties View System Administrator Administrator Template Creator Application Owner User View Only VMware, Inc.
Page 154: Organization Rights
Edit Properties System Administrator Administrator Template Creator Application Owner User View Only Resource Pool Rights By default, only system administrators can create, delete, and edit resource pools. Other users can access resource pools that are added to their organization as resources. Table A-19. Resource Pool Rights for Predefined Roles Attach Detach Edit Properties System Administrator Administrator Template Creator Application Owner User View Only VMware, Inc.
Page 155: Role Rights
View Only Sharing Rights for Predefined Roles (cont’d) Share Across Workspaces Share with Share with Users (Read Share with Organizations Share with Workspace Only) Organizations Users Workpsace Users System Administrator Administrator Template Creator Application Owner User View Only VMware, Inc.
Page 156: User Rights
Table A-24. Virtual Machine Template Rights for Predefined Roles Create Delete Deploy/Undeploy Edit Properties View System Administrator Administrator Template Creator Application Owner User View Only When an owner shares a virtual machine template with another user, the user’s rights are based on the intersection of the rights of the role and the access rights assigned by the owner sharing the object. Table A-25. Virtual Machine Template Rights for Sharing Roles Access Create Delete Deploy/Undeploy Edit Properties Full Control Change Read VMware, Inc.
Page 157: Workspace Configuration Rights
Full Control Change Read Workspace Rights This table lists the rights that the predefined roles have for workspaces in Lab Manager. Table A-28. Workspace Rights for Predefined Roles Clone Edit Edit Edit Create Delete Membership Prop. Resource Move From Move To View System Admin. Admin. Templ. Creator App. Owner User View Only VMware, Inc.
Page 158 Lab Manager User’s Guide VMware, Inc.
Page 159: Client And Browser Support
Red Hat Enterprise Linux 2.1 AS/ES/WS 3 AS/ES/WS 4 AS/ES/WS 5 AS/ES/WS SUSE Linux Enterprise Server 8 (SLES) Enterprise Server 9 (SLES) Enterprise Server 10 (SLES) Table B-2. 64-Bit Client Operating System and Web Browser Support Operating System IE 6.x IE 7.x IE 8.x Firefox 2.x Firefox 3.x Microsoft Windows Server 2008 Vista Server 2003 Standard Edition VMware, Inc.
Page 160 Lab Manager User’s Guide Table B-2. 64-Bit Client Operating System and Web Browser Support (Continued) Operating System IE 6.x IE 7.x IE 8.x Firefox 2.x Firefox 3.x Server 2003 Enterprise Edition XP Professional Red Hat Enterprise Linux 3 AS/ES/WS 4 AS/ES/WS SUSE Linux Enterprise Server 9 (SLES) Enterprise Server 10 (SLES) VMware, Inc.
Page 161: Guest Operating System Support
Edition Microsoft Windows Server 2003, Standard Versions 4 and 7 Edition Microsoft Windows Server 2003, Web Edition Versions 4 and 7 Microsoft Windows Small Business Server 2003 Versions 4 and 7 Microsoft Windows XP Professional Versions 4 and 7 Microsoft Windows 2000 Advanced Server Versions 4 and 7 Microsoft Windows 2000 Professional Versions 4 and 7 Microsoft Windows 2000 Server Versions 4 and 7 Microsoft Windows NT Version 4 and 7 Yes, SIDgen only Microsoft Windows 98 Version 7 only Microsoft Windows 95 Version 7 only UNIX/Linux Debian GNU/Linux 5 (experimental) Version 7 only Debian GNU/Linux 4 Version 7 only FreeBSD Version 7 only Other Linux Versions 4 and 7 Red Hat Enterprise Linux 5 Versions 4 and 7 Red Hat Enterprise Linux 4 Versions 4 and 7 Red Hat Enterprise Linux 3 Versions 4 and 7 VMware, Inc.
Page 162 Yes, Sysprep only Edition Microsoft Windows Server 2003, Enterprise Versions 4 and 7 Yes, Sysprep only Edition Microsoft Windows Server 2003, Standard Versions 4 and 7 Yes, Sysprep only Edition Microsoft Windows XP Professional Versions 4 and 7 Yes, Sysprep only UNIX/Linux Debian GNU/Linux 5 (experimental) Version 7 only Debian GNU/Linux 4 Version 7 only Other Linux Versions 4 and 7 Red Hat Enterprise Linux 5 Versions 4 and 7 Red Hat Enterprise Linux 4 Versions 4 and 7 Red Hat Enterprise Linux 3 Versions 4 and 7 SUSE Linux Enterprise Server 10 Versions 4 and 7 SUSE Linux Enterprise Server 9 Versions 4 and 7 Ubuntu Linux Versions 4 and 7 Solaris Sun Solaris 10 Versions 4 and 7 Other Other Versions 4 and 7 VMware, Inc.
Page 163: Using Ssmove
Using SSMove SSMove is a utility on the Lab Manager server that allows you to move datastores. This utility is located in C:\Program Files\VMware\VMware Lab Manager Server\Tools\SSMove. This appendix includes information about preparing to use SSMove, moving a datastore, and fixing common errors that might occur. Before You Move a Datastore To move a datastore, you must power off virtual machines and shut down ESX hosts and the Lab Manager server. To prepare to move a datastore Back up the Lab Manager database and data on the storage servers. See the VMware knowledge base article at http://kb.vmware.com/kb/1000023 for more information. In the left pane, click Resources. On the Datastores tab, click the % Used column heading. You can review datastore usage and identify datastores that are at or near capacity. In the left pane, click Users and Groups. Click Send Notification, which prompts all users to log out of Lab Manager. Undeploy the virtual machines on the datastores that you are moving. On the Datastores tab, move the pointer over the datastore name and select Open. In Status, move the pointer over each deployed virtual machine name and select Undeploy ‐ Save State or Undeploy ‐ Discard State. On the Datastores tab, move the pointer over the datastore name and select Disable. Click OK.
Page 164: Move A Datastore
Lab Manager User’s Guide Move a Datastore Only system administrators can move a datastore. To move a datastore On the Lab Manager server, run SSMove.exe, which is located in C:\Program Files\VMware\Vmware Lab Manager\Tools\SSMove. You can only run a single instance of SSMove at a time. Click Refresh Sizes to update the used and available space information for the datastores. Filter the source trees based on their datastore or size. Select the datastore that contains the data you want to move. Type a minimum tree size (GB). Click Apply. Choose a source tree to move. On the View Datastore Usage page, move the pointer over the virtual machine and select Context. Move the pointer over the root of the tree to display the directory path. The directory ID of the root node is the source tree that you want to move. Select the destination datastore. The drop‐down menu lists the datastores that are connected to the same ESX hosts as the source datastore and the amount of free space (GB) on the datastore. Select Move. SSMove moves the data from the source to the destination and reports its progress in the Status area. Click Exit when the move is complete. In the Lab Manager Web console, enable the datastore. 10 Notify users that they can log in to Lab Manager. Resolving Move Errors If errors occur during the move, this section describes how to fix them.
Page 165: Glossary
Glossary Active Directory A Microsoft directory service that stores information about the network operating system and provides services. Active Directory enables administrators to set security policies, control resources, and deploy programs across an enterprise. You can point Lab Manager at a Microsoft Active Directory domain or domain controller to enable an entire company (or subset) of users. ActiveX Control An object that supports programmatic interfaces. Lab Manager prompts you to install the remote console ActiveX Control when you initially access a virtual machine console. activity log A display of status information about asynchronous Lab Manager tasks or jobs that do not require immediate completion. administrator See Lab Manager system administrator. agent See Lab Manager agent. base disk The original virtual hard disk from which a virtual machine is derived. Virtual machines created by linked clones in Lab Manager consist of a base disk and chain of delta disks that store the changes made to the original. This process addresses the potential disk consumption difficulties that can occur with virtual machine proliferation. When you make a linked clone of a virtual machine, both the clone and the original use the same base disk. When you make a full clone of a virtual machine, Lab Manager consolidates the original base disk and its delta disks to create a new base disk. In this case, the original disks remain unchanged. See also chain length, clone, delta disk. chain length The number of delta disks associated with a virtual machine. The chain length indicates how distributed a virtual machine image is across the directories of a datastore. See also base disk, consolidate, delta disk. clone See linked clone, full clone. VMware, Inc.
Page 166 A group of virtual machines that Lab Manager controls as a unit. Lab Manager can replicate these configurations on demand. console See Lab Manager Web console, virtual machine console. consolidate To combine an existing base disk and its chain of delta disks into a single base disk. Use consolidation to move a virtual machine or configuration to a new datastore. See also base disk, chain length, delta disk. datastore Virtual representation of combinations of underlying physical storage resources in the datacenter. A datastore is the storage location (for example, a physical disk, a RAID, or a SAN) for virtual machine files. Lab Manager stores media files and virtual machines on VMFS and NFS datastores. delta disk “Differencing” disk created during the cloning process. A virtual machine created as a linked clone consists of a base disk, plus a chain of one or more delta disks that store the differences between the cloned virtual machine and the original virtual machine. See also base disk, chain length, clone. deploy To register a virtual machine or configuration on an ESX host. This host must have the proper CPU type, CPU numbers, and 64‐bit capability, if necessary. Lab Manager manages the selection of hosts when deploying virtual machines and configurations. deployment lease The amount of time a virtual machine template or configuration is deployed before Lab Manager is scheduled to undeploy it. DHCP (Dynamic Host Configuration Protocol) A communications protocol that enables dynamic addressing. The software relieves administrators of the task of assigning an IP address to each device that connects to a network. DNS (Domain Name System) An Internet data query service that translates host names into IP addresses. Also called Domain Name Server or Domain Name Service. DRS (VMware Distributed Resource Scheduler) See VMware Distributed Resource Scheduler (DRS). ESX See VMware ESX. export To move a configuration or virtual machine to an SMB share. VMware, Inc.
Page 167 To forcefully delete a virtual machine when an ESX host failure prevents the Lab Manager administrator from deleting the virtual machine. The operation cleans the virtual machine from the Lab Manager database but not from the VirtualCenter inventory. You can manually remove the virtual machine from the VirtualCenter inventory. force undeploy To forcefully undeploy a virtual machine after situations such as an ESX host goes permanently offline or someone manually removes a virtual machine from VirtualCenter inventory. FQDN (fully qualified domain name) The name of a host that includes the host name and the domain name. For example, the FQDN of a host named esx1 in the domain vmware.com is esx1.vmware.com. full clone (n.) Full copy of the consolidated sum of delta disks and base disk of a virtual machine. Full cloning takes a significantly longer time than linked cloning. (v.) To make a full copy of the consolidated sum of delta disks and base disk of a virtual machine. See also linked clone, base disk. guest customization Lab Manager customization of the network settings inside the guest operating system of a virtual machine. These settings include the machine name, IP settings, and Security Identifier (SID) for Windows guest operating systems. Lab Manager creates a package with the guest customization tools. When you power on a virtual machine for the first time, Lab Manager copies the package, runs the tools, and deletes the package from the virtual machine. Without guest customization, the virtual machine uses the settings of the virtual machine template it is based on. This situation can create machine name and network conflicts when you deploy more than one virtual machine created from the same virtual machine template at the same time. guest operating system An operating system that runs inside a virtual machine. host The physical computer on which the virtual machines managed by Lab Manager reside. import To copy a configuration from an SMB share, or to copy a virtual machine from an SMB share or VirtualCenter. internal IP address A preconfigured IP address for a virtual machine in a configuration. Internal IP addresses remain static across cloning activity. VMware, Inc.
Page 168 Lab Manager User’s Guide IP pool A range of IP addresses set aside for use by physical and virtual networks in Lab Manager. An exact representation of a CD or DVD, including its content and logical format. Lab Manager system administrator In most organizations, the highest level administrator who is likely to map to the VMware Infrastructure system administrator role. The responsibilities of the Lab Manager system administrator span the entire Lab Manager installation. Only Lab Manager system administrators can attach resources. Lab Manager agent Software installed on the ESX host that facilitates a connection to the Lab Manager Server system. Lab Manager installs the agent during the process of preparing a host. Lab Manager Server Component of the Lab Manager environment installed with the Lab Manager Server software. Lab Manager Web console A browser‐based interface that provides access to all Lab Manager operations. LDAP (Lightweight Directory Access Protocol) A protocol that enables you to locate organizations, individuals, or other resources from a server. lease See deployment lease, storage lease. linked clone (n.) A duplicate of a virtual machine that uses the same base disk as the original, with a chain of delta disks, to keep track of the differences between the original and the clone. (v.) To generate a “quick” copy by creating a delta disk instead of copying an entire virtual hard disk. This operation addresses virtual machine proliferation by using “referential provisioning,” a process that involves storing new changes but referring back to a chain of delta disks. For each clone, Lab Manager freezes the original delta disk and creates a new one. See also full clone, base disk, chain length. MAC (Media Access Control) address A hardware address that identifies each virtual or physical network adapter. media store A directory for media files on a datastore.
Page 169 Authorization to perform a specific action or set of actions on a managed object or group of managed objects. publish To make a Lab Manager virtual machine template available for use in creating configurations. ready Indicates an ESX host is available for use. Certain host states are documented that affect this status. referential provisioning A process for linked clones that involves storing new changes but referring back to a chain of delta disks. For each clone, Lab Manager freezes the original delta disk and creates a new one. A linked clone operation generates a “quick” copy by creating a delta disk instead of copying an entire virtual hard disk. reset To restart a virtual machine and clear the machine state. This operation can occur at the virtual machine or configuration level. resource pool A division of computing resources used to manage allocations between virtual machines. resume To return a virtual machine or configuration to operation from its suspended state. When you resume a suspended virtual machine or configuration, all applications are in the same state they were when the virtual machine or configuration was suspended. See also Suspend. revert To return the virtual machine to an earlier state captured in a snapshot. revert point The state of a virtual machine as captured by a snapshot at a specific point in time. You can restore the status of an active virtual machine to its revert point. SAN (storage area network) A large‐capacity network storage device that can be shared among multiple VMware ESX hosts. Shared storage (for example, SAN or NAS) is required for VMotion. Security Identifier (SID) A unique name in a Microsoft Windows environment used to identify an object. See Microsoft Windows documentation. See Security Identifier (SID). SIDgen A tool packaged with Lab Manager that changes the SID for virtual machines. VMware, Inc.
Page 170 The technology that enables you to assign two virtual processors to a virtual machine on any host machine that has at least two logical processors. SMTP (Simple Mail Transfer Protocol) A protocol that facilitates email transmissions between servers. SMTP Server A system running email server software that accepts email from within your enterprise. Lab Manager must connect to an SMTP server to send email alerts. snapshot A reproduction of the virtual machine or configuration as it was when you took the snapshot, including the state of the data on all the virtual disks and power state (on, off, or suspended). Lab Manager stores the snapshot with the configuration or virtual machine image. Only one snapshot is active at a time. The most recent snapshot replaces the previous one. You can revert the configuration or virtual machine to a snapshot. If you undeploy a virtual machine and deploy it, the snapshot remains. storage lease The amount of time an unused virtual machine template or configuration exists on a datastore before Lab Manager deletes it or marks it for deletion. This affects only unpublished virtual machine templates. Sysprep See Microsoft Sysprep. Suspend A state in which settings are preserved and actions are no longer performed. To turn off a virtual machine while preserving the current state of a running virtual machine. See also resume. TCP/IP The set of protocols that is the language of the Internet, designed to enable communication between networks regardless of the computing technologies that they use. TCP connects hosts and provides a reliable exchange of data streams with guaranteed delivery. IP specifies the format of packets and handles addressing. template See virtual machine template. undeploy To unregister a virtual machine or configuration from an ESX host. This operation makes the resources associated with that virtual machine available for use by the rest of the virtual environment. unprepare To remove an ESX host from use in the Lab Manager environment. This operation uninstalls the Lab Manager agent. vCenter See VMware vCenter (vCenter), virtual machine disk (.vmdk). VMware, Inc.
Page 171 A file containing a virtual machine configuration. This .vmx file is created after you create a virtual machine. It is used to identify and run a specific virtual machine. virtual machine console An interface to a virtual machine within the larger Lab Manager Web console. Use the virtual machine console to run programs within it or modify guest operating system settings. Lab Manager provides operations ranging from the installation of VMware Tools to media file activity for the guest operating system to snapshots of virtual machines. virtual machine disk (.vmdk) A file or set of files that appears as a physical disk drive to a guest operating system. These files can be on the host machine or on a remote file system. virtual machine template A master image of a virtual machine that typically includes a specified operating system and virtual counterparts to hardware components. A virtual machine template can include an installed guest operating system and a set of applications. virtual router A virtual machine that specifically routes packets between other virtual machines. Lab Manager configures the virtual router when you deploy a fenced configuration and deletes it when you undeploy the configuration. Lab Manager does not create a virtual router for the Block In and Out fencing mode. virtual switch A virtualized network switch used by ESX to manage traffic between virtual machines, the service console, and the physical network adapters on the ESX host. VMFS (Virtual Machine File System) A file system that is optimized for storing virtual machines. One VMFS partition is supported per SCSI storage device or LUN. Different versions of ESX might use different versions of VMFS. For example, VMFS3 was introduced with ESX Server 3. VMkernel In ESX, a high‐performance hypervisor that occupies the virtualization layer and manages most of the physical resources on the hardware, including memory, physical processors, storage, and networking controllers. VMotion A feature that enables you to move running virtual machines from one ESX system to another without interrupting service. It requires licensing on both the source and target hosts. VMotion is activated by the vCenter agent, and vCenter Server centrally coordinates all VMotion activities. See also virtual machine disk (.vmdk). VMware, Inc.
Page 172 VMware ESX A virtualization layer run on physical servers that abstracts processor, memory, storage, and networking resources into multiple virtual machines. ESX is a component of VMware vSphere. Lab Manager requires ESX hosts. VMware High Availability (VMware HA) Supports distributed availability services in an environment that includes ESX and vCenter. If you configured VMware HA and one of the hosts managed by vCenter Server goes down, all virtual machines on that host are immediately restarted on another host. See also DRS (VMware Distributed Resource Scheduler), virtual machine disk (.vmdk). VMware vSphere A software suite, including ESX and vCenter, that virtualizes servers, storage, and networking and enables multiple unmodified operating systems and their applications to run independently in virtual machines while sharing physical resources. The suite delivers comprehensive virtualization, management, resource optimization, application availability, and operational automation capabilities. See also VMware vCenter (vCenter), VMware ESX. VMware vSphere Client A user interface that runs locally in a Windows machine and provides access to the virtual machine’s display. vSphere Client runs on a networked machine that does not need to be the same machine as the vCenter Server. VMware Remote MKS Plugin An application that embeds in the browser to facilitate interaction with a remote machine. This application sends mouse, keyboard, and screen data back and forth across the network. VMware Tools A suite of utilities and drivers that enhances the performance and functionality of your guest operating system. Key features of VMware Tools include some or all of the following, depending on your guest operating system: an SVGA driver, a mouse driver, and the VMware Tools control panel. Guest customization in Lab Manager requires VMware Tools. VMware vCenter (vCenter) A software component of VMware vSphere for deploying and managing virtual machines across the datacenter. With vCenter, datacenters can instantly provision servers, globally manage resources, and eliminate scheduled downtime for hardware maintenance. See also virtual machine disk (.vmdk).
Page 173: Index
63 capturing configurations 54 sample configuration 49 CD images sharing 55 ejecting from virtual machines 79 suspending 62 inserting into virtual machines 78 taking snapshots 63 requirements 105 undeploying 62 swapping 78 virtual networks 59 VMware, Inc.
Page 174 98 media stores 101 copying network templates 30 resource pools 89 CPU hot add 86 users 109 creating version check of VMware Tools 47 configurations 49 discard state 70, 86, 129 LiveLinks 70 network templates 29 editing organizations 27...
Page 175 Microsoft Sysprep package 41 guest operating systems 36 prerequisites 41 VMware Tools 36, 37, 39 selecting the SID generation tool 44 Internet Explorer, set up requirements 15 settings in virtual machine properties 81 IP addressing modes 20, 29, 51, 83, 84, 132, 133...
Page 176 41 editing properties 123 properties roles and rights 153 of configurations 68 sharing 30 of datastores 96 networks of groups 113 adding to configurations 67 of hosts 92 and configurations 56 of media 107 host spanning 59 VMware, Inc.
Page 177 81, 99, 131, 143 roles SupportLink tab 142 adding 113 suspending deleting 114 configurations 62 editing properties 114 virtual machines 76 roles and rights 155 synchronizing media library with media store files 105 roles and rights system alerts 137 VMware, Inc.
Page 178 79 virtual hardware installing ActiveX 75 upgrading for a configuration 69 installing VMware Remote MKS Plugin 75 upgrading for virtual machine templates 134 leases 61, 74, 81, 143 upgrading for virtual machines 85 moving from one datastore to another 100...
Page 179 157 virtual router 56 workspaces VMware Distributed Power Management 92 adding or removing resource pools 121 VMware Distributed Resource Scheduler support 14 adding users and groups 120 VMware Fault Tolerance support 14 creating 28 VMware High Availability support 14...
Page 180 Lab Manager User’s Guide VMware, Inc.

This manual is also suitable for:

Lab manager 4.0

VMware VC-VLM4-C - vCenter Lab Manager User Manual

1 Getting Started with Lab Manager

2 Adding Resources

3 Adding Users and Groups

4 Setting up Organizations and Workspaces

5 Setting up Network Templates

6 Setting up Virtual Machine Templates

7 Working with Configurations

8 Working with Virtual Machines

9 Managing Resources

10 Managing the Media Library

11 Managing Users, Groups, and Roles

12 Managing Organizations and Workspaces

13 Managing Network Templates

14 Managing Virtual Machine Templates

15 Managing Lab Manager Settings

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for VMware VC-VLM4-C - vCenter Lab Manager

Summary of Contents for VMware VC-VLM4-C - vCenter Lab Manager