Licensing problem fixed

On January 19, 2009, in news, by

Read this blog post today and went… uh…okay…  I didn’t know I had that problem:

A lot has been said and written about Microsoft Licensing policy related to CALs required to access non Windows Server 2008 VMs on Microsoft Server 2008 Server Hyper – V.

Problem Scenario

If you move your physical Windows Server 2003 Operating System Environments (OSE) to run as virtual machines hosted by Windows Server 2008 Hyper-V,  Can i use my existing server 2003 CALs?

No, as the virtual instance of Server 2003 running on Windows Server 2008 instance you need to have Server 2008 CALs and not server 2003 CALs.

Those who have Microsoft Software Assurance license can upgrade their licenses to Server 2008

Problem Solved

Microsoft has changed its licensing policy relating to CALs accessing Virtual Machines on Server 2008 Hyper V.

Windows Server 2008 CALs are no longer required if you are using Windows Server 2008 solely as a virtualization host. The only exception to this is if you are running Windows Server 2008 virtual machines, which would require Windows Server 2008 CALs.

————-

I do know that I either need to cal license my Member server that is a 2k8 box by May of 2009, or migrate up to SBS 2008 in order to be legal on the ability to have the SBS cal cover the licensing of the member server box, but I didn’t know that I would need to worry about the 2k3 licensing of the virtualized 2k3 box that is sitting underneath my HyperV server.

Good to know that a licensing problem I didn’t know I had got fixed to that I don’t have it anymore.

 

Comments are closed.