Now we have our tenant created, identity source added and roles assigned we can create a fabric group to assign access to the underlying computer resources. The first step is to change the context of which we are connecting to the vRealize Automation system, this involves connecting to our newly created tenant instead …

In my previous post, I covered the creation of a tenant using the CloudClient but before you can authenticate to the tenant you need to first assign the Identity Store that you want to use for assigning access rights, then you need to assign access for the two tenant roles 'Tenant Admin' and 'Infrastructure Admin'. …

In this article I'm going to walk through the process of using CloudClient to create and delete tenants from vRealize Automation. I personally use this procedure to setup a consistent and repeatable environment when doing internal testing or building demo environments for developing our professional services offerings. …

Before you can start using the CloudClient to perform command-line actions against your vRealize Automation (vRA) platform you have to authenticate to it. Whilst complete documentation is provided with the CloudClient download it does lack some examples of how to use the syntax, this post and others I'm yet to write …

Do you have the need for performing multiple tasks in an efficient manner, tired of using the web-based GUI interface to perform common tasks in vRealize Automation? Help is at hand in the shape of the vRealize CloudClient. vRealize CloudClient is a command–line utility that provides simplified command line access to …

Prior to the release of vCloud Automation Center (vCAC) v5.2 there was no awareness or understanding of virtual machines protected through vCenter Site Recovery Manager. With the introduction of v5.2, VMware provided enhanced integration so that vCAC would correctly discover the relationship between the primary and …

Ever wanted to limit the number of VMs being requested via the Self Service portal per request. I had a customer who wanted to do this recently, their use case was to prevent user input mistakes when requesting services. The default value in vCloud Automation Center (vCAC) 5.x is 999. Just to be clear this is not …

To help manage your vCloud Automation Center (vCAC) implementation and the resources on which it depends, vCAC by default places limits on the number of concurrent instances of two particularly resource-intensive operations, machine provisioning and data collection. During a recent vCloud Suite implementation this …