Set the following properties for the new Connection instance:
Enter the web URL of the SDK of the vCenter server (for example, https://<vCenterServerName>/sdk).
Note: This name should match the VMware vCenter server name registered in BMC Server Automation.
Enter the name of an administrator of VMware vCenter, or another user with required privileges.
Enter the password of the user that is mentioned in the above property.
Hi M. Ragland,
The VCenter where we are connecting is a physical Server with RSCD Agent installed. The information that you are referring is related with a VMWare vcenter Virtual Appliance through Agentless connection so it´s not valid for us. Anyhow, as you could see, the connection is established with the Vcenter and we retrieved information from it but as I said if the Templates have the same name in all the EXS Cluster, this information field has the same value for all the templates.
Mark in yellow the propriety field with incorrect information when the Template has the same name in several ones.
it doesn't seem like it's handling the duplicated template names properly, i'd open a support ticket.
1 of 1 people found this helpful
I just found a workaround about the Template cluster information when we select it to create a VGPJ. We can select whichever Templace that is allocated on the Vcenter and customice the job with the proper information about the cluster and the rest of the custom OS parameters.
We can select the Target for Virtual Guest* Value from the vcenter on BladeLogic Agent inventory object for vmware:
So the job allocates the information on the correct VMware Cluster and the job allocates the VM on the correct ESX site.
Hope that this information could help for future queries.