7.1

Table Of Contents
Preparing Your SCVMM Environment
Before you begin creating SCVMM templates and hardware proles for use in vRealize Automation
machine provisioning, you must understand the naming restrictions on template and hardware prole
names, and congure SCVMM network and storage seings.
Template and Hardware Profile Naming
Because of naming conventions that SCVMM and vRealize Automation use for templates and hardware
proles, do not start your template or hardware prole names with the words temporary or prole. For
example, the following words are ignored during data collection:
n
TemporaryTemplate
n
Temporary Template
n
TemporaryProle
n
Temporary Prole
n
Prole
Required Network Configuration for SCVMM Clusters
SCVMM clusters only expose virtual networks to vRealize Automation, so you must have a 1:1 relationship
between your virtual and logical networks. Using the SCVMM console, map each logical network to a
virtual network and congure your SCVMM cluster to access machines through the virtual network.
Required Storage Configuration for SCVMM Clusters
On SCVMM Hyper-V clusters, vRealize Automation collects data and provisions on shared volumes only.
Using the SCVMM console, congure your clusters to use shared resource volumes for storage.
Required Storage Configuration for Standalone SCVMM Hosts
For standalone SCVMM hosts, vRealize Automation collects data and provisions on the default virtual
machine path. Using the SCVMM console, congure default virtual machine paths for your standalone
hosts.
Chapter 1 External Preparations for Provisioning
VMware, Inc. 23