Provision Windows & Ubuntu VM under different OU path in Active Directory for Same Project

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Provisioning of VMs is failing due to a conflict between the Active Directory (AD) Organizational Unit (OU) path defined at the project level and the OU path specified within the Cloud Template.

Provisioning fails with similar Error:

[ad-integration] Active Directory Action MOVE_MACHINE for request ######## failed with errors:[ad-integration]Failed to deserialize outputs of [action: #######][action-run: #############], [outputs {error=ou_validation_failed, status=failure, actionType=MOVE_MACHINE}]

 

 

Environment

VMware Aria Automation 8.18

Resolution

Workaround

You can add a property called FinalRelativeDN to blueprints to change the OU for Active Directory deployments.

Currently the recommendation is to use the finalRelativeDN field in YAML script .

You can add a property called FinalRelativeDN to blueprints to change the OU for Active Directory deployments. This property enables you to specify the OU to use with an Active Directory deployment.

 

formatVersion: 1
inputs: {}
resources:
Cloud_vSphere_Machine_1:
 type: Cloud.vSphere.Machine
 properties:
   image: CenOS8
   flavor: tiny
   activeDirectory:
     finalRelativeDN: ou=test
     securityGroup: TestSecurityGroup