Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Creating a VGP using BMC Server Automation

You can build a repeatable process for deploying new virtual systems by using a virtual guest package (VGP). The VGP describes the new virtual system you want to add.

For example, you can base the VGP on an existing VMware vCenter template or create the VGP using values of your own, if you do not have an existing machine or template on which to base the configuration. Having a base package from which to deploy new virtual machines helps enforce consistency and standards, such as including Antivirus and management software on any new virtual machine.

Note

To ensure that BMC Cloud Lifecycle Management can create a VGP from a blueprint, make sure that the VGP has at least one NIC configured in BMC Server Automation (even if you have more than one network configured in the blueprint). Do not configure more networks in the VGP than what you have configured in the blueprint.

When you have a NIC configured, BMC Cloud Lifecycle Management can determine the type of adapter that is configured in the VGP, and then copy that adapter type when creating new entries during provisioning. If no adapter exists to copy, then you will see an error.

Refer to the following topics for information about creating a VGP for a specific virtualization environment:

Note

For VMware and Microsoft Hyper-V,  you must select the Customize OS checkbox on the appropriate Virtual Guest Job panel if the VGP is based on a template:

Virtualization platform

Location of Customize OS checkbox in Virtual Guest Job wizard

vCenter

VMware - Config

Hyper-V

Microsoft Hyper-V - Basic

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*