Wow! This new post by the competition team at VMware is really interesting.
Here’s the scenario: Say someone’s got existing Windows Server 2003 licenses (non-OEM versions) and CALs. He wants to use these licenses and CALs to run a Windows Server 2003 virtual machine. Seems pretty straight forward – as a 2003 CAL is being used to access a Windows Server 2003 environment – and a good way to save money since he’s already paid for the Windows Server 2003 licenses and CALs – right?
Make sure to read the whole post at the source. It’s interesting because there’s a huge, hidden cost to using Hyper-V for shops that aren’t upgrading to Windows Server 2008 right now. I know, some people are going to comment that everyone is upgrading already. No so. As a matter of fact I was just with a customer in Ohio today that is just beginning the process of upgrading from Windows Server 2000 to Windows Server 2003. No, that wasn’t a typo. This is a pretty major customer out there too – not your mom and pop shop.
It will be interesting to see how Microsoft talks its way out of this one. Even if it decides to change it’s CAL model that’s going to be pretty complex. If anyone does have some constructive comments on ways to get around this CAL upgrade requirement I’d love to hear about it. Just drop your info in the comments for all of the readers to hear.
UPDATE (January 18, 2008) – Microsoft has recently changed their licensing structure so you don’t need Windows Server 2008 CALs anymore if you’re accessing non-Windows Server 2008 VMs. Read more here.
