Re-installing 7 from scratch

[alivin]

I built a comp recently and with it I bought an OEM system builders home premium 64bit pack. It came with a dvd. I would like to re-install it from scratch.
My only worry is the serial #, I used it to originally install and if I re-install will the on-line registration be rejected as the # has been used ?

 

[kronwhon]

If your hardware config is unchanged, you will be fine

 

[alivin]

I added a 2nd hard drive after the install, Problem ?

 

[kronwhon]

Possibly, but as long as you didn't replace the motherboard, you are perfectly within your rights. If there is a problem, you will need to do a phone activation (VERY routine at MS).. It even provides the phone# for you.

1-888-571-5048, if memory serves correct

 

[gregrocker]

Bypass the first key request and activate upon connecting to internet at Computer>Properties link. It may require a robo call to trade numbers, but more than likely it won't since it will match enough of the hardware to pass that flag, then see the same key.

Changing the HD is not enough to invalidate an OEM, only a mobo. And they are apparently making some exceptions now: http://www.sevenforums.com/installa...-retail-oem-osb-sb-versions-3.html#post404303

 

[solar]

alivin, one of the ideas of an OEM pack (and since you are saying you are building on ONE computer), it shoudl not be a problem AT ALL, as people have pointed out (i.e. MOBO isssues).

As an 'builder' you should b aware of the whole point of you perhaps trying to set up a honme recovery system which means 'factory restore' ... a key is still valid right?

 

[kronwhon]

Users who run a Microsoft Original Equipment Manufacturer (OEM) operating system may upgrade or replace most of the hardware components on the computer and still maintain the license for the original Microsoft OEM operating system software provided by the OEM, with the exception of an upgrade or a replacement of the motherboard. An upgrade or a replacement of the motherboard is considered to create a new personal computer. Therefore, Microsoft OEM operating system software cannot be transferred from another computer. If the motherboard is upgraded or replaced for reasons other than a defect then a new computer is created, and a new operating system license is required.

from:
How to replace the motherboard on a computer that is running Windows Server 2003, Windows XP, or Windows 2000

Replacing the motherboard is considered to be creating a new computer.

 

[gregrocker]

Replacing the motherboard is considered to be creating a new computer.

Unless you replace it with the same model motherboard.

This is what the Geek Squad does for manufacturer's OEM.

But they say if they can't find the exact mobo, they have a way to get around it.

I have always wondered what that is, and how would it be legal enough for them to get away with it?

 

[kronwhon]

Replacing the motherboard is considered to be creating a new computer.

Unless you replace it with the same motherboard.

This is what the Geek Squad does.

But if they can't find the exact mobo, they say they have a way to get around it.

I have always wondered what that is?

Yes, if the motherboard is replaced under WARRANTY by manufacturer. e.g. Geek Squad contacts manufacturer who prescribes replacement MOBO but is no longer sold, replace with current model. Replacement for any other reason constitutes brand new computer.

 

[kronwhon]

If the motherboard is replaced because of a defect, the user does not need to acquire a new operating system license for the computer. The motherboard replacement must be the same make and model, or the same manufacturer’s replacement or equivalent, as defined by that manufacturer’s warranty
same article referenced above

 

[alivin]

Thanks guys,
interesting to see it's still the same, new mobo = new comp, it's been a while and I wondered if they'd tightened up the definition of 'new'

 

[whs]

You should not have any problem if you just added a disk. I just switched the Win7 installation disk on my OEM Win7 without problems. I went the normal route and activated it first time it asked for the key.

 

[kronwhon]

The article I referenced was reviewed Sept 07. Vista was released Jan 07.

If anything new is announced, I will most likely be among the first to know (I work for MS licensing). mobo is still considerred the computer, and likely will be for quite a while to come.

 

[gregrocker]

Replacing the motherboard is considered to be creating a new computer.

Unless you replace it with the same motherboard.

This is what the Geek Squad does.

But if they can't find the exact mobo, they say they have a way to get around it.

I have always wondered what that is?

Yes, if the motherboard is replaced under WARRANTY by manufacturer. e.g. Geek Squad contacts manufacturer who prescribes replacement MOBO but is no longer sold, replace with current model. Replacement for any other reason constitutes brand new computer.

They still have to activate it. What allows the exception for a replacement mobo not of the same model? I know the manufacturer authorizes it under warranty, but MS must make an activation exception, right?

I think they have some undisclosed leeway on OEM, as with Upgrades being allowed to install to new or formatted HD's.

 

[kronwhon]

Hi Greg, Yes MS has to make an activation exception. This is something I've never encountered, and a very rare issue (most computer repair shops will suggest a new comp if faced w/ replacing the mobo)... also, if a mobo is being replaced under warranty (usually 1 year) there is only a very very slim chance that the model is not being produced any longer.

In the unlikely event that all above situations fall into place, activations will be forced to make an exception, although I foresee that being a problem getting transferred to several different departments until you reach an agent who knows what he's doing.

In short, the situation you are suggesting almost never happens, and that will be reflected when calling MS to try to get the "exception".

Geek Squad is correct in saying that if the mobo is not available there are ways around it, but this is extremely unlikely, as it must be under manufacturer's warranty.

 

[solar]

Kronwhon, I just wrote to microsoft regarding some issues but for now no reply so I just was wondering if you coudl ask someone or you know a pointer for me.

I want to link a program I am making to a motherboard. Is there a 'simple' way of accessing unique mobo identifiers or does one have to go via the native api (ntoskrnl.exe etc)?

 

[kronwhon]

Hi Solar, sorry I don't have any pointers for you. If you have MSDN subscription, then you're best to post on an MSDN forum. I have some personal programming background, but my training at MS was strictly licensing, not technical or dev.

 

[gregrocker]

Hi Solar, sorry I don't have any pointers for you. If you have MSDN subscription, then you're best to post on an MSDN forum. I have some personal programming background, but my training at MS was strictly licensing, not technical or dev.

Perhaps you can enlighten us whether MS will easily activate a 64 bit reinstall of a 32 bit factory installed OEM.

Several who have received their maker's Upgrade Kit report a clean copy Win7 Upgrade DVD but only of the 32 bit version installed. They would rather have 64 bit.

If they reinstall using their own 64 bit installer and attempt to activate using the OEM key on the Upgrade Kit DVD package, will it auto-activate 64 just as it does 32, since it is the same hardware, or will they need to make a call?

Can their manufacturer block activation of another bit version when it is MS policy to allow either 64 or 32 bit with each license?

I'm assuming the makers are sending same bit version to keep machines same version for proprietary reasons, but these owners surely have the right to try 64 bit since it comes with the same license.

 

[kronwhon]

Hi Greg,

If you are referring to the upgrade kit provided with the Free Windows 7 Upgrade Offer when buying a computer pre-loaded with Vista, you will always receive the same platform as that which was pre-installed. eg. if it came with 32-bit, the upgrade kit will always be 32-bit. Windows Anytime Upgrade works the same way.

The retail upgrade purchase will always come with both 32 and 64-bit versions, and the same product key will unlock both.

If your computer is pre-installed with OEM Windows 7 32-bit, then your key will also unlock 64-bit, provided that it is OEM, and that it is the same Edition (eg. Home Premium 32-bit will unlock Home Premium 64-bit). An OEM key will not unlock retail or Volume License media, and vice versa.

Furthermore, your manufacturer should be giving a choice before purchase of either 32-bit or 64-bit, and neither the OEM or MS are required (or willing, in most cases) to provide alternate media.

********
There are 2 types of OEM media, system builder (generic/custom built) and hardware manufacturer (HP, Dell, Toshiba, etc.). If you purchased from a hardware manufacturer, then only media provided by the same manufacturer will activate properly. If you have a generic system builder license, then any generic 64-bit media will work.
*********

NOTE: The reason I put stars around the above paragraph: there are computer repair shops out there who will disagree with the above statement, and will be partially correct. Bottom Line: using media from a different hardware manufacturer is NOT supported by MS, and if any WGA errors occur as a result, MS will not help. This is the case even if reinstalling same bit media. This fact is documented by MS, but not widely known (even by MS employees).

 

[kronwhon]

"You cannot use your own OEM System Builder media to reinstall the operating system, or any other version of media (e.g., TechNet, MSDN, Action Pack, etc.), because these versions differ from the original OEM Windows license your customer acquired from the direct OEM."

from Microsoft OEM Partner Center