6.2
Table Of Contents
- IaaS Configuration for Physical Machines
- Contents
- IaaS Configuration for Physical Platforms
- Configuring IaaS
- Optional Configurations
- Preparing for Provisioning
- Enabling Visual Basic Scripts in Provisioning
- Choosing a Provisioning Scenario
- Preparing for PXE Provisioning
- Preparing for Linux Kickstart Provisioning
- Preparing for SCCM Provisioning
- Preparing for WIM Provisioning
- Creating Blueprints
- Configuring Advanced Blueprint Settings
- Managing Infrastructure
- Monitoring Workflows and Viewing Logs
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 must be able to resolve the fully qualified 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.
3 In SCCM, create the desired task sequence for provisioning the machine. The final 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, please see the SCCM
documentation.
4 Create the boot ISO image for the task sequence and place it in the required location. Record the
address.
Table 3‑3. Required Location
Scenario Location
HP iLO Place the image in a web-accessible location.
Dell iDRAC Place the image in a location available to NFS or CIFS.
PXE provisioning The appropriate location is determined by your PXE server
configuration.
5 Gather the following information so that tenant administrators and business group managers can
include it in their blueprints:
n
The name of the collection containing the task sequence.
n
The fully qualified domain name of the SCCM server on which the collection containing the
sequence resides.
n
The site code of the SCCM server.
n
Administrator-level credentials for the SCCM server.
Note You can create a build profile with the property set SCCMProvisioningProperties to include all
of this required information. This makes it easier for tenant administrators and business group
managers to include this information correctly in their blueprints.
Create a Software Package for SCCM Provisioning
The final step in your SCCM task sequence must be to install a software package that includes the
vRealize Automation guest agent.
IaaS Configuration for Physical Machines
VMware, Inc. 42