OEM OR Retail
- Thread starter magicman
- Start date
YeOldeStonecat
Well-Known Member
- Reaction score
- 6,888
- Location
- Englewood Florida
I don't get concerned with desktops...but for servers, and for MS Office...I always do Volume licenses.
The reason for servers, is for the purpose of disaster recovery...and virtualization. As you know, OEM licenses live and die with the hardware they were purchased on/with. If a server goes belly up (like catches fire, or major hardware failure, or even just a normal hardware refresh/upgrade) , you can't "restore" it's last backup to new hardware.
Similar to places that do backups of important users desktops...gotta make sure that's a retail or volume license of Winders....
The reason for servers, is for the purpose of disaster recovery...and virtualization. As you know, OEM licenses live and die with the hardware they were purchased on/with. If a server goes belly up (like catches fire, or major hardware failure, or even just a normal hardware refresh/upgrade) , you can't "restore" it's last backup to new hardware.
Similar to places that do backups of important users desktops...gotta make sure that's a retail or volume license of Winders....
Slaters Kustum Machines
Well-Known Member
- Reaction score
- 2,498
- Location
- Iowa
I do the OEM System Builder licenses if needed for residential.
TurricanII
Well-Known Member
- Reaction score
- 449
- Location
- Isle of Man
My understanding and experience is that if there is a Windows OEM sticker on the new hardware then you can restore the OEM server or workstation to the new hardware. It will deactivate and you can enter the key attached to the new hardware to successfully and legitimately activate. It is just the licence (key) that is non transferable.
TurricanII
Well-Known Member
- Reaction score
- 449
- Location
- Isle of Man
I'll do some research. Image based deployment is one thing. Restoring a PC is a different thing.
Maybe, but I'd say restoring an image of PC that came with an OEM install of Windows to a different PC with an OEM install of Windows is re-imaging.
TurricanII
Well-Known Member
- Reaction score
- 449
- Location
- Isle of Man
How to restore a Windows installation or move it to different hardware
"Also, the source and destination computers should both use retail versions of Windows or the same OEM version of Windows."
https://support.microsoft.com/en-us/kb/249694
I will still look for more recent evidence but I did research this years ago and was satisfied that restoring and reactivating is fine.
"Also, the source and destination computers should both use retail versions of Windows or the same OEM version of Windows."
https://support.microsoft.com/en-us/kb/249694
I will still look for more recent evidence but I did research this years ago and was satisfied that restoring and reactivating is fine.
Markverhyden
Well-Known Member
- Reaction score
- 11,213
- Location
- Raleigh, NC
Not entirely correct, at least on this side of the pond. You cannot take an HP OEM image and move it to a Dell for example. The OEM license is with HP and not Microsoft. Now, you could move it to a new HP machine as long as the OS license version is the same.
Well, it's looks like the line is probably drawn a little farther back. However, when that article talks about different hardware, they mean the same make and model.
My guess is that if the image has to be generalized, that is when you are not in compliance without re-imaging rights.
My guess is that if the image has to be generalized, that is when you are not in compliance without re-imaging rights.
TurricanII
Well-Known Member
- Reaction score
- 449
- Location
- Isle of Man
Yes indeed - keep the same manufacturer and precise edition of Windows IF your backup is of the original HP/Dell factory installation, or if you installed with manufacturer system locked media, because it may well not activate (due to not having correct manufacturer info in BIOS) or might BSOD due to OEM drivers.
If you are restoring MS OEM Windows server/workstation then don't worry about keeping same manufacturer - just make sure you have a new OEM licence for the new hardware.
When you restore to a new PC, you are not transferring the original OEM licence. The original OEM licence and sticker stays with the original chassis. You input and start using the new OEM sticker licence on the new chassis.
Microsoft define imaging as 'the copying of software onto multiple devices from one standard image'. That is clearly not restoring in full from backup in order to recover from hardware failure.
A Microsoft SAM audit for instance will not flag any problems with OEM systems that had to be restored.
Last edited:
YeOldeStonecat
Well-Known Member
- Reaction score
- 6,888
- Location
- Englewood Florida
In a disaster recovery scenario...I often won't have the luxury of "lots of time" dealing with Haboo in India arguing about moving a Windows server license. In the past, I may have gotten OEMs to work on different hardware, and we have called MS support for "special cases" and gotten it working. But..during an emergency, spending lots of extra time isn't something you want to do.
I've always read "OEM license lives and dies with the hardware it came with".
Perhaps for desktop computers....you can sleep better at night knowing the Microsoft Police won't be knocking on your door, if you purchase another computer with the same exact OS sku.
But I focus on servers. What about "business continuity" services....you're booting up that VMDK or VHD on a new appliance that is running some *nix host? Or even if it's another Hyper-V box? Multiple hosts are migrated to it? If I think long and hard I "might" be able to come up with a scenario where I get lucky and the new destination host happened to be purchased with the same exact sku OEM license. BUT...in the real world...99% of the time I won't get the lucky. I have to have confidence it will work on the first shot!
TurricanII
Well-Known Member
- Reaction score
- 449
- Location
- Isle of Man
Don't want to sound like I am waffling on about this so I will make this my last post, but there is no arguing with MS activation line. Because the new hardware has its own OEM key matching its hardware ID's, activation happens without a problem.
The point I was making for the benefit of desktop support people is that in an emergency you can restore e.g. the CEO's PC or move their hard drive to a spare PC of the same model in the office. Just need to reactivate it afterwards with the new machine's OEM 25 digit key. You are NOT transferring any licence. The old licence key does stay and die with the old machine. You switch to the new 25 digit Windows (and maybe Office 20xx) licence stuck to the new hardware. Knowing you can do this might get someone out of the X@$! one day if it is the CEO/a critical system that has failed and you can't afford to wait for spares/a rebuild.
E Bell
Active Member
- Reaction score
- 88
- Location
- Houston, TX
The Microsoft Software License Terms is granted to the end user by you, the system builder. It is related to the OEM System Builder License for the PC on which it was originally installed.
You are required to support the license on that original PC, but you cannot support a license that has been moved from a PC that you manufactured to one that you did not. This is one of the key reasons why an OEM System Builder License can’t be transferred.
PC transfer to another end user
The entire PC, however, may be transferred to another end user, along with the software license rights. When transferring the PC to the new end user, the following must be included:
https://www.microsoft.com/OEM/en/licensing/sblicensing/Pages/transfer_oem_licenses.aspx
Just for grins and giggles:
If you are building a system for your personal use or installing an additional operating system in a virtual machine, you will need to purchase a full version of Windows 10, available in FPP. Windows 10, Windows 8.1, and Windows 7 system builder software does not permit personal use, and is intended only for preinstallation on customer systems that will be sold to end users.
You are required to support the license on that original PC, but you cannot support a license that has been moved from a PC that you manufactured to one that you did not. This is one of the key reasons why an OEM System Builder License can’t be transferred.
PC transfer to another end user
The entire PC, however, may be transferred to another end user, along with the software license rights. When transferring the PC to the new end user, the following must be included:
- Original software media
- Manuals (if applicable)
- Certificate of authenticity (COA)
https://www.microsoft.com/OEM/en/licensing/sblicensing/Pages/transfer_oem_licenses.aspx
Just for grins and giggles:
If you are building a system for your personal use or installing an additional operating system in a virtual machine, you will need to purchase a full version of Windows 10, available in FPP. Windows 10, Windows 8.1, and Windows 7 system builder software does not permit personal use, and is intended only for preinstallation on customer systems that will be sold to end users.
Similar threads
