The Post-Install Configuration panel lets you specify processes to run after the operating system is installed on the server. For Microsoft Windows R2 operating systems, you must provide a post-install script to complete the R2 portion of the installation. The following sections describe the fields available on the Post-Install Configuration panel.
Check this option to install an RSCD agent on the target servers. (An agent must be installed on every server that you want to manage using the BMC Server Automation Console or Network Shell.)
Agent Install Options* (Optional)
Type one or more properties that override the default settings for the Windows RSCD agent installation. To specify a property, use the format: PROPERTY=value. Separate properties with a space.
INSTALLDIR="C:\Program Files\RSCD" KEYLOGS=0 MAPUSER=Administrator RSCDPORT=4400
The following table lists the properties:
The target location for the RSCD installation. The default is C:\Program Files\BMC Software\BladeLogic\RSCD
Any valid path for Windows. Enclose the path in double quotation marks ("").
Enables or disables the use of keystroke logs for nexec commands.
1 (enable) or 0 (disable).
Location of agent log files. The default is C:\Program Files\BMC Software\BladeLogic\RSCD
Valid directory for RSCD log files.
A local user's account. If you specify a value for this option, the exports configuration file is modified to force the agent to impersonate the specified user for all activities. By default the property is not set and no user mapping is created.
Sets the RSCD port number in the rscd entry of the agent's secure configuration file.
Valid port number
Enables or disables use of secure (digitally signed) logs for the RSCD agent.
1 (enable) or 0 (disable).
Suppresses server reboot after agent installation. Without this parameter, the server reboots when the agent installation finishes.
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.
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.
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.
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.
The runonce.bat file runs one time when Windows starts for the first time after an unattended installation of the operating system.
Any commands you enter into this 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 jobs you specify.
Use the following lines to complete the R2 portion of a Windows 2003 R2 installation. The last line, disabling the Windows firewall, is optional.
For Windows 2003 R2:
<data_store_folder_name> in the second line is the same folder that you specified in the Name field when you created the system package. It is the CMPNENTS folder's parent folder in the data store.
These instructions assume that the data store contains the Windows R2 installation media in a CMPNENTS folder. For information about setting up the data store for Windows R2 systems, see Stocking the data store.
The second line in the preceding script executes the setup2.exe utility from the Windows R2 installation media. The r: drive was created when you created the Windows 2003 R2 or Windows 2008 R2 system package type. The system maps to r: by default.
For Windows 2008 R2:
Use the following lines to complete the R2 portion of a Windows 2008 R2 installation. The last line, disabling the Windows firewall, is optional.
A system package for Windows 2008 Server Core requires the following entries on this panel. Otherwise, the Provision Jobs that use the system package do not complete successfully.
In the Agent Installation Options field (earlier on the panel), enter the following line:
In the Post-Install Script field, enter the following line:
The first line, which prevents the server from rebooting, allows the runonce.bat file to complete. The second line forces the reboot later, which is required to start up the RSCD agent.
Proceed to the Local properties - Windows tab.