I'm trying to install the vCAC Log Insight Content Pack and tried to download the "vCAC 6.0 Content Pack for Log Insight Setup" document. It asks me to register, which I already did. It's been over a day and I'm not able to receive the activation email to enable the download of this document. I'm wondering if anyone is experiencing the same issue? Or, better yet, maybe make the document public?
Hey Rick, Solution Exchange requests should be processed within three business days. The document is just a formalization of this blog post so feel free to reference this in the meantime: vCAC remote logging | SFlanders.net
Hey Rick, Solution Exchange requests should be processed within three business days. The document is just a formalization of this blog post so feel free to reference this in the meantime: vCAC remote logging | SFlanders.net
Thank you for your quick response. I actually found your blog posting and appreciate the helpful syslog component configuration lines and registry entries. I found them very useful so far, however I did run into some confusion with the IaaS registry modifications. I have a distributed deployment and the registry lines deal with an all-in-one IaaS scenario. Instead of filtering the lines out, I decided to take a snap and import all lines. I'm thinking the registry lines regarding components that don't exist will be ignored. I tried this on the IIS server with only the Model Manager to see if this theory pans out. However, I'm currently getting very limited dashboard metrics for the IaaS view. I suspect it's because I only have one server configured out of the distributed deployment. I'm going to import the registry file on all other components today and see if the IaaS dashboard view lights up.
I envision that the only way to efficiently troubleshoot vCAC in a timely manner is with Log Insight and the vCAC content pack. I see a tremendous value in this technology.
On another note, I'm not sure what needs to happen to activate a registration from Solution Exchange but it seams a bit inefficient.
Hey Rick,
Yes, the registry file is for an all-in-one solution, but it also works fine in a distributed environment as non-relevant files will be ignored (I will add a note to my blog post). Let me know how it works out!
As for Solution Exchange, send them an email at vsxalliance@vmware.com.
