Creating virtual machine templates

This section describes the overview steps when creating a virtual machine (VM) template on VMware Virtualcenter. A VM template is a reusable image created from an existing Virtual Machine.

You use these VM templates when creating a Virtual Guest Package in BMC BladeLogic Server Automation.

Before you begin

Before creating a VM template, you must make sure that your version of vCenter supports OS Customization for the specified Guest OS. See the VMware Documentation regarding Operating System Compatibility for vCenter Server.

Adding a licensed BMC BladeLogic Server Automation Agent to the VM template

Before you use a VM template to create a VirtualGuest Package, a licensed BMC BladeLogic Server Automation Agent must be added to the template

1. Convert the template to a VM.
2. Install a licensed agent on the VM.
3. Make sure that there are no firewall issues.
4. From a remote machine, use the BBSA utility 'agentinfo' to ensure connectivity.
    Enter the following command:
   agentinfo <hostname>
    If the agent is not reachable, you may need to disable the firewall on the VM.
5. Delete the BladeLogicRSCD user before converting the VM to a template.
6. Convert the VM back to a template

Linux VM templates

Linux VM templates must include the following:

1. Modify the /etc/rc.d/rc.local script to ensure successful DNS registration.
2. Distribute the UnixUsers custom object to the BMC BladeLogic Server Automation Agent.
    You must do this to validate users created on VirtualGuests.

Disabling Windows 2008 Password complexity checks

If you do not want the Windows 2008 Password Complexity check enabled on your VMs, disable it in the template. If you do not disable this check, VM creation will fail during the Create User phase if you do not supply a complex password.

1. Convert your template to a VM
2. In the VM, click Start > Administrative Tools > Local Security Policy.
3. Select * Security Settings > Account Policies > Password Policy*.
4. Right-click Passwords must meet complexity requirements and then select Properties.
5. Disable this option.
6. Log out of the VM and convert it back to a template.

VMware Tools

VMware Tools must be installed in all templates. Refer to the VMware VirtualCenter Templates documentation for installation details.

Microsoft System Preparation (Sysprep) tool

VirtualCenter uses the Microsoft System Preparation (Sysprep) tool to automate the deployment of various Microsoft operating systems. Sysprep must be present on the Virtual Center to support OS Customization for Windows. If Sysprep is not present for a specific version of Windows 2003, OS Customization will fail. This in turn causes the VirtualGuest create task to fail.