Category Archives: 6.2

Finding where a build profile is used in vRA

Keeping track and documenting relationships between build profiles and blueprints is a very important aspect of keeping your vRA deployment organized and easy to maintain.

But is very tedious keep track of build profiles and blueprint relationships. And can even be difficult for some activities:

  • When yo try to delete a build profile you may end up with this message, asking yourself in which blueprints it is actually referenced:

  • when trying to document your blueprint you will struggle with this selector window that only let you see 5 build profiles at a time:

All those informations are stored in the IaaS DB, so here are two short SQL queries that you can run against the vRA IaaS SQL server DB to help speeding up things:

  • Find where a build profile is referenced (the WHERE clause is optional and given as example):
SELECT GP.ProfileName, VMT.VirtualMachineTemplateName
FROM
		VirtualMachineTemplate AS VMT
	JOIN
		TemplateToGlobalProfiles AS TG
	ON TG.VirtualMachineTemplateID = VMT.VirtualMachineTemplateID
    JOIN
		GlobalProfiles AS GP
	ON TG.GlobalProfileID = GP.GlobalProfileID
 WHERE GP.ProfileName = 'vra.gugent.enable'

  • Print a human readable list of the build profiles attached to each blueprint:
SELECT VMT.VirtualMachineTemplateName ,GP.ProfileName
FROM	VirtualMachineTemplate AS VMT
	JOIN
	TemplateToGlobalProfiles AS TG
	ON TG.VirtualMachineTemplateID = VMT.VirtualMachineTemplateID
	JOIN	GlobalProfiles AS GP
	ON TG.GlobalProfileID = GP.GlobalProfileID
ORDER BY VMT . VirtualMachineTemplateName

 

You can even copy the data to excel (or create a data source) and build a nice PivotTable:

vRA 6.2 installation gotchas

Here is a list of the tricks and tips I found deploying vRA 6.2:

  • Java

This one is very nice. Java 1.8 prevent Liquibase from working using SSL (credits). The easiest workaround is to install Java 1.7 instead.
Don’t forget to create the JAVA_HOME environment variable using short names because again vRA installer is not confortable with the quotes in the path.

  • Internet explorer

I was working at a customer where IE is stripped out from Windows (even the explore.exe file is removed). Nevertheless if you don’t disable IESC for admin this will prevent the installer to reach the repository. So disable it (server manager > local server > IE Enhanced Security Configuration).

Setting screen:

  • Simple Install

When you try to deploy a simple install be aware that you cannot control the following elements:
– Installation path of vRA, everything will be deployed in “C:\Program Files (x86)\VMware\vCAC”
– Certifiacte to use, vRA installer will generate a self-signed one. You can then change it after the install following the procedure on page 126 of vrealize automation 62 installation and configuration PDF.

  • Custom install

When you choose the custom install and want to deploy everything on a single machine you must deploy all core components in one pass. I tried to deploy database, model manager data and web site then later Manager and the installer just told me that the vCAC app pool already exist and refused to go further. I had to reinstall everything from scratch including dropping vCAC DB.