License for Windows 7 in VM?

[CootCraig]

I just ordered an HP ENVY 17-1010NR with Windows 7 Home Premium 64-bit. I would like to install a clean Windows 7 on the hard drive and then use a Windows VM as my main workstation. Can anyone tell me if the Windows 7 license allows this?

FWIW, I am a software developer and have been running multiple VMware player VM's on a Vista 64 box for work.

 

[pparks1]

Not without purchasing another license. Of course, as a software developer you might have something like Technet or more likely MSDN which would allow this.

 

[CootCraig]

Thats too bad. What about running Ubuntu on the hard drive and then running Windows 7 on a VMware player, does the Windows 7 license allow this?

Not without purchasing another license. Of course, as a software developer you might have something like Technet or more likely MSDN which would allow this.

 

[Dark Nova Gamer]

Thats too bad. What about running Ubuntu on the hard drive and then running Windows 7 on a VMware player, does the Windows 7 license allow this?

Not without purchasing another license. Of course, as a software developer you might have something like Technet or more likely MSDN which would allow this.

This page may help you slightly.

Neowin.net - Virtualizing Windows may violate your license requirements

--

Though to be honest, I wouldn't truly worry any 'End User License Agreements'. As long as you are running it on one PC at a time (this includes VM's) you should be golden.

 

[ken9122]

Though to be honest, I wouldn't truly worry any 'End User License Agreements'. As long as you are running it on one PC at a time (this includes VM's) you should be golden.

I agree

 

[pparks1]

Thats too bad. What about running Ubuntu on the hard drive and then running Windows 7 on a VMware player, does the Windows 7 license allow this?

Yes, because you would be using the 1 license you are entitled to. Unless of course that license is OEM and then it's tied to the actual physical machine and cannot be moved to another machine.

 

[CootCraig]

I have some trouble grasping this. I would wipe windows 7 from the hard drive, install Linux and VMware player, and then install windows 7 on a vm using the activation key for the OEM license on the laptop. So there would be only one copy running on the OEM hardware. I am assuming that the windows 7 would be legal and could be activated. Agreed?

Yes, because you would be using the 1 license you are entitled to. Unless of course that license is OEM and then it's tied to the actual physical machine and cannot be moved to another machine.

 

[Darician]

Technically, this would be a sort of loophole as you are still technically on the same physical machine. It just so happens you're running a virtual one on top of it. I don't think there would be a problem with it but again, this is one of those really grey areas.

 

[pparks1]

I have some trouble grasping this. I would wipe windows 7 from the hard drive, install Linux and VMware player, and then install windows 7 on a vm using the activation key for the OEM license on the laptop. So there would be only one copy running on the OEM hardware. I am assuming that the windows 7 would be legal and could be activated. Agreed?

I don't even think in this instance that it actually qualifies...as technically the virtual hardware being presented does not match the physical real hardware in the box. Plus, once a VM is up and running, you can easily move it from machine to machine without it seeing a hardware change....so in the event that you went to another machine your VM license would still be activated and valid...which is not allowable with an OEM copy.

 

[CootCraig]

I'm not going to attempt this - I'm usually a stickler for following licensing, although sometimes I don't understand. In any case, I think I'm better off leaving the laptop hardware to Windows 7. I am disappointed Microsoft does not allow one Windows 7 VM on the native instance though.

I plan to use VMware player hosted on Windows 7 to run a number of Linux instances.

Thank you for all the thoughtful responses.

I don't even think in this instance that it actually qualifies...as technically the virtual hardware being presented does not match the physical real hardware in the box. Plus, once a VM is up and running, you can easily move it from machine to machine without it seeing a hardware change....so in the event that you went to another machine your VM license would still be activated and valid...which is not allowable with an OEM copy.

 

[pparks1]

I'm not going to attempt this - I'm usually a stickler for following licensing, although sometimes I don't understand. In any case, I think I'm better off leaving the laptop hardware to Windows 7. I am disappointed Microsoft does not allow one Windows 7 VM on the native instance though.

The only thing they do allow is for somebody who purchases Windows 7 Professional, Enterprise (which required a VL) or Ultimate is a license to allow them to run Windows XP Mode on their machine in a VM. Microsoft is all about making money.

 

[CootCraig]

If I find I really need this I will purchase a Windows 7 retail license.

 

[CootCraig]

On my previous job I had access to MSDN licenses, but I don't now.

Not without purchasing another license. Of course, as a software developer you might have something like Technet or more likely MSDN which would allow this.

 

[jimbo45]

Hi there
Windows licenses in Virtual Machines is a rather moot point -- in theory you will need a license for EACH Virtual machine --but in practice since you build your Virtual Machines using essentially identical (or similar) Virtual hardware you can actually make a number of identical virtual machines using ONE copy of Windows.

You will need to activate ONE version of windows even in a Virtual Machine.

OEM versions cannot be activated but full retail or technet copies can be.

Create your VM with roughly the Virtual hardware you need and then activate it. Now this Virtual Machine can be "cloned" as many times as you like and it will actually allow reasonable "Virtual Hardware" changes before requesting a new activation.


XP mode is another issue -- you *might* be able to extract the XP image and run this as a native VM under vmware / vbox. Some people have done this --I haven't tried yet as I was really DISAPPOINTED with XP mode --great idea but badly implemlented.

Cheers
jimbo

 

[Barman58]

One other option which may be of use in a development environment, and it would be wholly dependent on the development cycle involved - you can legally run a copy of win7 either actual or virtual for up to 120 days before it needs to be activated, using the re-arm system.

 

[jimbo45]

Hi Barman -- true but if you actually USE your VM for work then the rearm every so often is a pain in the rectum.

I use an XP VM for a Canon 1240 scanner, an old HP Blueprint plotter, some Minidisc recording software, Outlook Express email client and some other Pre Press type of applicatons.

I don't think I'd want to go through the rearm / re-install again --especially for some of the legacy hardware I don't have the drivers any more -- and can't get them as the devices are no longer made.

For some people your solution is fine.

The real problem with licensing I suspect is that Windows doesn't know whether it's running on a real or Virtual Machine.

I hope the NEXT version of Windows will allow you to run as many Virtual machines as you like so long as it's on the SAME computer you licensed Windows for.

This will need a change to the Intel / AMD instruction set as well as to most PC's.

The old IBM mainfames came equipped with an instruction STCPUID which stored the CPU ID in a protected area in ROM. When the OS was loaded (Old MVS/370 etc) the OS would check the CPUID that it was licensed for and if OK would continue the boot (or IPL - Initial Program Load as it was known in those days).

Something like that would do and also prevent "Infinite cloning" of Virtual Machines too.

Cheers
jimbo

 

[Barman58]

Hi Jimbo,

My suggestion here was not one for long term but more for short term development projects, where in my case normally ended with the os being re-installed anyway - The rearm is a short term workaround and always will be