Difference between revisions of "Lab Manager"

From vwiki
Jump to navigation Jump to search
Line 19: Line 19:


== Export a Machine from Lab Manager ==
== Export a Machine from Lab Manager ==
Note that if you can't satisfy the [[Lab_Manager#Prerequisites|Prerequisites]] then you can always use [[VMware Converter]]...
# Deploy a single VM from a template and power off
# Use Converter to create a clone in a new location
=== Prerequisites ===
=== Prerequisites ===
* Your source ESX's need to have SMB access to the UNC path your going to copy to, from an ESX test the following...
* Your source ESX's need to have SMB access to the UNC path your going to copy to, from an ESX test the following...
Line 29: Line 33:
*#* <code> umount //Dest_Win_Server/D$ /tmp </code>
*#* <code> umount //Dest_Win_Server/D$ /tmp </code>
* Lab Manager server must not have [http://support.microsoft.com/kb/956572 MS KB 956572] installed
* Lab Manager server must not have [http://support.microsoft.com/kb/956572 MS KB 956572] installed
=== Procedure ===
# Locate the machine within the '''VM Template''' screen
# Right-click over the VM and select '''Export...'''
# Enter a UNC path
#* Must be accessible via SMB from the ESX's
#* Must be a sub-folder, not a root
# Enter user/pass with Write rights on UNC share


== Change a Deployed VM's Resources ==
== Change a Deployed VM's Resources ==

Revision as of 14:17, 7 October 2010

Import Machine into Lab Manager

Prerequisites

  • Source Virtual Machine
    • Will be cloned (or moved) into Lab Manager, can be a template or a VM (but must be powered off)
  • Destination info
    • Hostname
    • Description (optional)
    • Network (an existing Physical [lab] Network)
    • Datastore

Procedure

  1. Within Lab Manager, select the correct Organisation
  2. Go to Build and Deploy > VM Templates, and hit the Import VM Template... button (if the button doesn't exist then your account doesn't have sufficient rights)
  3. Enter the new Template's Name and Description, then locate the source Virtual Machine and hit Next
  4. Select the appropriate Network and Datastore, leave Make a Copy option selected unless you want the source VM to be lost/moved, then hit Import
  5. Once the import has completed, check/change the following options
    • Owner
    • Published

Export a Machine from Lab Manager

Note that if you can't satisfy the Prerequisites then you can always use VMware Converter...

  1. Deploy a single VM from a template and power off
  2. Use Converter to create a clone in a new location

Prerequisites

  • Your source ESX's need to have SMB access to the UNC path your going to copy to, from an ESX test the following...
    1. SMB allowed through ESX firewall
      • esxcfg-firewall -q smbClient
    2. ESX can access server via SMB
      • smbmount <share> <mountpoint> -o username=<username>
      • EG smbmount //Dest_Win_Server/D$ /tmp -o username=Administrator
    3. If successful, remove the mount
      • umount //Dest_Win_Server/D$ /tmp
  • Lab Manager server must not have MS KB 956572 installed

Procedure

  1. Locate the machine within the VM Template screen
  2. Right-click over the VM and select Export...
  3. Enter a UNC path
    • Must be accessible via SMB from the ESX's
    • Must be a sub-folder, not a root
  4. Enter user/pass with Write rights on UNC share

Change a Deployed VM's Resources

In theory a deployed VM's config shouldn't be changed, in reality its bound to be required at some point as a one off, but its quite limited on what can be acheived.

Any changes will be lost when the template is undeployed and its state not saved. If this isn't wanted, or if its a regular occurrence, the VM templates should be edited (CPU and memory can be edited with Lab Manager, the VM doesn't need to be re-imported).

  • CPU - Update the deployed VM's config through vCentre
  • Memory - Update the deployed VM's config through vCentre
  • Network - Update the deployed VM's config through vCentre
  • Disk - Can't be changed, a deployed template is a delta from the original template (think snapshotting), you must reconfigure the template

Troubleshooting

Unable to Deploy Virtual Machine

External network PortGroup is not deployed on host "ESX"
Caused by a Physical Network not being correctly configured on the ESX property

  1. Go to Manage > Resources
  2. Locate the problem network and go to Properties
  3. Update the Physical Network Bindings for the relevant ESX


Unable to deploy VM VM in VirtualCenter. The session is not authenticated.
OR Failed to collect requirements for virtual machine VM. The session is not authenticated.
Caused by logon from Lab Manager to Virtual Centre being unable to authenticate, assuming the user/pass on the VC hasn't been changed, this can be corrected by...

  1. Go to System > Settings
  2. Go to the VirtualCentre tab
  3. Click on OK to re-apply the user/pass

Lab Manager Disconnected from ESX

Check/restart the Lab Manager agent service that runs on the ESX...

  • service vsla-agent status