Regarding the Firmware (BIOS/UEFI) settings from Image Mapping in VMware Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

This document describes how Firmware settings (BIOS/UEFI) of a template are handled when deploying a virtual machine using Image Mapping in VMware Aria Automation.
Specifically, it covers the following operational behaviors:

• Whether the Firmware settings after deployment match the settings of the source template.
• Whether there is a possibility that the settings are automatically overwritten by Aria Automation.

Environment

VMware Aria Automation: 8.x

VMware vCenter Server: 8.0

Resolution

In the standard provisioning process of VMware Aria Automation, the hardware configuration of the template is respected.

• The Firmware (BIOS / UEFI) settings and Secure Boot (enabled/disabled) settings of the vCenter template specified in the Image Mapping are applied directly to the virtual machine after deployment.
• In the standard functionality of Aria Automation, these settings are not unintentionally changed or overwritten with uniform settings.

Note:

If explicit customizations are integrated into the provisioning process, such as those listed below, the settings may be overwritten.

When a process to dynamically change the hardware configuration is explicitly included during provisioning using vRealize Orchestrator (vRO) workflows or Action Based Extensibility (ABX) within the Cloud Template.

Recommendations

• When using a new template or a different firmware configuration, it is recommended to perform a test deployment in advance.
• After deployment is complete, it is recommended to verify from the "Edit Settings" menu of the virtual machine that the Firmware settings are in the intended state (BIOS or UEFI).

Additional Information

Japanese KB: VMware Aria Automationのイメージマッピングにおけるファームウェア（BIOS/UEFI）設定について