Question about licencing guest OS's under Hyper-V

Все ответы

• 1 июля 2009 г. 12:46John Paul CookMVP, Модератор

   
  

  0

  Войдите в систему, чтобы проголосовать

  Windows Server 208 Enterprise edition allows up to four server virtual machines. Standard edition only one, Datacenter edition unlimited.
  
  What we are talking about is the right, not necessarily the ability to legally run virtualized server operating systems. Once you start talking about the actual activation process, it's the same as with physical machines. You have to have the product activation keys.
  
  Here's the best post I've seen on explaining virtualization licensing rights: http://blogs.technet.com/mattmcspirit/archive/2008/11/13/licensing-windows-server-in-a-virtual-environment.aspx
  
  Here's an explanation of activation keys: http://technet.microsoft.com/en-us/library/cc308698.aspx

  • Предложено в качестве ответаJohn Paul CookMVP, Модератор3 июля 2009 г. 12:19
  • Помечено в качестве ответаVincent HuMSFT, Модератор6 июля 2009 г. 2:44
  •  
  • Ответить
  • Цитировать

   
• 1 июля 2009 г. 16:04Xonus

   
  

  0

  Войдите в систему, чтобы проголосовать
  Licensing for Hyper-V is serious fail. I understand the need/wish to isolate the clients from the host, but you DO still have host integration services. The best way would be to have the clients licenced would be through an API to the host and get the licensing "done" through the host (which would also allow MS to force the licensing limits for the server versions, which isn't the case atm).
  
  Right now unless you have 5+ machines and can use KMS keys, its a downright nightmare with the licensing of the Hyper-V's with MAK keys, especially if you are trying to move stuff from 1 machine to another.
  
  Example: We purchased a full Datacenter 2 processor edition (to get unlimited hyper-v's), and got 12 activactions. 12. For fully licensed product with unlimited clients its downright unacceptable that you are close to being forced to use KMS - i.e. have 5+ physical servers - before licensing works. Right now the situation is that we have hit the 12 and now need to call MS every time we are adding a hyper-v client.
  
  As I said - just pure fail. My 2 cents anyway.
  • Ответить
  • Цитировать

   
• 2 июля 2009 г. 7:39Vincent HuMSFT, Модератор

   
  

  0

  Войдите в систему, чтобы проголосовать

  Hi,

   

  John has provide the most authoritative explaining of virtualization licensing from Microsoft. I will include another wonderful explaining about virtualization licensing, you can refer to:

   

  Hyper-V Licensing Explained!

  http://msmvps.com/blogs/virtualreality/archive/2009/04/01/hyper-v-licensing-explained.aspx

   

  If you want to do the further research about virtualization licensing, it is recommend you to contact Microsoft Licensing center so that you can get the most qualified pool of respondents. Thanks for your understanding.

   

  http://www.microsoft.com/licensing/contact-us.aspx

   

  NOTE: This response contains a reference to a third party World Wide Web site. Microsoft can make no representation concerning the content of these sites. Microsoft is providing this information only as a convenience to you: this is to inform you that Microsoft has not tested any software or information found on these sites and therefore cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software on the Internet.

   

   

  Best regards,

  Vincent Hu

  • Предложено в качестве ответаJohn Paul CookMVP, Модератор3 июля 2009 г. 12:19
  • Помечено в качестве ответаVincent HuMSFT, Модератор6 июля 2009 г. 2:44
  •  
  • Ответить
  • Цитировать