Clean Install of OEM OS

[mjf]

I have 2 questions that relate to a "store bought" PC with OEM OS.
Instructions for doing a clean install using the COA key are often given. Legal of course and abides by the EULA.

1) Why do you need to "find" an install disk. Why can't you download this for activation with your legal key?

2) An OEM OS has a different authentication process to a retail version. As I understand it the OEM authentication is based on motherboard identification and little further to do with MS. Whereas, the retail version authentication is always under the watch of MS.
How is authentication handled when you do an OEM OS clean install?

 

[whs]

ad1) I would think that one could download a .iso from a site like this. But then you will have to burn the .iso to a dvd too (unless you use it in a virtual machine). I do not know how safe that site is because I have never used it myself.

ad2) I have installed a few OEM versions from purchased OEM DVDs (I got them from NewEgg). There was no difference in the authentication procedure than with a full retail version.

 

[mjf]

ad1) I would think that one could download a .iso from a site like this. But then you will have to burn the .iso to a dvd too (unless you use it in a virtual machine). I do not know how safe that site is because I have never used it myself.

ad2) I have installed a few OEM versions from purchased OEM DVDs (I got them from NewEgg). There was no difference in the authentication procedure than with a full retail version.

Thanks whs
but Q.2 still puzzles me.
Like many people who buy a PC now. The PC manufacturer has the license to install the OS on their machines. But even with the bought OEM OS they are locked to the PC. A full retail OS is not locked to your PC.

PS: I understand you recently had an activation issue by restoring an "old" image. I don't think an OEM OS would have the same problem. If it did I don't think MS would sort it out for you.

 

[whs]

ad1) I would think that one could download a .iso from a site like this. But then you will have to burn the .iso to a dvd too (unless you use it in a virtual machine). I do not know how safe that site is because I have never used it myself.

ad2) I have installed a few OEM versions from purchased OEM DVDs (I got them from NewEgg). There was no difference in the authentication procedure than with a full retail version.

Thanks whs
but Q.2 still puzzles me.
Like many people who buy a PC now. The PC manufacturer has the license to install the OS on their machines. But even with the bought OEM OS they are locked to the PC. A full retail OS is not locked to your PC.

PS: I understand you recently had an activation issue by restoring an "old" image. I don't think an OEM OS would have the same problem. If it did I don't think MS would sort it out for you.

The statement marked in red is correct. That applies to any OEM version, preinstalled or installed later.

My activation problem was with an OEM version and MS did sort it out. I probably could have done that myself with the automatic facilities, but I called because I had hoped they would shed some light on the cause of the problem. But they had no clue either.
Later I got into contact with another MS person (on the MSN forum) and found out that these problems happen with both retail and OEM versions and with all kinds of different imaging programs, including the Win7 imaging. But he had no suggestion either as to the cause of the problem.

 

[gregrocker]

Everything needed and most questions are answered in http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164.

 

[mjf]

Thanks all - useful info Greg.
WHS,
thanks again
The activation issue/problem bothers me. Maybe MS in the US are more understanding to their customers. Based on previous experience I don't think they would be as supportive in my part of the world (OEM OS=hangup).

 

[Bill2]

OEM activation that happens in the factory is different from how it happens when you do a clean install.

In the factory, the activation process is offline, which means MS servers are not required to be contacted. This is because MS permits large royalty vendors like Dell, HP etc. to deploy a single win7 image across multiple computers, then activate them with a particular brew (Bios marker plus digital certificate plus standard key), to save them the hassle of entering the key and activating 1000s of computers one by one online.

So if, E.g., you run a mgadiag or slmgr -dlv, you'll see the license type OEM-SLP. SLP stands for sytem locked preinstallation which means the SLP keys used to activate.

OTOH, when you do a clean install, you use the COA key on the sticker. This process is the same as retail activation. You go through the usual loops- online activation, if that doesnt work then call MS. The license type will now be OEM-COA (not OEM-SLP).

Feel free to ask.

 

[mjf]

OEM activation that happens in the factory is different from how it happens when you do a clean install.

In the factory, the activation process is offline, which means MS servers are not required to be contacted. This is because MS permits large royalty vendors like Dell, HP etc. to deploy a single win7 image across multiple computers, then activate them with a particular brew (Bios marker plus digital certificate plus standard key), to save them the hassle of entering the key and activating 1000s of computers one by one online.

So if, E.g., you run a mgadiag or slmgr -dlv, you'll see the license type OEM-SLP. SLP stands for sytem locked preinstallation which means the SLP keys used to activate.

OTOH, when you do a clean install, you use the COA key on the sticker. This process is the same as retail activation. You go through the usual loops- online activation, if that doesnt work then call MS. The license type will now be OEM-COA (not OEM-SLP).

Feel free to ask.

Thanks Bill2.
(1) So can you still move from OEM-SLP to OEM-COA using the COA key that's on the computer.
(2) OEM-SLP are authenticated differently and maybe more robust to accepting older images made from the same computer?

 

[Bill2]

(1) So can you still move from OEM-SLP to OEM-COA using the COA key that's on the computer.
(2) OEM-SLP are authenticated differently and maybe more robust to accepting older images made from the same computer?

1) Yes, you can. The COA key is exactly what it says- proof that you purchased genuine windows and a safety net to reactivate the system should a fresh install be required. There is no bar to moving from one type of activation to another. Practically speaking, once the OEMs stopped giving out restore disks, this is the only way left for end users to reactivate.

2) The only reason OEM-SLP are authenticated differently is the convenience of the royalty OEMs. See, OEM sales are a very large proportion of MS profits and MS and OEMs have a symbiotic relationship. This method permits painless activation, because the image already contains the certficate and key required to pair with the bios flag.

 

[mjf]

So it seems to me that if
(1) you have a factory recovery capability (made the disks)
(2) Cleaned out undesirable trial software ("bloatware")
(3) Are making good reliable images

there may be advantages in just sticking with the OEM-SLP authenticated system.
I am guessing that when you do an online check that the OS is authentic MS may just look for some form of valid OEM-SLP certificate.

 

[Bill2]

Yes, the COA key comes in handy when you need to do a clean install, mostly for folks who never got a restore disk and failed to make recovery disks/ image their system. Otherwise, people just continue using their SLP installs, theres no reason not to.

When you validate an SLP system, the certificate is naturally one of the key indicators that is verified. There are many others- the mobo brand, computer maker, bios maker, bios date, product key, bios flag etc.

 

[mjf]

Yes, the COA key comes in handy when you need to do a clean install, mostly for folks who never got a restore disk and failed to make recovery disks/ image their system. Otherwise, people just continue using their SLP installs, theres no reason not to.

When you validate an SLP system, the certificate is naturally one of the key indicators that is verified. There are many others- the mobo brand, computer maker, bios maker, bios date, product key, bios flag etc.

Sorry if I'm going on a bit - just interesting (to me).
I would have expected MS to have off loaded the items in bold to the trusted manufacturers (HPs, Acers etc..) otherwise MS aren't saving themselves that much effort.

 

[Bill2]

If I understand correctly, what you mean is that either OEM computers should not require validation at all or validation should be restricted to some select components. In an ideal world, that could be possible. Unfortunately, there exist ways to circumvent the system.

Also, this is part of the broader MS anti-piracy initiative which covers the different types of licenses. Piracy hurts MS, so anturally one would expect innovation to come from them rather than from the OEMs. Also, there really isnt that much effort going into it as you might think. WAT calls home only once in 90 days, and it hasnt evolved too much since it was introduced, but thats another topic......

 

[mjf]

I came across the summary below which was interesting.
I never recall activating my Acer OS and I think it falls into the category OEM:SLP described in the link. It states that the OEM:SLP activation is carried out offline without contacting MS. I can imagine how the security of these systems could be very tight and avoid MS costly overheads.
My PC appears to have a COA sticker so I think it may fall into the category OEM:COA with OEM:SLP key preinstalled.

They mention the OEM:NONSLP which does need to be activated by phone or online. I'm guessing that if I activate my OS with the COA key it then falls into the OEM:NONSLP category.

Introduction to windows 7 product key

 

[Bill2]

I never recall activating my Acer OS and I think it falls into the category OEM:SLP described in the link

Correct.

It states that the OEM:SLP activation is carried out offline without contacting MS. I can imagine how the security of these systems could be very tight and avoid MS costly overheads.

The SLP activation scheme has loopholes which have been exploited but by no means is this MS's biggest headache. However, newer EFI bios's are already around and will become mainstream, these will be far more difficult to manipulate. I believe MS and the OEMs are cooperating on this.

Please remember that its not that MS cant catch this kind of rogues. Technically its quite possible but the logistics are somewhat prohibitive plus false positives ratchett up support calls.

My PC appears to have a COA sticker so I think it may fall into the category OEM:COA with OEM:SLP key preinstalled.

No, your PC will fall into the COA category only if you use the COA key to activate windows.

I'm guessing that if I activate my OS with the COA key it then falls into the OEM:NONSLP category.

When you do that, it'll fall in the COA category. OEM-NONSLP is a different license, it refers to system builder oem installs. Thats the kind you buy cheap from Newegg etc. or the types used by white box vendors, they work and behave like retail keys but are cheaper because MS support is not bundled.

 

[mjf]

My PC appears to have a COA sticker so I think it may fall into the category OEM:COA with OEM:SLP key preinstalled.

No, your PC will fall into the COA category only if you use the COA key to activate windows.

Yes ok. My PC is effectively OEM:SLP at the moment but can be made OEM:COA with a clean install and activating windows.

Where I started from was the idea that with OEM:SLP you are less likely to get activation issues (on the same PC of course). Moving to OEM:COA could introduce the occasional need to reactive like OEM:NONSLP which both seem to involve MS in ongoing activation checks.
Therefore there could be an advantage in retaining the OEM:SLP activation state.

 

[Bill2]

Well, if you stick to the original factory install or reinstall using the recovery disks/restore disk, then activation issues are unlikey to crop up.

 

[gregrocker]

What activation issues? No activation issues here in 100+ factory OEM clean reinstalls with COA activation.

A factory install is compromised from the start with bloatware including useless factory utilities which needlessly duplicate superior features in Win7, and which are nearly impossible to remove without corrupting System Files. It is a corrupt install.

Therefore a clean reinstall makes any factory install "better than new."

Activation issues are negligible.

Clean reinstall tips: http://www.sevenforums.com/installation-setup/125874-re-install-windows-7-a.html#post1086729
Attempt to clean up factory OEM tips: http://www.sevenforums.com/installa...p-all-four-primary-partitions.html#post952573

 

[Bill2]

Dont worry, I'm not advocating factory installs, the statement about activation was not exclusive of other types of licenses.

 

[mjf]

As I now see it the best approach is if you have an OEM:SLP (most bought systems)
(1) Clean up the trial software. If some residual components remain, clean them up manually (or with things like Revo Uninstaller) or forget about them unless they cause problems.
(2) Go to OEM:COA if (1) is proving to be a problem or you want certain changes to your partition structure. With the COA sticker you can always go from OEM:SLP to OEM:COA at a later stage.

With (1) it appears to be less likely you will get reactivation issues later on. eg. with older images.
Retail, OEM:COA, OEM:NONSLP may all require MS reactivation at some stage. This should be straightforward and able to be done with a phone call or online.
-------------------------------------------------------------------------------

This is the conclusion I have come to so far in this discussion (including the little bit of information I refer to).
My current OEM:SLP has 4 primary partitions:
Factory Recovery; System Reserved; Win 7 OS; Data
I think I could (if I wanted!) change the Data partition to Extended & have multiple logicals.

I know through the forum advice how to go OEM:COA / clean install if and when I want to.