FacebookTwitterDiggGoogle BookmarksRedditTechnoratiLinkedinRSS Feed
Pin It

Install the vCAC 5.2 Agent for Windows


Convert the VM Template to a VM

First thing's first, the easiest way to call the vCAC agent is to bake it into a template that you clone other machines off of. To do this, you'll want to:

1. Go into vCenter
2. Find your template
3. Right click the template and choose "Convert to Virtual Machine"
4. Power the machine on 

Convert Template to VM

Extract the Agent

1. Copy the "GugentZip.zip" file into the VM that will be used as the VM template. This zip file can be found in the vCAC-52-Installation.zip file under the "Setup" folder

2. Extract the GugentZip file to the C drive. 

3. Confirm that there is now a C:\VRMGuestAgent folder located on the machine

Extract vCAC Agent

Install the Agent

1. Open a command prompt as the Administrator and change directories to C:\VRMGuestAgent

2. Run the following command:
{codecitation}winservice -i -h YOUR_VCAC_SERVERFQDN:443 -p ssl{/codecitation}

Install vCAC Agent

Make Edit to InstallSoftware.js

There's currently an issue with the InstallSoftware.js file that comes in the GugentAgent install. To fix this:

1. Navigate to C:\VRMGuestAgent\site\InstallSoftware in your Windows Explorer and edit the installsoftware.js file

2. Where it says "var p = this.shell.Exec(cmd);" replace it with this line:
{codecitation}var p = this.shell.Run(cmd);{/codecitation}

Update InstallSoftware file

Copy Script onto Machine 

If you're going to be running a script locally, copy it to a convenient location 


Convert Your VM Back to a Template

In vSphere, power down the VM and then right click the virtual machine and go to template > convert to template

Depending on how long you took to do all of the things above, you may have to run an inventory scan inside vCAC to get the template to show up in your list of clone-able templates when creating a blueprint. Make sure that you use this template in your vCAC blueprint.

Convert Machine to Template

Build the Properties

You can do this step directly on a blueprint, or you can create a build profile so that the set of properties can be used on many blueprints.

Enter the following properties. descriptions of what should be entered are right after the property name:

VirtualMachine.Admin.UseGuestAgent - this should be set to "true" (without quotes) to tell the agent that you will be making calls to it
VirtualMachine.Customize.WaitComplete - set this to be "true" (without quotes) to have vCAC wait for the scripts to finish before moving on down the rest of the life cycle
VirtualMachine.Software0.Name - enter a friendly name for your script that you want to run. If you want to run more than one script, create new properties with sequential numbers (ex: VirtualMachine.Software0.Name, VirtualMachine.Software1.Name, etc).
VirtualMachine.Software0.ScriptPath - enter the location and file name of the script that you want to run. If you want to run more than one script, create new properties with sequential numbers (ex: VirtualMachine.Software0.ScriptPath, VirtualMachine.Software1.ScriptPath, etc)
VirtualMachine.Admin.CustomizeGuestOSDelay - This is optional. Use this and set it if your sysprep runs scripts and thus takes longer to get to the point where the agent would run 

Blueprint Properties in vCAC

Passing Variables into Properties

If you want to pass a property into the ScriptPath property, or any of the other ones, you can do so by putting curly brackets around the property name that you want to call. An example would be that if I had a custom parameter named ScriptFile.Custom and I wanted to call it into the VirtualMachine.Software0.ScriptPath property, I could do so by setting the value to something like:


You can see I've done this in the last screen shot with the repo.path property