SOLVED

ESU (Extended Support Update ) and SA (Software Assurance) for 2008 R2 virtual guest on VMware ESXi

%3CLINGO-SUB%20id%3D%22lingo-sub-2238848%22%20slang%3D%22en-US%22%3EESU%20(Extended%20Support%20Update%20)%20and%20SA%20(Software%20Assurance)%20for%202008%20R2%20virtual%20guest%20on%20VMware%20ESXi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2238848%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20trying%20to%20understand%20licensing%20term%20for%26nbsp%3BESU%20(Extended%20Support%20Update%20)%20and%20SA%20(Software%20Assurance)%20for%202008%20R2%20virtual%20guest%20on%20VMware%20ESXi.%20When%20I%20read%20ESU%20guide%2C%20it%20seems%20the%20licensing%20is%20to%20cover%20physical%20cores%20of%20the%20hypervisor%2C%20not%20individual%20VM.%20I%20read%20multiple%20times%2C%20but%20still%20confusing.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EESU%20guide%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fwindows-server%2Fextended-security-updates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fwindows-server%2Fextended-security-updates%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EFirst%20of%20all%20my%20environment%20is%20below%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E-%202%20ESXi%20servers%2C%2016%20Cores%2C%202%20Processors.%20Total%2032%20cores.%26nbsp%3B%3C%2FP%3E%3CP%3E-%203%20Windows%20Server%202008%20R2%2C%203%20Windows%20Server%202012%20R2.%26nbsp%3B%3C%2FP%3E%3CP%3E-%2050%25%20VM%20guests%20(3%20VMs)%20run%20on%20ESXi%20A%2C%2050%25%20on%20ESXi%20B.%3C%2FP%3E%3CP%3E-%20Through%20vCenter%2C%20failover%20vMotion%20is%20configured.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhat%20I%20understand%20for%20Microsoft%20ESU%20licensing%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E-%20ESU%20is%20core-based.%201%20license%20covers%202%20cores%20of%20'physical'%20processors%2C%20in%20this%20case%2C%20ESXi%20physical%20cores.%3C%2FP%3E%3CP%3E-%26nbsp%3BMinimum%2016%20cores(8%20licenses)%20need%20for%201%20server.%3C%2FP%3E%3CP%3E-%20After%20physical%20cores%20are%20licensed%20as%20above%2C%20two%20Windows%20Server%20virtual%20guests%20will%20be%20covered%2C%20as%20adding%20more%20guests%2C%20need%20to%20cover%20physical%20cores%20of%20the%20hypervisor%20in%20the%20same%20way(1%20physical%20core%20cover%20will%20provide%202%20Windows%20server%20guests).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhat%20I%20don't%20understand%20when%20it%20comes%20to%20virtual%20guest%20on%20VMware%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E-%20As%20ESU%20guide%20says%2C%20I%20need%20to%20cover%20the%20physical%20cores%20of%20the%20hypervisor%2C%20so%20my%20calculation%20is%20for%201%20ESXi%20server%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%201%20(ESXi)%20x%2032%20(cores)%20%2F%202%20(2%20core%20per%20license)%20%3D%2016%20licenses%3C%2FP%3E%3CP%3E-%20Then%2C%20since%20I%20have%203%20Windows%20Server%202008%20R2%20which%20need%20ESU%2C%20I%20need%20to%20cover%20one%20more%20time%20of%20ESXi's%20physical%20cores.%20Does%20below%20calculation%20looks%20correct%20if%20I%20put%20all%20Windows%20server%202008%20R2%20to%20ESXi%20A%20only%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%3CU%3E1%20(ESXi)%20x%2032%20(cores)%20%2F%202%20(2%20core%20per%20license)%20x%202%20(3%20virtual%20guests)%20%3D%2032%20licenses%20need%20to%20be%20purchased%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B-%20Then%2C%20even%20though%20I%20put%20all%203%202008%20R2%20VMs%20on%20ESXi%20A%2C%20since%20I%20configured%20vMotion%20failover%2C%20should%20I%20license%20ESXi%20B%20as%20the%20same%20way%20or%20is%20there%20any%20term%20such%20as%20%22If%20the%20number%20of%20days%20of%20VMs%20on%20a%20failover%20host%20B%20is%20not%20more%20than%2010%20days%20per%201%20year%2C%20you%20need%20to%20cover%20only%20one%20hypervisor%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20in%20advance.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2238848%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELicense%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESoftware%20Assurance%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2239404%22%20slang%3D%22en-US%22%3ERe%3A%20ESU%20(Extended%20Support%20Update%20)%20and%20SA%20(Software%20Assurance)%20for%202008%20R2%20virtual%20guest%20on%20VMware%20E%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2239404%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3Eor%20is%20there%20any%20term%20such%20as%20%22If%20the%20number%20of%20days%20of%20VMs%20on%20a%20failover%20host%20B%20is%20not%20more%20than%2010%20days%20per%201%20year%2C%20you%20need%20to%20cover%20only%20one%20hypervisor%22%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3EEach%20server%20needs%20to%20be%20licensed%20to%20cover%20the%20max%20VMs%20that%20could%20be%20on%20it%20even%20for%201%20second.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F3%2FD%2F4%2F3D42BDC2-6725-4B29-B75A-A5B04179958B%2FWindowsServer2016VirtualTech_VLBrief.pdf%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F3%2FD%2F4%2F3D42BDC2-6725-4B29-B75A-A5B04179958B%2FWindowsServer2016VirtualTech_VLBrief.pdf%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello, 

I'm trying to understand licensing term for ESU (Extended Support Update ) and SA (Software Assurance) for 2008 R2 virtual guest on VMware ESXi. When I read ESU guide, it seems the licensing is to cover physical cores of the hypervisor, not individual VM. I read multiple times, but still confusing. 

 

ESU guide: https://www.microsoft.com/en-us/windows-server/extended-security-updates

 

 

First of all my environment is below;

- 2 ESXi servers, 16 Cores, 2 Processors. Total 32 cores. 

- 3 Windows Server 2008 R2, 3 Windows Server 2012 R2. 

- 50% VM guests (3 VMs) run on ESXi A, 50% on ESXi B.

- Through vCenter, failover vMotion is configured. 

 

What I understand for Microsoft ESU licensing;

- ESU is core-based. 1 license covers 2 cores of 'physical' processors, in this case, ESXi physical cores.

- Minimum 16 cores(8 licenses) need for 1 server.

- After physical cores are licensed as above, two Windows Server virtual guests will be covered, as adding more guests, need to cover physical cores of the hypervisor in the same way(1 physical core cover will provide 2 Windows server guests).

 

What I don't understand when it comes to virtual guest on VMware;

- As ESU guide says, I need to cover the physical cores of the hypervisor, so my calculation is for 1 ESXi server;

      1 (ESXi) x 32 (cores) / 2 (2 core per license) = 16 licenses

- Then, since I have 3 Windows Server 2008 R2 which need ESU, I need to cover one more time of ESXi's physical cores. Does below calculation looks correct if I put all Windows server 2008 R2 to ESXi A only? 

     1 (ESXi) x 32 (cores) / 2 (2 core per license) x 2 (3 virtual guests) = 32 licenses need to be purchased

 - Then, even though I put all 3 2008 R2 VMs on ESXi A, since I configured vMotion failover, should I license ESXi B as the same way or is there any term such as "If the number of days of VMs on a failover host B is not more than 10 days per 1 year, you need to cover only one hypervisor"

 

Thank you in advance. 

2 Replies
best response confirmed by sungpill_han (Occasional Contributor)
Solution

or is there any term such as "If the number of days of VMs on a failover host B is not more than 10 days per 1 year, you need to cover only one hypervisor"

 


Each host needs to be licensed to cover the max VMs that could be on it even for 1 second.

http://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/WindowsServer2016V...

 

 

 

Thank you.
It's funny that I cannot even say 'I always run on this server'.

"This holds true regardless of whether you plan the workload to: Always run on a single server."