vRealize Automation boots a newly provisioned machine from an ISO image, and then passes control to the specified 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:
Communication with SCCM requires the NetBIOS name of the SCCM server.
Work with your network administrator to ensure that at least one Distributed Execution Manager (DEM) can resolve the FQDN of the SCCM server to its NetBIOS name.
You do not need to place DEMs directly on the same network as the SCCM server, but DEMs need to be able to reach the SCCM server over IP.
Create a software package that includes the vRealize Automation guest agent. See Create a Software Package for SCCM Provisioning.
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, see SCCM documentation.
Create a zero touch boot ISO image for the task sequence. By default, SCCM creates a light touch boot ISO image. For information about configuring SCCM for zero touch ISO images, see SCCM documentation.
Copy the ISO image to the location required by your virtualization platform. If you do not know the appropriate location, refer to the documentation provided by your hypervisor.
Gather the following information so that blueprint architects can include it on blueprints:
The name of the collection containing the task sequence.
The fully qualified domain name of the SCCM server on which the collection containing the sequence resides.
The site code of the SCCM server.
Administrator-level credentials for the SCCM server.
(Optional) For SCVMM integrations, the ISO, virtual hard disk, or hardware profile to attach to provisioned machines.