Link to home
Start Free TrialLog in
Avatar of pragmadrift
pragmadriftFlag for Norway

asked on

Deployment of OEM image on Computers?

Hello

We are currently using SCCM to deploy computers in out company. When we buy new Dell Laptops it is shipped with Win7 Pro OEM.  So Dell is certified to deploy an OS with the Laptop. But i find these "Default Os installations from DELL" to contain to much software and I would like to add other software to like (firefox,adobe).

So when I opened the package there was a reinstallation DVD with Win7. I took that DVD installed a fresh install of Windows 7 and added software to it.Then when the image was finish. I syspreped the Imaged and created a deployment of it.

Every thing is working perfect but there is one thing I'am, wondering,f I have done something wrong. When I look at one of the clients I have deployed win7 I can se that it have been Activated auto, I was told that this is because it is activated in BIOS since it is a OEM.

But then i See that every computer has the same Product-ID. This is were i am thinking something is wrong.

So i need a little guideiance here.

We can not use Enterprise agreement or an Open vaule. we have to use OEM.

So am I doing right? Can I create a image of OEM Win7 and then deploy it to other computers?

Everything works just the computers get the same product ID..........:(

Thx to everyone who has a minute :)



 
ASKER CERTIFIED SOLUTION
Avatar of Glen Knight
Glen Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It's called system locked preinstallation (SLP) and yes, the Dell copy will just "Activate" if it finds the correct SMBIOS string on the motherboard.  What you are doing will work unless you try deploying the image to non-Dell hardware.  In that case, Windows will refuse to activate.
Avatar of pragmadrift

ASKER

Yes I tried deploy to other models to se if they activated, they did not. Everyting works fine it's just the Product ID is the same on every computer.

Can I solve this any way or isn't this a problem?

Thx for the reply!:)
As I already said you should be using Volume Licensing to do this, the OEM is licensed to the hardware it is provided with.

You are actually breaking the license agreement if you rollout an OEM license to more than 1 computer.
Okey butt all the computers are deployed with a OEM lisens. So every computer are having a Win7 license. Don't se I'am breaking any agreement?
Only Microsoft can confirm this, I suggest you give them a call.
Every PC should have a unique product key sticker.  That is your OS license.
If you want the flexiablity of using VL media, then you need to purchase a VL license on top of the OEM license for every PC.  You cannot and should not try to use VL keys with OEM media.
As demazter suggests, you should talk to a Microsoft licensing specialist.  The 2nd page of this PDF should answer some of your questions:
http://download.microsoft.com/download/F/8/7/F875E083-1721-459D-A84D-4AD21F06EEE9/OpenProgramsComparison-includesFPPandOEM.pdf
Restrictions of OEM licensing:

May only be sold with a complete system (PC or Server)
OEM licenses may not be moved or transferred to
another system (even if the hardware dies)

No previous version and re-imaging rights for Office
(Product Activation)
Also, all systems are preloaded from the factory with the same "dummy" key, because these do not go online to activation with Microsoft.  As long as you have a COA key on each PC, that's all that matters.

Okey..:) That is what I am thinking. We have all ready purchased 50 Dell Laptops with OEM. All of them have a COA key. I just wanted to create one Image, like Dell do and use this on all the machines.

So if I use 1 OEM image on all the computers and they alll have a individual  COA Win7 license on them.

I really do not se the problem here...?
The OEM will be using a System Builder version of the installation they can do this as part of their system builder license.

Talk to Microsoft Licensing and see what they say.

Thats the only way you will get the correct "legal" answer.
Talked with microsoft, they sad it works but it is not "legal", so we used an volume version.

Thx for all replys, to clearify this :)
As I suspected.
I quite clearly said this in Comment ID: http:ID:26285557 and therefore object to the question being closed by accepting your own answer.
demazter's first answer should be accepted as the solution