Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Executing a Provision Job

This topic describes how to execute a Provision Job, and explains the actions the system takes on behalf of the job. It includes the following sections:

To execute a Provision Job 

You execute an existing Provision Job from the Jobs folder.

In the Jobs folder, select the Provision Job, right-click, and select Execute.

This procedure executes the job immediately. (To schedule the job's execution for a specific date and time, see Provision Job - Schedules.)

 If your system is configured to require approval for this job type, select Execute on Approval and then click Browse to display the Approval Information dialog box. For more information, see Provision Job - Execute on Approval and Approval type settings

The job appears on the Tasks in Progress view, where you can view its status or cancel it, if necessary.


  • If you execute a Provision Job against target devices that are not booted, the Provision Job remains in the Task in Progress pane for the time set in the JOB_TIMEOUT Job property or until the device boots up. By default, the JOB_TIMEOUT value is 0, which means that the job does not time out. For information, see Defining timeouts for jobs.
  • If you execute a Provision Job on servers already provisioned, the job re-provisions the servers. For information, see Reprovisioning servers.

What happens when a Provision Job executes

When you execute a Provision Job, the provisioning environment determines the actions the system takes.

  • In PXE environments:
    • If you select a bare metal server that just completed a network boot and is waiting for provisioning instructions, the server is provisioned.
    • If you select an existing server, you must reboot the server. Then the server is provisioned automatically.
  • In JumpStart, NIM, and Ignite Environments:
    For both bare metal and existing servers, if your system package contains a reboot script, the server is provisioned automatically. (If your system package does not contain a reboot script, you must manually force the server to boot from the network, and the server is provisioned automatically.)
  • In all environments:
    You can re-provision a server by re-executing the Provision Job associated with the server. If the existing server was part of the BMC Server Automation system before you re-provisioned it, you must redefine any jobs you want to run on the newly re-provisioned server. Jobs that were defined for the server before you re-provisioned it do not run now, even if you keep the same host name for the machine.
    The newly provisioned or re-provisioned server is part of the BMC Server Automation system.

Where to go from here

Was this page helpful? Yes No Submitting... Thank you