Imaging Windows 7 OEM Build

[SYSTEMATIC]

Morning guys/girls,

I will try to be as brief and precise as possible.

Our company does not have a Windows 7 VLK. Instead we have been instructed to build our laptops and use the OEM key provided with the machine. The model of laptop we are using is HP 8440P.

After receiving our first machine last week, I have configured it to a decent basline standard. I then imaged it using Symantec Ghost - everything went fine.

The problem comes when deploying the image onto another HP 8440p (when it arrives) - If i deploy my image, the product key installed, will be the same one from original laptop (not the new one that comes with the new laptop).

To avoid any legalities and to abide by all MS agreements in place, is there a way I can change the Product Key from the image to the new OEM key provided with the new laptop?

I understand Sysprepping is an option however, I have configured and installed too much on my current image that makes sysprepping a pain in the a**. I have also read a couple of Win7 Sysprep guides, which have led to a few problems.

Is there any other EASIER way or tool (magicjellybean was perfect for XP) where I can simply change/swap the OEM key with the new valid OEM key?

Thanks and appreciate any input,

 

[richc46]

Welcome

After reading so many posts where the Origianal Poster has no regard or respect for the EULA, it is a pleasure to help you.

http://www.sevenforums.com/tutorials/18630-product-key-number-change.html

 

[SYSTEMATIC]

Welcome

After reading so many posts where the Origianal Poster has no regard or respect for the EULA, it is a pleasure to help you.

http://www.sevenforums.com/tutorials/18630-product-key-number-change.html

I have seen the above work for Vista and Windows 7 machines but the same does not work for OEM builds. There is no "Change Product Key" option in the system menu.

My image was taken was from an Activated OEM build. Im guessing, it's not possible to change the key once it's activated.

 

[electrotune1200]

Rt. click My Computer and select properties.

At the bottom of the window click change product key.

My Windows 7 is an OEM installation. I still have the option to change the key.

 

[SYSTEMATIC]

Rt. click My Computer and select properties.

At the bottom of the window click change product key.

My Windows 7 is an OEM installation. I still have the option to change the key.

Hey Friends,

I do not have the "Change Product Key" option whatsoever. I just see the key is activated.

 

[electrotune1200]

The system you are on now... Was it imaged with Ghost, or is it a stock installation of 7?

 

[electrotune1200]

I found this info posted on a forum after doing a quick Google search.

1. Click on start and type command (cmd) with run as administrator option or
open elevated command prompt

• Click on Windows 7 Start Button
• Go to All Programs-> Accessories
• Now right on Command Prompt and select “Run as Administrator” from context menu.
• This should bring elevated command prompt mode with full Administrators rights

2. Now type following command

“slmgr.vbs -ipk <insert your new product key here>”

3. To activate windows after changing the key, run “slmgr.vbs -ato”

done


Link to the source Change Windows 7 product key - Operating Systems

 

[SYSTEMATIC]

Rather than doing a fresh install using the media that came with the laptop, i customised the pre-installed OEM version so yes this was the stock build. I also tried the command as mentioned above - no joy.

 

[madtownidiot]

you could always use one of the windows 7 loaders.. I'm pretty sure you'd be the only one to ever download for a legal purpose

 

[SYSTEMATIC]

What is a Windows 7 loader, and where could I find one please?

 

[madtownidiot]

windows 7 loaders are created by hackers to activate illegal copies of windows. using one to activate windows, or more correctly, to bypass activation is illegal, but you can also change the product key with one, and I don't think there would be anything wrong with that, so long as the rest of the activation process is done legally. as for where to find one, a google search will point you in the right direction.. but I wouldn't seriously recommend using one unless you can't find another way.

 

[theog]

your Norton Ghost image will recovery to all HP 8440p with the same spec.
Did you image all partitions.
I hope you using Norton Ghost v15, as you may find problems earlier ones.

 

[pparks1]

I don't think you want to just image a machine with Ghost and then deploy to multiple machines on the network. If you do this, the SID's and such will be the same on the other machines.

Instead, get the base machine ready and run sysprep on it. This will generalize it and remove the SID's and such as well as the registration key used. Then, once it shuts down, you image it. When you deploy this image, the first boot will take you through a mini-setup...where you can input the proper key.

There are other ways to resolve the SID issue (newsid)....but this method resolves multiple issues for you.

 

[Mark Phelps]

I understand your predicament, but would advise against using any of the "loaders" or any other of the activation-bypass "hacks" -- no matter where you find them.

There is an ongoing cat-and-mouse game between the hackers and MS, with the hackers being one or two steps ahead at most. A "hack" that works today might very well NOT work tomorrow -- when MS catches up with the latest one and patches that "problem" with a security update.

I'm guessing you wouldn't want your network of machine to suddenly become deactivated, right?

Better to avoid that problem now than have a community of angry Win7 users because their machines have suddenly been crippled!

 

[Faladu]

At this point, I would call Microsoft and ask them for advice on the matter.

 

[Reboot]

I'm not sure how the build of the system can result in sysprep being a problem. I guess that I just dont have enough information as to the build as to what could go wrong when the system gets resealed.

I'm currently in the process of migrating our company from XP/Vista to 7 Pro and I'm going to give Microsoft's "how to" a shot:

How Do I: Windows 7 Deployment Tools Part 1?

I'm building out my first laptop system now (Dell Latitude E6410) and I'll let everyone know how it turns out in a day or two.

 

[agreensmith]

Hi Systematic,

One of the problems you face is that OEM keys have certain reference files in the OS and recovery media that make that build of OS specific to that machine / machine type.

If you are imaging WITH the key installed on an existing OEM install, and then deploy that image to another OEM machine, you SHOULD be ok. Some manufacturers keep the keys PER MODEL, but some have individual keys PER MACHINE. I know this as I've been having trouble with Lenovo Thinkpad E530's for the last three months! They're keys are the same PER MODEL. But if you rebuild to fresh install you cannot activate it on the original key. (Origonal key was gotten using Bellarc Advisor). There are various legitimate workarounds to re-insert a new OEM key, but be if you are using a fresh build it wont activate. Best thing to do (as Faladu suggested) is speak to Microsoft, or even better, the manufacturer/supplier/purchaser to make sure that their OEM install will be accepted on multiple machines.

 

[NoelDP]

If you are imaging WITH the key installed on an existing OEM install, and then deploy that image to another OEM machine, you SHOULD be ok. Some manufacturers keep the keys PER MODEL, but some have individual keys PER MACHINE. I know this as I've been having trouble with Lenovo Thinkpad E530's for the last three months! They're keys are the same PER MODEL. But if you rebuild to fresh install you cannot activate it on the original key. (Origonal key was gotten using Bellarc Advisor). There are various legitimate workarounds to re-insert a new OEM key, but be if you are using a fresh build it wont activate. Best thing to do (as Faladu suggested) is speak to Microsoft, or even better, the manufacturer/supplier/purchaser to make sure that their OEM install will be accepted on multiple machines.

Not so - with Windows 7's SLP v2.1 activation, all manufacturers use a single Key (per OS per manufacturer).
What changes is the licenses built in to the OS, and the SLIC table in the BIOS.
With machines from the same model line, all SLIC tables and OS licenses are the same,

Reinstallation using the manufacturer's media (and from images created from such an install) do not require external activation, as the three parts of the process force internal self-activation.

Reinstallation using media other than the Recovery media from the manufacturer will require use of the COA Key.