Printable View
I have a server that was loaded with an OEM license for Windows Server2003
Web edition, and am converting it to a virtual machine. When doing so, the
server requires re-activation, and the OEM license is not valid. I have a
Windows server Datacenter license to cover my VM host and guests, but want to
know how to either activate the OEM license on the guest, or apply my
datacenter license (while not fundamentally changing the guest).
Datacenter is not webedition, so it will not work. Also you can not upgrade
from web edition to datacenter.
Q. What are the licensing considerations in a virtual machine environment?
A. For information about licensing in a virtual machine environment, download
the licensing brief Licensing Microsoft Windows Server and Other Microsoft
Server Software for Microsoft Virtual Server 2005 or Other Virtual Machine
Environment (Microsoft Word file, 307 KB).
Q. Can I move an original equipment manufacturer (OEM) license for Microsoft
Windows Server to a virtual machine into another virtual machine? How is
the situation handled?
A. You may not transfer OEM server licenses from the original machine to
a different machine. Any Microsoft Windows Server license that is preinstalled
on a new computer from an OEM or that you acquire through any Microsoft Volume
Licensing program is tied to the computer on which the licensed software
is first installed. This applies to the initial copy that is installed on
the computer and to any subsequent copies that are licensed to run with virtual
machine software.
Also see:
http://www.microsoft.com/licensing/h...ation/faq.mspx
http://download.microsoft.com/downlo...whitepaper.doc
So in my opinion there ios no way to move the OEM to another hardware even
if virtual. If the VM stay on the SAME hardware, it should be possible. To
make usre contact MS or your license vendor, he should know it correct.
According to your description, I understand you would like to virtualize an
OEM Windows Server 2003 Web Edition and have some questions about
licensing. If I have misunderstood the problem, please don't hesitate to
let me know
I agree with Meinolf, it basically should not work. However, in order to
get more detailed information, please call 1-800-426-9400 (select option
4), Monday through Friday, 6:00 A.M. to 5:30 P.M. (PST) to speak directly
to a Microsoft licensing specialist. They may provide workaround for this
problem.
Do you need any other assistance? If there is anything we can do for you,
please let us know.
I agree, the PID bits are not interchangeable between OEM, Technet, MSDN or
VL. Each are unique to their respective media.
Start the VM with a boot disk like BartPe. SOoyou can access the data.
I think I have a similar situation as David...
I converted my physical Windows 2003 Server to a VMware Image.
After loggin a new activation is required ... still no problem...
Installation ID is not valid anymore... ok.
Change Product Key... and now the "strange story" starts.
I want to enter my product key: "PBTYW-...." But some keys are not working???
e.g. "B" or "Y". So I cannot enter the product key :-(
Keyboard works fine at GINA login...
Any idea how to solve this?
Small correction: "P" key is not working and not "B" ;-)
As the server is used in a lab installation, is it possible to migrate to a
technet product key?
Did you install the VM additions on the VM, to get full compatible VM drivers
also for the keyboard?
You can not use OEM software to install another liecensed version like Technet,
MSDN or volume license as far as i know.
I installed VM Tools but that did not help either...
actually the Windows installation itself is not that important BUT the
data which is stored on the harddisk of the virtual machine. I have a backup
of almost everything... but still some files missing....
As I cannot do anything except activating windows after login I have no
access to them anymore.
Is there a way of postponing the activation to rescue the files?
As I own a legal version of windows server 2003 which is installed on the
same hardware I think I should have the right to run a working OS...?
Or if the original harddrive still exists, install it into a machine with an existing Windows installation, and access the data on that drive through the other Windows installation.