1 person found this helpful
I think vshpere plugin may be got from hq old version 5.7.
The future of HQ is not clear. vshpere plugin is removed from 5.8. As a component of the VMware® vCenter™ Operations Management Suite™ , HQ does not need to support VShpere any more.
Is it right?
I can't find it either...
Yes the plugin is not into the installation. The 5.7.1 works but now there's also a 5.8 version on the Marketplace.
The plugin is not needed for vcops integration I think but from what I've understood it's needed for VMWare AppHA.... probably the next version will not need the plugin anymore (I hope).
With HQ there was the ability to auto-provision the guestOS agents when the vCenter plugin had been installed. Reading the 5.8 documentation this seems to not be supported anymore? Now an install server must be created and an seperate agent.properties file must be created for the provisioning purpose.
I just wanted to check if I understood this correctly. I thought the autoprovisioning feature sounded amazing. If i'N correct, why would VMware deprecate it?
Can you explain the feature you are talking about since its news to me.
The information from the VM (OS name, Memory, CPU) were acquired by querying the vCenter Server.
The portion of the video where is shows that an agent is installed is a little ambiguous.
In that case the agent was already installed on the VM prior to the running of vSphere discovery.
In cases where we have VMs that were discovered by both having an agent installed and running vSphere discovery we will merge that information.
The vSphere Discovery does not really provide application level information.
We do have a product called VIN (vCenter Infrastructure Navigator) which can be used to install agents in your virtual environment.