vRealize 7 Application Services – Windows Agent Install

I am new to Application Services, and had some trouble successfully preparing the template. To prepare the template, a few pieces of software (including an agent) have to be installed in the template for vRA to be able to interact with the VM once it is deployed.

Here are a few resources I found that helped me successfully create/deploy a blueprint with a simple software component.

Preparing the Template

  1. The Virtualization Team has a great article (vRealize 7 Automation Bootstrap Installation) on preparing the template.
    • NOTE: There is a note in the article that threw me off. I read it as if I didn’t need the Guagent install because I am using a certain license. I was wrong, and without pulling down the ‘GuestAgentInstall_64.exe’ file from the vRA server, I wasn’t able to execute any of the PowerShell actions in the Software Component.
  2. Extendingclouds.com created a great PowerShell script to prepare the template . Overview of the script can be found here (PrePare_vra_template), and you can snag the script from the VMware Developer Center.
  3. Check out this article from vmtocloud.com for getting started with the software component properties (Application Authoring Deep Dive)

What to do if it is still not working:

Troubleshooting this can be extremely time-consuming and frustrating because it has to go through the entire provisioning process every time you test. Furthermore, after the machine is provisioned the software component magic begins. However, if there is a problem, vRA waits 30 minutes before it errors out and disposes of the VM.

Below are a few places to look to see if the agent is working. If it’s not, I don’t wait. I go on troubleshooting and let the request (eventually) fail.

  1. Check out the ‘c:\opt\vmware-appdirector\agent\logs\agent_bootstrap.txt’ log file to see whats going on. Because I didn’t have the Guest agent installed, I saw the following repeated in the file.

    I also noticed, ‘logs’ was the only directory that existed in the ‘c:\opt\vmware-appdirector\agent’ folder until the Agent was working correctly.

  2. Reduce the complexity of what you are trying to run (PowerShell in my case), and validate the agent is working to begin with. I used a simple PowerShell Script that would simply write the value of a property to the ‘c:\temp\’
    • Create a property in the software component called ‘test_property1

    • Create an action to log the value of the property
    • Once the machine is deployed, verify the vraAgentTest.log we created in the action exists.
  3. .NET 3.5 install. I have seen a few articles that show .NET is required on the template to get this to work.

Thanks!

Comments 1

  1. ******************Check out the ‘c:\opt\vmware-appdirector\agent\logs\agent_bootstrap.txt’ log file to see whats going on. Because I didn’t have the Guest agent installed, I saw the following repeated in the file.

    I also noticed, ‘logs’ was the only directory that existed in the ‘c:\opt\vmware-appdirector\agent’ folder until the Agent was working correctly.****************

    -> I am getting the same message, even after re-installing Guest Agent,
    -> vcacguestagent service is verified to be running before i turn the Virtual machine into template.

    What did you do to fix this issue

Leave a Reply

Your email address will not be published. Required fields are marked *

*