Walkthrough: Provisioning Microsoft Windows 2012 on a bare metal machine
TrueSight Server Automation can provision operating systems on bare metal computer systems using the Preboot Execution Environment (PXE) architecture. This topic describes how to provision Microsoft Windows 2012 on a bare metal machine.
This topic includes the following sections:
- Introduction
- What do I need to do before I get started?
- How to provision Microsoft Windows 2012 on a bare metal machine
- Wrapping it up
- Where to go from here
Introduction
TrueSight Server Automation provisioning performs unattended installations of operating systems onto new machines ("bare metal" machines) or reprovisions existing machines. To provision higher layers of the server stack above the operating system, you can run jobs that configure server settings, deploy files, and install software. In this example, you will provision the Microsoft Windows 2012 OS onto a bare metal machine.
What do I need to do before I get started?
This example assumes that you have performed all of the provisioning configuration steps outlined in the following table:
Task | Description |
---|---|
Review and meet provisioning requirements | The provisioning infrastructure includes TrueSight Server Automation software and additional supporting software, installed on networked hosts and configured for PXE-based provisioning. See Reviewing-requirements-for-provisioning and Implementation-process-for-provisioning. |
Install the PXE and TFTP servers | The PXE server delivers instructions to servers being provisioned so they can download a bootstrap program. The TFTP server serves boot images required for a network-based installation of the operating system. (TrueSight Server Automation provisioning requires that the PXE server and the TFTP server reside on the same host computer.) |
Configure the PXE and TFTP servers | Configure the PXE and TFTP servers to communicate with the TrueSight Server Automation database and target servers being provisioned. To configure, you can use the PXE/TFTP Server Configuration tool. (To configure the PXE server for a multiple database provisioning environment, you must use this tool.) See Configuring-the-PXE-and-TFTP-servers. |
Configure the DHCP server to support the provisioning process | The TrueSight Server Automation provisioning process requires a DHCP server, which assigns IP addresses to the devices being provisioned and (in a one-database environment) configures the location of the Application Server. See Configuring-a-DHCP-server-on-Linux and Configuring-a-DHCP-server-on-Windows. |
Set up and share the data store | On the host computer for the data store, set up a directory structure to store the operating system installers required for provisioning. |
Stock the data store | Copy all required files into the data store, including operating system installers, files for Windows drivers, and files needed to install RSCD agents on target devices. See Stocking-the-data-store. |
Prepare agents for provisioning | Set up RSCD agents so that they can be installed on target devices as part of the provisioning process. See Preparing-agents-for-provisioning. |
Create WinPE boot images for Microsoft Windows systems | The provisioning process uses WinPE for bare metal provisioning of Microsoft Windows operating systems. You must create the WinPE boot images for Windows operating systems and include the drivers required for your networking environment. See Creating-WinPE-boot-image-files. |
Prepare for UEFI booting | If you plan to use Unified Extensible Firmware Interface (UEFI), instead of BIOS, for booting hardware over the network during provisioning, perform several preparatory tasks to enable the use of UEFI. See Preparing for UEFI booting. |
How to provision Microsoft Windows 2012 on a bare metal machine
- For this walkthrough, you log on as BLAdmin, the default superuser for TrueSight Server Automation. Note that in live deployments, BMC recommends you grant access based on roles with a narrower set of permissions.
- In this example you use the out-of the box configuration for the default boot image files.
| Procedure | Example screen |
---|---|---|
1 | Add a DataStore.
| |
2 | Add a device. The Add Device panel lets you specify the MAC address of the new device.
| |
3 | Configure the Provisioning Manager.
| |
4 | Create a Microsoft Windows Server 2012 system package
| |
5 | Complete the General tab:
| |
6 | Complete the Disk Partition tab:
| |
7 | Complete the Basic Configuration tab:
| |
8 | Complete the Computer Settings tab:
| |
9 | Complete the Local Properties tab:
| |
10 | Create the Provision Job.
| |
11 | Complete the Provision Job - General panel:
Use the defaults for all other settings. | |
12 | Complete the Provision Job - System Package Properties panel:
Use the defaults for all other settings. | |
13 | Complete the Provision Job - Devices to provision panel:
Use the defaults for all other settings. | |
14 | Complete the Provision Job - Schedules panel: Check the Execute job now option to trigger immediate execution when you finish defining the Provision job. | |
15 | Complete the Provision Job - Permissions panel:
The Provision job executes immediately. The job is stored in the Jobs folder. |
Wrapping it up
In this walkthrough, you created a system package for a Microsoft Windows Server 2012 image and provisioned that image to a bare metal system. You can now set up post-provisioning jobs to perform additional configuration on the server and install software.
Where to go from here
For a description of provisioning a new virtual machine onto a VMware host, see Walkthrough-Provisioning-a-Linux-VM-on-VMware.