VMTN

ferdis,

try exiting Powershell and try again.

Hi digitlman,

thanks for response but no sucess. It just reports same as in 04 05 screenshots from my original response. Only difference is that it repeats more sentences which are the same:

Row 31 char:56 "A parameter cannot be found that matches parameter name 'Property' "

Hi

I know this doesn't answer your initial question, but you may want to try a different method.  The results of the below script will pull from your license manager, not powered on guests (what is currently in use). Both methods are great, but for me, I like to see what is currently in use.

http://www.virtu-al.net/2011/07/14/vsphere-5-license-entitlements/

Hi Troy,

I run License Validator on two VMware PowerCLI v 4.1 machines against two vCenter 4.1 but it generated a lot of errors. So no success again. It generated report with no data.

Thanks.

Frantisek

yes, I see you already stated Alans code errors too.  I guess I should read the thread a bit better.  I'm no PowerShell guru, just barely a novice, but do you have the most recent version of PowerCLI

> Get-PowerCLIVersion

PowerCLI Version
----------------
   VMware vSphere PowerCLI 4.1 U1 build 332441
---------------
Snapin Versions
---------------
   VMWare vSphere PowerCLI 4.1 U1 build 332441

Hi,

yes I have latest VMware PowerCLI:

VMware vSphere PowerCLI 4.1 U1 build 332441

I got more vCenters. One with 4.1 258902 release, and others with 4.1 U1 345043 release.

All vCenters are Windows 2008.

VMware PowerCLI machine one is Windows XP SP3.

VMware PowerCLI machine two is Windows Server 2003 SP2.

It looks as if you are running PowerShell v1.

The function requires PowerShell v2.

Do you have a W7 or W2K8R2 box where you can try the script ?

Those have PowerShell v2 by default.

I'll tap out because I don't want to lead you down a road of no return.  I'm sure the PowerCLI gurus will come to the rescue soon.

You may also want to open a new thread in the VMware vSphere™ PowerCLI Community to get a bit better exposure.

You are right!!!

Problem was that I had PowerShell v1 on my XP and Win 2003 machines.

Now after upgrade to PowerShell v2 everything is going well.

Luc, THANK YOU SO MUCH!!!!

You know that feeling when someone help you to move forward? YOU HELP ME SO!!!!!!

Once again, big thank you!!!

If you guys are having problems with the scripts and just want the numbers then you can run this single cmdlet after connecting to vCenter to pull the current configured vRAM amount.

>Get-VM | Measure-Object -Property MemoryMB -Sum

It will return the total configured memory in MB, so divide by 1000 to change to GB

slaclair wrote:

 

>Get-VM | Measure-Object -Property MemoryMB -Sum

 

It will return the total configured memory in MB, so divide by 1000 to change to GB

Nice and simple... slaclair wins.  Thanks!

You can expand that simple line into

Get-VM | where {$_.PowerState -eq "PoweredOn"} | Measure-Object -Property MemoryMB -Sum

That way you'll see what actually uses vRAM pool memory.

In this last environment I tested, they are not going to be impacted by the licensing change..however they are horribly horribly underutilized and overbuilt.

they have 10-esx hosts with 48-96gb of RAM in them and they are running 125VM's with 300GB allocated...

So..what it comes down to, is..if you built your vmware environment using the Microsoft hyper-v design of a 1-2 or 1-5 consolidation ratio you will be fine...however most of us have paid for the vmware design..which is consolidate the living hell out of things and use the power of the product to oversubscribe much higher since it does it so well.  We are the ones who will get screwed.

Everyone else who threw way more money and licenses at their pool early on without needing to, save money in the future...those of us who scrimped and got the biggest ROI on our servers now have to pay the piper...

I Still believe the vRAM OR pCPU model is the correct answer..not both...

Without sharing specific numbers, I can tell you that in our environment that we've just upgraded to new hardware AND ENT+ licensing to be able to use that new hardware, we will be ok initially as we have about 1.7T of vRAM entitlement headroom.  My account team will be eager to say "see, you'll be ok".  But that's not acceptable to me because we're only 20% utilized right now and we invested alot of money to be able to use the infrastructure for the next year or two.

If I wanted to get to a conservative 65% utilization, I'll have to buy at least an additional 80 ENT+ licenses as our utilization increases under the current entitlment numbers.

Without re-posting my thoughts on this, check this out if you like.  http://communities.vmware.com/message/1792658#1792658

Have a good weekend everyone!

I have four servers, each dual socket, 256 GB with Enterprise Plus licensing.  I an currently using 340 GB vRAM which comes out to about 7.1 licenses.  I own 8 so according to VMware I should be perfectly happy. I purchased the servers 12 months ago and sized them to allow for at least four years of growth.  Thanks to the new licensing I've just about reached that point already.

I still have several physical servers that I would like to migrate.  Those servers have 160 GB of memory.  I know I can cut down on some of that but most of them are configured as required by the software vendor.  Whenever we have an issue I'll have to boost it back up to the vendor requirements and taking it back down will be a losing battle.  I'll take a rough stab at a number and reduce the memory by 25% and go with 120 GB as the vRam needed for these servers.  340 + 120 =  460.  This will require me to purchase 2 more licenses.  I'd need to get the required vRAM down to 92 GB in order to get the extra license down to one.

VMware response seems to be that all I need to do is right size my servers and  I'll be fine.  I actually have software that monitors my VMs and makes sizing recommendations.  According to that software I need to add about 8 GB of memory overall to my existing servers to right size them.  In addition several servers are being used for projects that are in the development stage.  They are sized anywhere from 25% to 50% of what is recommended by the vendors so I am sure I'll need to add memory to them when they go into production.

Doing the math, to utilize the memory I have and allowing for one server offline for HA, 1024 - 256 = 768, I need 16 licenses or an additional 8 licenses.  This is using a 1:1 ratio of pRAM to vRAM, in actual practice I should be able to get more than 768 GB of vRAM from 768 GB of pRAM so the number is probably more like 10 to 12 licenses.

So yes, according to the script I'm fine under the new licensing scheme and I'm in the 90% to 95% of users that aren't affected by the new licensing.  Life is good.