Configuring boot image files
For provisioning in the PXE environment, you must create boot image files specifically for use with TrueSight Server Automation provisioning. You can review and change configuration settings for each image file type.
When provisioning a device, the provisioning process uses an image that contains, among other things, device-specific network drivers that interact with the hardware and retrieve configuration information (such as the MAC address) for the device.
To prepare for Windows and Linux provisioning, create the appropriate WinPE or Gentoo Linux images that contain generic network drivers that work for most hardware types. By default, the TrueSight Server Automation Console contains the following pointers to these image files:
Boot image file
Used only when working with legacy system packages.
Used to provision x86 Linux machines.
Used to provision AMD64 Linux machines.
Skip Linux Pre-Install
Used to provision a device with the Red Hat, VMware ESX, or SUSE operating system when you want to skip the Gentoo pre-installation image. For information, see Using the Skip Linux Pre-Install image option.
ESXi 4.0 (vmkboot.gz)
Used to provision AMD64 machines with ESXi 4.0. For information, see Provisioning target servers with ESXi 4.0.
Used to provision x86 Windows machines using WinPE 2.x.
Used to provision AMD64 and Windows machines using WinPE 2.x.
Used to provision x86 Windows machines from removable or CD-ROM media connected to the machine using WinPE 2.x. For information, see Provisioning Windows 2003 or later servers from a local data store.
Used to provision AMD64 and Windows machines from removable or CD-ROM media connected to the machine using WinPE 2.x. For information, see Provisioning Windows 2003 or later servers from a local data store.
Used to provision AMD64 and Windows machines using WinPE 5.1.
Used to provision AMD64 and Windows machines from removable or CD-ROM media connected to the machine using WinPE 5.1. For information, see Provisioning Windows 2003 or later servers from a local data store.
The pointers become operational after you create the corresponding image files and place them in their correct locations on the TFTP Server.
Each image file has associated configuration settings, including a description and an indication of which image file is the default for your environment. You can review and change these configuration settings using the Image files tab.
In addition, to provision a device that requires a custom image file containing specialized network drivers, you can register the custom image file. After you register the custom image file, you can assign it to the specific device you want to provision.
Typically, a TrueSight Server Automation technician creates the custom image file for you. This file must be located in the same directory as the standard image files:
- WinPE image: Under the base TFTP directory, for example C:\tftproot.
- Gentoo image: Under the appropriate pxelinux directory for the client architecture under the base TFTP directory. For example, /tftproot/X86PC/pxelinux.
- DOS image: tftproot/X86PC/pxelinux
To configure a boot image file:
- Choose Configuration > Provisioning Configurations.
- Click the .
- Add or edit the information for the image type. For information, see The Image Files tab.
- Click OK to save the current values.