Licenciamiento Windows Server 2016 Data Center

%3CLINGO-SUB%20id%3D%22lingo-sub-1407314%22%20slang%3D%22es-ES%22%3EWindows%20Server%202016%20Data%20Center%20License%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1407314%22%20slang%3D%22es-ES%22%3E%3CP%3EGood%20morning%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20appreciate%20your%20help%20in%20clarifying%20the%20next%20situation%20I%20have%20in%20a%20virtualization%20scheme%20on%20a%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20currently%20have%20a%20Physical%20Server%20(HOST)%20with%204%20virtual%20machines%20via%20HYPER-V.%20I%20have%20HOST%20configured%20with%20the%20Windows%20Server%202016%20Data%20Center%20operating%20system%20and%20on%20virtual%20machines%3A%203%20with%20Windows%20Server%202016%20Standard%20and%201%20with%20Windows%20Server%202012%2C%20my%20concern%20is%20as%20follows%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Host%20is%20properly%20licensed%20by%20the%20number%20of%20cores%20that%20the%20server%20processor%20has%2C%20however%20I%20want%20to%20know%20if%20the%20operating%20systems%20of%20the%20virtual%20machines%2C%20should%20I%20acquire%20the%20licenses%3F%20or%20if%20with%20the%20DataCenter%20version%20features%20that%20allow%20OSEs%2F%20Hyper-V%20Containers%20Unlimited%20am%20covering%20these%20licenses%20for%20virtual%20machines%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20so%20much%20for%20your%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1407314%22%20slang%3D%22es-ES%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1407342%22%20slang%3D%22en-US%22%3ERe%3A%20Licenciamiento%20Windows%20Server%202016%20Data%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1407342%22%20slang%3D%22en-US%22%3E%3CP%3EA%202016%20DataCenter%20host%20can%20activate%202016%20and%202012%20R2%20guests%20via%20AVMA%20keys%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started-19%2Fvm-activation-19%23system-requirements%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started-19%2Fvm-activation-19%23system-requirements%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E(please%20don't%20forget%20to%20mark%20helpful%20replies)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Buenos días,

 

Agradezco de su ayuda en aclararme la siguiente situación que tengo en un esquema de virtualización en un cliente.

 

Actualmente tengo un Servidor físico (HOST) con 4 maquinas virtuales a través de HYPER-V. El HOST lo tengo configurado con el sistema operativo Windows Server 2016 Data Center y sobre las maquinas virtuales: 3 con Windows Server 2016 Standard y 1 con Windows Server 2012, mi inquietud es la siguiente:

 

El Host se encuentra licenciado adecuadamente por el numero de núcleos que tiene el procesador del servidor, sin embargo quiero saber si los sistemas operativos de las maquinas virtuales, debo adquirir las licencias? o si con la características de la versión DataCenter que permite OSEs/ Hyper-V Containers Unlimited estoy cubriendo estas licencias de las maquinas virtuales?

 

Muchas gracias por su ayuda.

1 Reply
Highlighted

A 2016 DataCenter host can activate 2016 and 2012 R2 guests via AVMA keys

 

https://docs.microsoft.com/en-us/windows-server/get-started-19/vm-activation-19#system-requirements

 

(please don't forget to mark helpful replies)