Small Things: vCAC 6.1 – "Data Collection" catalog entry

For anyone that does template configuration changes in vCAC can attest to how big of a pain it is to reconfigure the agents, shut down the machine, snapshot, browse the menu structure to where you force data collection, click collect data for all the items, browse to the blueprint config and wait for it to complete.    Well, hopefully this tip can speed that up just a little, or at least make it less of a headache for you.

vCAC 6.1 comes with a ton of vCO workflows out of the box.  One that caught my eye is “Force data collection”.

Snip20140919_22

 

Adding this workflow as a catalog item is a breeze under Advanced Services – Service Blueprints.  When complete it will show up like any other service or template:

Snip20140919_25

 

And does its job quite well:

Snip20140919_30

 

One warning, you will want to set a constant value for the one question it will prompt for in this workflow.   Edit the blueprint as such:

Snip20140919_26

 

And choose your IaaS (windows) server:

Snip20140919_27

 

I quickly installed a fresh new instance of vCAC & IaaS today, and not sure if it was an error during install or not but at first mine didn’t show any hosts here in the above screen shot.   I had to go into vCO with the client and run this workflow to add it.  Your results may vary.

Snip20140919_31

 

EDIT Sept 22 2014:   I wasn’t clear about where to find this workflow.  It’s found within these folders:

Orchestrator
Library
vCloud Automation Center
Infrastructure Administration
Extensibility
> Force Data Collection

Tagged , , ,

6 thoughts on “Small Things: vCAC 6.1 – "Data Collection" catalog entry

  1. Fernando says:

    Hi,
    I’m trying add IaaS but not working, return error: “Unauthorized: Access is denied due to invalid credentials”.

    Credentials is ok.
    Host: https://

    Can you help me?
    Tks.

  2. Oxana says:

    Hello,

    I’m trying to connect vCAC appliance to vCAC identity appliance. But vCAC appliance returns error – Error updating SSO configuration. SSL certificates are self-signed with fqdn of appliances in common name.

    Can you help me?
    Thanks

    • jasper9 says:

      Are you using the newest version? 6.1 or 6.0? Be sure you don’t put a port number in the hostname box in the appliance config for SSO like we had to in 6.0. That’s a common mistake now.

      • Oxana says:

        Yes, I’m using the newest version 6.1.
        No, i don’t put a port number in the hostname box.
        I’ve been redeployed appliances several times already. Same mistake…
        I try vCenter SSO instead of vCAC IA. Same mistake again.

  3. […] you’re ready to shut it down, take a snapshot, start data collection, and update your […]

Leave a Reply

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