When virtualising your final physical Windows XP machines (just in case you need to hook up old hardware that is unsupported from newer Windows versions), you need to figure out the kind of license of each physical Windows XP machine in order to stand a chance to keep it licensed.
This answer by [Wayback] Moab [Wayback] windows xp – How to know which license version has an XP installed system – Super User helped me a lot.
I tried to make it a bit easier to read:
- First obtain the “Product ID” from the Windows XP machine. It is derived from the original Windows XP installation product key and displays a few values:
xxxxx-yyy-zzzzzzz-zzzzzxxxxx: the MCP (Microsoft Product Code) describing which product version, or in case of Windows XP: what language, edition (like “Home” and “Pro”) and often some more information)yyy: the Channel ID (especially important to set apartOEMfrom other channels;OEMis not allowed to be virtualised, so would need a complete new Windows XP key to be activated as Virtual Machine; Channel IDs being neitherOEMnorVLK(volume license key) can often be re-activated, sometimes over the phone to explain the situation; I’ve not tried virtualising aVLKbased Windows XP yet.zzzzzzz-zzzzz: semi-random values
[Wayback/Archive.is] Product IDs – Lunarsoft Wiki has quite detailed lists of not just the MCP and Channel ID values for Windows XP and Windows Server 2003, but also the disk volume labels and
setup.inilabel values.Often this is easier to do from the physical machine before virtualising it, but even afterwards you can get it by running Windows in Safe Mode, then use either of these to get the Product ID:
- Run the Windows Contol Panel applet
sysdm.cplwhich shows the “Product ID” us under the “Registerd to” information. - From the console, run
reg query "hklm\software\microsoft\windows nt\currentversion" /v ProductID - From another machine or boot CD (like Hiren’s Boot CD or Windows Ultimate Boot CD), mount the hard disk, mount the registry hive, then show the above registry key value
- Download and run NirSoft [Wayback] ProduKey (which usually will give you both the Product ID and Product Key)
- From the product key, determine if you can re-activate Windows, either by phone, or by this link:
I got the link from [Wayback] activate windows xp – Microsoft Community via [Wayback] windows xp – How do I activate WindowsXP now that support has ended? – Super User.
Phone (in most countries) and on-line activation should still work; it worked in 2016 (see [Wayback] license – Will I still be able to activate Windows XP after support ends? – Super User) 2019 (see [Wayback] windows xp – How do I activate WindowsXP now that support has ended? – Super User) and 2020 (see [Wayback] XP activation – Windows XP Home and Professional).
- When OEM, try to obtain a legal Windows XP license key that matches the MCP, then change the key using steps in for instance:
- [Wayback] Change the Volume Licensing product key – Windows Server | Microsoft Docs. I think this is what these below links are based on:
- [Wayback] 3 Ways to Activate Windows XP Without a Genuine Product Key (which covers Changing the Windows XP Product Key Manually, fixing the original product key, and Fixing the Windows Activation Loop)
- [Wayback] Windows XP needs to be activated before logging in [Fix]
- [Wayback] Bypass Windows XP product activation – My *nix world
- [Wayback] How to Make Windows XP Genuine Forever (with Pictures) – wikiHow
- [Wayback] Use OEM Version to Upgrade XP | Petri
- Licensing is a pain; this interesting thread shows how much pain:
-
- [Wayback] Licensing after Virtualizing Windows XP physical machine – MS Licensing – Spiceworks
- [Wayback] Licensing after Virtualizing Windows XP physical machine – MS Licensing – Spiceworks – Page 2
- [Wayback] Licensing after Virtualizing Windows XP physical machine – MS Licensing – Spiceworks – Page 3
- [Wayback] Licensing after Virtualizing Windows XP physical machine – MS Licensing – Spiceworks – Page 4
- [Wayback] Licensing after Virtualizing Windows XP physical machine – MS Licensing – Spiceworks – Page 5
- [Wayback] Licensing Windows 10 with virtualization technologies – How-To – Windows Forum – Spiceworks
I’m not a lawyer, and Microsoft Licensing is a pain (especially for products that are out of support), but it looks like it is about three licenses:
-
- the original OEM license on the physical machine that allowed you to install the original Windows XP on that machine
- the non-OEM license for the Virtual Machine (if I read the thread correctly, it needs to be a Volume License that has Software Assurance) to activate it
- an access license so you can logon to the Virtual Machine or otherwise access it
Alternatively, if you started with a non-OEM license, and you could re-activate it on the virtual machine, it looks like you only need 3 (if you could not reactivate, you’d need 2 and 3)
Chris (Microsoft) had many interesting responses in the thread: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17
Other interesting bits in the thread: the XP activation servers are still working, but buying new keys for it can be problem and given the right licenses, reinstalling a virtual machine is virtually indistinguishable from cloning the physical machine.
-
Note that it is no use searching Google for Windows XP License keys: Microsoft did and invalidated them back in the Windows XP SP1, SP2 and SP3 days: Wayback: Error message when you install Windows XP Service Pack 1 (SP1) or Service Pack 2 (SP2): “The product key used to install Windows is invalid
- [Wayback] Change the Volume Licensing product key – Windows Server | Microsoft Docs. I think this is what these below links are based on:
The 2001 Windows XP Professional License is archived in the Wayback machine as Microsoft Windows XP Professional END-USER LICENSE AGREEMENT: Windows%20XP_Professional_English_9e8a2f82-c320-4301-869f-839a853868a1.pdf (via [Wayback] Convert your existing Windows XP system into a virtual machine – TechRepublic).
Note this does not cover OEM or Volume Licenses.
–jeroen
The Wiert Corner - irregular stream of stuff 