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.

Post-install configuration - ESX

The Post-install Configuration tab lets you specify the installation of a BMC Server Automation RSCD agent on the target server, specify a Batch Job that runs after the operating system is installed on the server, and enter commands that are included in the Kickstart file.

Field definitions

Install RSCD agent

Check this option to install an agent on the server being provisioned. (An agent must be installed on every server you want to manage using the BMC Server Automation Console or Network Shell.)

Push ACLs

Check this option to push the ACLs defined for the server in the BMC Server Automation system to the RSCD agent you are installing on the server.
Selecting this option automatically translates the permissions you have defined for the server in the BMC Server Automation system into a users configuration file on the RSCD agent. In this way, you control users' access to the server not only through the BMC Server Automation Console but also through Network Shell and the BLCLI.

Run post-install batch job

Check this option to run a post-install Batch Job that can install software and configure the server. Then for Path to post-install job, enter the path to the job or click Browse to select it.
In order to check Run post-install batch job, you must also check Install RSCD agent, because running a post-install job requires that there is an agent installed on the server.
If you specify a Post-install Batch Job, make sure that the provisioning operator who runs the provisioning wizard logs is using a role that has Read and Execute authorizations on the Batch Job and has Read and Execute authorizations on all the Jobs contained in the Batch Job.

Force Post-install Batch Job

Select this option to ensure that the post-install Batch Job runs, even if RSCD agent enrollment fails. If you do not select this option, the post-provisioning Batch Job does not execute if RSCD agent enrollment fails.
For example, if you use DNS, the RSCD agent enrollment cannot succeed until a DNS entry for the target server is provided. If you want to provide the DNS entry using a script in the Batch Job, you need the Batch Job to run even when the RSCD agent enrollment fails.

Application Server for BMI callback

For load balancing, you can use different Application Servers for reporting Provision Job completion status. Use these fields to identify the Application Server to which target servers in this job should report their Provision Job completion status.

  • IP address — Enter the IP address of the Application Server or click Select Property to specify a property that contains the value.
  • Port — Accept the default (9831) or enter a different port number.

Post-install Script

Commands that you want added to the post-install section of the Kickstart file, which runs once after a server reboots for the first time after an unattended installation of an ESX operating system. Enter the commands or click Select Property  to insert a parameter.
Any commands you enter into the post-install script are appended to commands that BMC Server Automation provisioning also inserts in this script, including a command to install the RSCD agent. The commands that you enter run before any post-install Batch Job that you specify.

Proceed to the Local properties - ESX tab.

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