Microsoft Active Directory

Configure and use the OneFuse Microsoft Active Directory module with VMware vRealize Automation 7.6

  4 minute read  

To learn more about this OneFuse module, refer to Microsoft Active Directory.

Prerequisites

  1. Configure OneFuse Property Set(s) and OneFuse Module Policies.
  2. Run OneFuse Configuration per vRA Tenant.
  3. Review the OneFuse Modules overview for vRealize Automation 7.6.
  4. Create a new vRA Blueprint (if none exist) or determine which existing Blueprint(s) will utilize this OneFuse Module.

Configure the Blueprint

  1. Know the name of the OneFuse Endpoint created via OneFuse Configuration.
  2. Determine which OneFuse Microsoft Active Directory Policy to run for this Blueprint.
  3. Update the Blueprint to add in the necessary vRA Property to invoke a OneFuse Microsoft Active Directory Policy.
  4. Deploy the Blueprint to provision a vRA Deployment and create a computer account in Microsoft Active Directory.
  5. Destroy the vRA Deployment to remove the computer account from Microsoft Active Directory.

Update the Blueprint

  1. Log in to the vRA Tenant
  2. Select the Design tab from the top menu bar
  3. Select the Blueprints tab from the left menu
  4. Edit the Blueprint and perform the below:

Add in necessary vRA property

The following vRA Property needs to be added to the Blueprint’s Properties > Custom Properties section under the Resource(s) of interest.

Call a Microsoft Active Directory Policy:

Property Name Format Property Value Format
OneFuse_ADPolicy <OneFuse Endpoint Name> : <Microsoft AD Policy Name>

Example vRA Custom Property (in key: value pair format):

# -- Property Value
# <OneFuse Endpoint Name>  is onefuse
# <Microsoft Active Directory Policy Name> is global

OneFuse_ADPolicy: onefuse:global
Additional helpful vRA properties

Purpose: Relate OneFuse Policy executions from different OneFuse Modules together with a Tracking ID.

Property Value format
OneFuse_Tracking_Id A GUID (globally unique identifier) that links OneFuse Policy Executions and the resulting Managed Objects together for a given resource on a deployment. The first OneFuse Module Policy execution will populate this vRA property and it will be passed into other OneFuse Modules automatically. Learn more about OneFuse Tracking ID.

Purpose: Reference a specific NIC’s values to get hostname, IP address, etc.

Property format Example
OneFuse_VmNic<#>.<value> See examples below

Replace <#> with a number from 0 to 9, one for each NIC.

Replace <value> with an appropriate key: dnsSuffix, fqdn, gateway, hostname, ipAddress, macAddress, netmask, network, subnet, target

Examples:

  • OneFuse_VmNic0.dnsSuffix
  • OneFuse_VmNic0.fqdn
  • OneFuse_VmNic0.hostname
  • OneFuse_VmNic0.ipAddress
  • OneFuse_VmNic0.target: when DNS Suffix is provided, will be the FQDN; otherwise, will be the hostname (without domain).
Custom property placement methods

Influence Custom Properties for Resources using different methods:

Method Description
Basic Add a Custom Property to the vSphere machine on the blueprint canvas, or to the blueprint layer itself.
Advanced 1 Add a Custom Property to an existing or new vRA Property Group.
Advanced 2 Add a Custom Property to a more global level, such as vCenter Endpoint (to run on all deployments) and/or a Reservation (to run on all deployments using that reservation), etc.

Learn more: Understanding Custom Properties Precedence

Provision

Deploy a Blueprint with OneFuse Microsoft Active Directory Policy configured. A computer account will register in Microsoft Active Directory.

Outputs

The following vRA Properties will exist on the Deployment.

Property Name Property Value
OneFuse_AD JSON string of OneFuse Microsoft Active Directory Managed Object
OneFuse_AD_State build or final depending on the state.

Deprovision

Destroy an existing deployment with OneFuse Microsoft Active Directory Policy configured. The computer account will be removed from Microsoft Active Directory.

vRA EBS

EBS Execution Subscription State EBS Priority EBS Name
Provision
BuildingPre Early 1500 OneFuse_Provision_AD
ProvisionedPre Early 1500 OneFuse_Move_OU_AD
Deprovision
MachineDisposingPost - 1200 OneFuse_De-Provision_AD

Troubleshooting

Troubleshoot in vRealize Orchestrator.

  1. Log in to vRealize Orchestrator.
  2. Turn on Verbose Logging and try again to see additional log messages in vRO Workflows:
    • Select Library > Workflows from the left menu
    • Go to: OneFuse > AD > vRA7 to find corresponding workflow runs and view logs
    • Optionally, run the workflows in the Manual folder to manually test
  3. Optionally, configure timeouts for EBS and/or Configure timeouts for OneFuse modules.

Additional resources: