vRealize Automation 7.2 – Fabric and Business Groups

Under Endpoints, select Fabric Groups

Enter a name for the Fabric Group and select a Fabric Administrator. If you don’t see any resources, re-check your vCenter Endpoint and ensure the configuration is correct.

Now you essentially given more permissions to said admin – logout – time for a drink or wait for 2 minutes whilst looking into the nowhere.

Next we need to create a Machine Prefix. Whilst not REALLY needed (you can overwrite hostnames via custom property) it is still a requirement when creating a Business Group

Browse to Infrastructure > Administration > Machine Prefixes

Note: If you do not see the option, then log back out, wait 5 minutes and then back in again. It means the permissions aren’t ‘right’ yet and may still need a bit to sync (Fabric Admin permissions that is)

Here I add two prefixes, one for Windows and one for Linux

Now I want that every VM deployed via vRA is being deployed into a particular OU in Active Directory.

Here you can see I have the OU vRA7 machines

Now navigate to Administration > Active Directory Policy

Click New

Now enter an ID – select the newly created AD Endpoint and type in the Domain. Also enter the OU DN

Hopefully you won’t receive an error

Now navigate to Users & Groups > Business Groups

Click New

Enter a name, email address and select the newly created AD Policy

Enter the AD groups for the appropriate rules. Note: Support User means that someone can submit requests on BEHALF of someone. Here I don’t need that role.

The majority of VMs deployed in my environment are Linux based – so this is the default prefix I select. Active Directory Container is only needed for WIM provisioning

That is it.

Next will be Reservations and Reservation Policies