7.1

Table Of Contents
Prerequisites
n
Prepare a kickstart or autoYaST conguration le. See “Prepare the Linux Kickstart Conguration
Sample File,” on page 47.
n
Your script must return a non-zero value on failure to prevent machine provisioning failure.
Procedure
1 Create or identify the script you want to use.
2 Save the script as NN_scriptname.
NN is a two digit number. Scripts are executed in order from lowest to highest. If two scripts have the
same number, the order is alphabetical based on scriptname.
3 Make your script executable.
4 Locate the post-installation section of your kickstart or autoYaST conguration le.
In kickstart, this is indicated by %post. In autoYaST, this is indicated by post-scripts.
5 Modify the post-installation section of the conguration le to copy or install your script into
the /usr/share/gugent/site/workitem directory of your choice.
Custom scripts are most commonly run for virtual kickstart/autoYaST with the work items SetupOS (for
create provisioning) and CustomizeOS (for clone provisioning), but you can run scripts at any point in
the workow.
For example, you can modify the conguration le to copy the script 11_addusers.sh to
the /usr/share/gugent/site/SetupOS directory on a newly provisioned machine by using the following
command:
cp nfs:172.20.9.59/linuxscripts/11_addusers.sh /usr/share/gugent/site/SetupOS
The Linux agent runs the script in the order specied by the work item directory and the script le name.
Preparing for SCCM Provisioning
vRealize Automation boots a newly provisioned machine from an ISO image, and then passes control to the
specied SCCM task sequence.
SCCM provisioning is supported for the deployment of Windows operating systems. Linux is not
supported. Software distribution and updates are not supported.
The following is a high-level overview of the steps required to prepare for SCCM provisioning:
1 Consult with your network administrator to ensure that the following network requirements are met:
n
Communication with SCCM requires the NetBios name of the SCCM server. At least one
Distributed Execution Manager (DEM) must be able to resolve the fully qualied name of the
SCCM server to its NetBios name.
n
The SCCM server and the vRealize Automation server must be on the same network and available
to each other.
2 Create a software package that includes the vRealize Automation guest agent. See “Create a Software
Package for SCCM Provisioning,” on page 49.
3 In SCCM, create the desired task sequence for provisioning the machine. The nal step must be to
install the software package you created that contains the vRealize Automation guest agent. For
information about creating task sequences and installing software packages, see SCCM documentation.
4 Create a zero touch boot ISO image for the task sequence. By default, SCCM creates a light touch boot
ISO image. For information about conguring SCCM for zero touch ISO images, see SCCM
documentation.
Configuring vRealize Automation
48 VMware, Inc.