Setting up the provisioning environment
Before you can use BMC Server Automation to perform unattended installations of operating systems on servers, you must set up all the functional components of the BMC Server Automation provisioning system. Generally, you need to perform these tasks only once unless you are changing the configuration of your provisioning system.
For a high-level view of the tasks in a general provisioning workflow, see Implementation process for provisioning.
The following table lists the technologies used for provisioning of various types of servers and the topics associated with each platform.
| Provisioning platform | See these topics |
|---|---|
| All | |
| All | Importing and managing devices |
| Windows, Linux, ESX, and ESXi servers via the Pre-boot Execution Environment (PXE) | To set up the environment for Windows, Linux, ESX, and ESXi servers, see: Setting up and sharing a data store Configuring the data store for PXE provisioning Creating boot image files and placeholders Configuring a DHCP server on Windows Configuring a DHCP server on Linux Configuring the PXE and TFTP servers Configuring system package types for Windows and Linux Creating a system package for Windows and Linux For an example of how to set up and implement PXE-based provisioning, see How to use BMC Server Automation for PXE-based provisioning. |
| Solaris SPARC and x86 servers via Oracle Solaris JumpStart software or Oracle Solaris Automated Installer | To set up the environment to provision Solaris systems, see Setting up Solaris provisioning. |
| AIX servers via the IBM Network Installation Manager (NIM) software | To set up the NIM environment, see Setting up AIX provisioning. |
| HP-UX servers via Ignite software | To set up the Ignite environment, see Setting up HP-UX provisioning. |
| All (optional) | Properties and provisioning |
Comments
Log in or register to comment.