Upgrading the Provisioning System

This topic provides instructions for upgrading the components that BMC Server Automation uses in provisioning operating systems to bare metal machines.

This task assumes you have upgraded the provisioning server (the Application Server enabled for provisioning.)

Upgrade the components

1. If you have not already done so, upgrade all BMC Server Automation Consoles. See Upgrading-the-BMC-Server-Automation-Console
2. If you have not already done so, upgrade the agent on the data store server. See Upgrading-RSCD-agents.
3. If you have not already done so, upgrade the PXE and TFTP Servers. See Upgrading-a-PXE-server-on-Windows or Upgrading-a-PXE-server-on-Linux-or-UNIX.
4. To install the current release of the agents while provisioning bare metal machines, upgrade your agent installers in the data store.
5. Start the PXE and TFTP Servers. See Starting-and-stopping-a-PXE-server and Starting-and-stopping-a-TFTP-server.

Upgrade the provisioning files

1. Extract the new provision-files.zip. 
2. Locate the bmilinux.tar file (in the \provisioning\pxe directory) and copy it to the datastore directory.
3. Locate the bmiwin.exe file (in the \provisioning\pxe directory) and copy it to the datastore\bmi directory. 
4. (Windows only) Locate the bllibeay32.dll and blssleay32.dll files (in the \provisioning\winpe\x86 directory) and copy them to the datastore\bmi directory.
   See Setting up a data store and the BMC Communities forum article: 8.5 Upgrade - Changes to provisioning files for BMI. 
5. Using the new provisioning-files.zip, create new Gentoo or WinPE boot images, as discussed in Creating-boot-image-files-and-placeholders.

Note: After the upgrade, you cannot continue using any existing Gentoo or WinPE boot images that were created in the previous version of BMC Server Automation. This is only applicable while upgrading major releases or service packs. You can continue using the existing boot images in case of patch-level upgrades.