I know many of you have been waiting on this so I figured I would report it is available. You can find the official vSphere License Advisor on here. I know many have used Alan’s script, and some couldn’t use it because it didn’t support VI3. The vSphere License Advisor will work in environments with Virtual Infrastructure 3.5, vSphere 4.0 and vSphere 4.1 so pick it up and run it.
Useful !
Seems to have some fairly major bugs:
We have in excess of 1400x VMs, the tool only reports 174(!) in the GUI but in the export to CSV function the numbers appears correct.
Host licensing: VLA reports 74 licenses in total, with 74 deployed yet we have 238 licenses deployed and in use. We still haves some VI3 which is being deppreciated for vSphere 4.1.1.
Looking again at the CSV export, it seems to only count the “vSphere 4″ licenses and ignore VI3.
@Duncan, my email address is enclosed in this feedback, happy for you to send onto the dev/product team if needed be? Very useful tool if it would report correctly.
Thanks
Neil,
I know my script is not official but it has some logging in it, I just wondered, do you get the correct results when you run my script ? http://www.virtu-al.net/2011/08/03/vsphere-5-license-entitlement-changes
Neil,
Did you see the statement on the License Advisor site which states….
“The tool will work in environments with Virtual Infrastructure 3.5, vSphere 4.0 and vSphere 4.1.
Environments with vCenter Server 4.x managing Virtual Infrastructure 3.5 hosts are not supported with this tool.”
http://www.vmware.com/products/datacenter-virtualization/vsphere/upgrade-center/vsphere-licensing-advisor.html
Hi Alan (sorry I have been on vacation so late in replying).
I now see the statement from VMware re. vCenter 4.1 managing ESX 3.5 host is not supported, this is really lame. Can someone feed this back to the product team to have this functionality added? This seems a major oversight, if nothing else the tool should state x ESX 3.5 hosts have been excluded rather than reporting what looks like incorrect results.
My just 2p worth…!
Thanks, Neil
Have to agree with Neil – just ran the tool against 2 of our vCenter servers, and it’s chopping a few hundred VMs from our totals. Have to say I’m not surprised – the QA process at VMware has been questionable for some time now which is a real shame.
I downloaded yesterday. I’m going to try the tool today. Shame about the bugs if that is true.
Jas
Very handy, large font, % of entitled being used. I’m sure it will take many people by surprise when they see the number (given they didn’t already figure it out)
Afaik, the tool only show the actual allocated vRAM. Is there a tool that pulls information out of the VC DB to see, what’s the year to year average?
This statistic is not gathered, unless something isn’t working right in my environment.
None of the host memory metrics match the allocated vRAM on my hosts. I have 192,512MB assigned to VMs on a host – but no memory metric matches this.
Unfortunately for me I can’t even get the tool to authenticate with our vCenter server … no matter what credentials I try I get told they are invalid (yet they work fine when running the vSphere Client to connect to vCenter).
… and now, several days later, its working … weird … using the same credentials …