Posted: 12/29/2007 7:51:04 AM EDT
| Can I use my current Windows key in a VMware instance or do I have to buy a new key? |
I don't know much about windows licensing but I use the same MSDN server 2003 license on 6 VM's and each one consumed a MSDN use license. I think every new SID is a new license and Vmachines have nothing to do with the parent computer. |
Well there goes that idea. Maybe I'll just dual boot two installs of XP or VM Linux. 
|
technically,you are flat out WRONG. except for development (MSDN, etc) licensing, you need a seperate, additional copy of windows for each virtual machine. try taking a gander at the EULA someday, it will be eye opening  if you want to run windows with the same key on the host and virtual machines, be my guest - i can't say i've never done the same thing. just understand that it IS a violation of the EULA, and there may be some point in time where they refuse to activate your copy of windows. dizza, i've run into your incorrect info more than a few times here. where you do find this stuff? |
that is incorrect, VMware virtually creates its own seperate set of hardware specs, like the motherboard, chipset, video card, NIC, etc. this will cause windows product activation to freak out if you try to move an activated copy of windows from a physical machine to a virtual machine. |
If it is the same key, on the same machine it is just like having two instances of XP installed in two different directories as a dual boot option. You did notice the ":)" there as well... I didn't give a dissertation on how it was legal or not legal. It was a quick comment about it, because it will work. As for my "incorrectness" on these forums, call me out on them right here and now. As I think you are full of shit on that account. -d |
unfortunately, it is not just like having two instances of XP set up in a dual boot configuration. in this setup, only one OS could be in use at any certain time. using VMware, it is possible to derive usage from both "installations" at the same time. that is a problem with IT folks today, just saying "oh it will work" without really thinking about what is the best choice is gets alot of people into problems. i also don't like to hand out information that instructs users to violate EULAs without making sure they really understand what they are doing and the possible reprocussions. if this is a Retail copy of windows that the OP is talking about, it will almost surely fail activation and WGA on the new installation. |
As far as I know, the only Windows product EULA that has any leeway for multiple instances when virtualized is 2003 Enterprise. You can have 4 instances virtualized for a single license IIRC (ESX or I3) or 1 physical plus 4 virtual in the case of VMWare server. Of course, it just so happens that 4 standard 2003 licenses is damned near identical to the cost of 1 Enterprise. YMMV depending on your "licensing specialist"  It's definitely worth the Enterprise license if you need to cluster or address more than 4GB of RAM |
We could, but first it's better to address erroneous information about the most basic aspects of the MS licensing scheme. 
|