Boot image files and placeholders


To provision Microsoft Windows and Linux machines, you must create boot image files specific to BMC Server Automation. The system contains placeholders for these files.

The type of boot image file you create depends on the types of machines you plan to provision.

If you plan to provision...

You need to create...

Windows machines

Create WinPE image files. See Creating-WinPE-2-0-and-later-boot-image-files

Linux machines

Create a Gentoo Linux image file. See Creating-a-Gentoo-Linux-image-file.

A placeholder is a pointer to a BMC Server Automation-specific image file. After you create the image files and put them in the correct places on the TFTP server, you can use the default placeholders built into the system.

Placeholders let you specify which image file to use in provisioning a device. For example, if you add a device, the BMC Server Automation Console displays a drop-down menu of image files that you can associate with the device.

BMC Server Automation contains the following default placeholders:

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

Boot image configurations

In addition to pointing to an image file, a placeholder provides default configuration settings for the image in the BMC Server Automation system. These configuration settings include: image type, image file name, description, image path (kernel name), and whether the image is the default boot image.

To view configuration settings for an image, in the BMC Server Automation Console, select Configurations > Provisioning Configurations. Then click the Image Files tab.

 

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