6.2
Table Of Contents
- IaaS Configuration for Virtual Platforms
- Contents
- IaaS Configuration for Virtual Platforms
- Configuring IaaS
- Configuring IaaS Checklist
- Custom Properties in Machine Provisioning, Blueprints, and Build Profiles
- Bringing Resources Under vRealize Automation Management
- Choosing an Endpoint Scenario
- Store User Credentials for Endpoints
- Create a vSphere Endpoint
- Create a vSphere Endpoint with Networking Integration
- Create a NetApp ONTAP Endpoint
- Create a KVM (RHEV) Endpoint
- Create a Standalone Hyper-V Endpoint
- Create an SCVMM Endpoint
- Create a Xen Pool Endpoint
- Create a XenServer Endpoint
- Preparing an Endpoint CSV File for Import
- Import a List of Endpoints
- Create a Fabric Group
- Configure Machine Prefixes
- Create a Business Group
- Virtual Reservations
- Optional Configurations
- Build Profiles and Property Sets
- Reservation Policies
- Storage Reservation Policies
- Static IP Address Assignment
- Cost Profiles
- Enabling Users to Select Datacenter Locations
- Active Directory Cleanup Plugin
- Enabling Remote Desktop Connections
- Enabling Connections to Machines Using SSH
- Preparing for Provisioning
- Space-Efficient Storage for Virtual Provisioning
- Preparing Your SCVMM Environment
- Enabling Visual Basic Scripts in Provisioning
- Choosing a Provisioning Scenario
- Checklist for Virtual Provisioning by Cloning Preparation
- Choosing Your Linux Kickstart Provisioning Preparation Method
- Preparing for SCCM Provisioning
- Preparing for WIM Provisioning
- Creating Blueprints
- Space-Efficient Storage for Virtual Provisioning
- Choosing a Blueprint Scenario
- Create a Blueprint for the Basic Workflow
- Create a Blueprint for Cloning
- Create a Linked Clone Blueprint
- Create a Blueprint for Net App FlexClone Provisioning
- Create a Blueprint for WIM Provisioning
- Create a Blueprint for Linux Kickstart Provisioning
- Create a Blueprint for SCCM Provisioning
- Troubleshooting Blueprints for Clone and Linked Clone
- Publish a Blueprint
- Configuring Advanced Blueprint Settings
- Assigning Datastores to Machine Volumes
- Choosing a Storage Scenario
- Add a Datastore to a Create, Clone, or FlexClone Blueprint
- Add a Datastore to a Linked Clone Blueprint
- Add a Storage Reservation Policy to a Create, Clone, or FlexClone Blueprint
- Add a Storage Reservation Policy to a Linked Clone Blueprint
- Allow Alternative Datastores at Provisioning Time
- Reservation Policies
- Configuring Network Settings
- Enable Users to Select Datacenter Locations
- Allow Requesters to Specify Machine Host Name
- Enabling Visual Basic Scripts in Provisioning
- Add Active Directory Cleanup to a Blueprint
- Enable Machine Users to Create Snapshots
- RDP Connections
- Enable Connections Using SSH
- Assigning Datastores to Machine Volumes
- Infrastructure Organizer
- Managing Infrastructure
- Monitoring Workflows and Viewing Logs
- Appendix A: Machine Life Cycle and Workflow States
2 A fabric administrator removes all the compute resource associations to the location by editing the
locations of each associated compute resource.
Remove a Datacenter Location
Fabric administrators must remove all associations to a datacenter location before it stops displaying to
machine requesters as a datacenter location option.
Prerequisites
n
Log in to the vRealize Automation console as a fabric administrator.
n
Your system administrator removes the datacenter from the locations file. See System Administration.
Procedure
1 Select Infrastructure > Compute Resources > Compute Resources.
2 Point to a compute resource associated with the location you want to remove and click Edit.
3 Remove the datacenter location by selecting the blank option in the Locations drop-down menu.
4 Click OK.
5 Repeat this procedure to remove the location from all of your compute resources.
After the datacenter location is removed from all compute resources, it no longer appears to machine
requesters in the locations drop-down menu.
Active Directory Cleanup Plugin
The Active Directory Cleanup Plugin is a plugin that tenant administrators and business group managers
configure with a set of custom properties to specify actions to take in Active Directory when a machine is
deleted from a hypervisor.
Using the Active Directory Cleanup Plugin, you can specify the following Active Directory account actions
to occur when a machine is deleted from a hypervisor:
n
The AD account is deleted
n
The AD account is disabled
n
The AD account is renamed
n
The AD account is moved to another AD organizational unit (OU)
Gather the following information for tenant administrators and business group managers to include in their
blueprint:
n
An Active Directory account user name and password with sufficient rights to delete, disable, rename,
or move AD accounts. The user name must be in domain\username format.
n
(Optional) The name of the OU to which to move destroyed machines.
IaaS Configuration for Virtual Platforms
VMware, Inc. 57