Volume License Product Key Invalid with ghosted OEM software?!

[Blaine]

I have a VLP for XP Pro but recently received a number of OEM laptops (all
the same type). I configured one of the OEM laptops the way I needed it, ran
Setupmgr to configure the Answer File and then ran Sysprep with the
mini-setup option. In the Answer file I used the VLP Key. I then ghosted the
system. After Ghosting the system I deployed the image to a laptop and
started the setup, which ran fine until it hit the License Key portion,
stating that the key was invalid. I verified that I had typed it in
correctly, retyping a number of times, but received the same error. I then
tried the OEM key and received the same error.

By reading through some of the earlier posts I would assume that using the
VLP with the OEM software won't work. Am I correct in assuming this? This
used to work fine with Win2K systems. Is there a proper way to ghost these
OEM systems so that I don't have to configure each one?

Thanks much...

 

[Mike Brannigan [MSFT]]

Your assumption is correct - you may not use an VLKey with an OEM product.
OEM builds and keys are tied to a single PC - you cannot ghost an OEM image
and install to another PC. They will need to be built individually. Unless
you cab agree terms to replace them with your VL build, contact your OEM
and your Microsoft licensing provider for more information and
clarification.

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

 

[Blaine]

FRAQ!
Thanks for the clarification.

~ Blaine

Your assumption is correct - you may not use an VLKey with an OEM product.
OEM builds and keys are tied to a single PC - you cannot ghost an OEM image
and install to another PC. They will need to be built individually. Unless
you cab agree terms to replace them with your VL build, contact your OEM
and your Microsoft licensing provider for more information and
clarification.

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

 

[Bruce Chambers]

Greetings --

You're correct.

Product Keys are bound to the specific type and language of
CD/license (OEM, Volume, retail, full, or Upgrade) with which they are
purchased. For example, a WinXP Home OEM Product Key won't work for
any retail version of WinXP Home, or for any version of WinXP Pro, and
vice versa. An upgrade's Product Key cannot be used with a full
version CD, and vice versa. An OEM Product Key will not work to
install a retail product. An Italian Product Key will not work with
an English CD. Product Keys and CDs cannot be mixed & matched.


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH

 

[Adam Kuhn]

I've been looking for an answer to this question for the
last couple of days, and couldn't even get MS to provide a
solution. After building a golden image off of a factory
build of WinXP on a IBM Thinkpad X31, I'm stuck with a
retail oem version of XP that's not deployable with my 30
new laptops.

Here's the real question: Does anyone think that one can
use the MS Volume License Media and Activation Key to
REINSTALL OVER the factory OEM build to turn the image
into a deployable version of XP as it's meant with Volume
Licensing? Or, do I have to start all over with a fresh
install using the MS XP Media and wipe the oem version
clean off the unit?

 

[Mike Brannigan [MSFT]]

Adam,

The first thing to do is contact the OEM and your Microsoft Volume Licensing
sales rep to discuss if the replacement of the OEM license with one of your
VL licenses can be done without incurring any additional licensing cost to
yourself, as may be the case as it may be seen that each new VL license you
deploy requires you to pay for that license, or you may be able to just
"swap" out the OEM build with your VL build without this additional cost.

Once you have this sorted you will then need to prepare a new image based on
theVL build on a clean machine. You can then image and deploy this VL Media
build.
The first step above is the most important to ensure you are not in
violation of your Volume Licensing contract etc.

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

 

[Bruce Chambers]

Greetings --

I'd certainly start over, using the Volume License Media. The
very first thing I do when any machine with an OEM installation
arrives is format the hard drive to remove all of the extraneous
nonsense with which OEMs fill hard drives.

Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH

 

[Adam Kuhn]

I hear you on that. Although, I felt IBM did a good job on the think pads.
Now that I know I have to do it (after building the image that I now have to
wipe) I've resigned myself to doing it and I don't think it will be too bad.
The key will be backing up the c:\drivers directory first and then putting
it back after the initial install. Plus, IBM has a nice driver installation
package that may allow me to install all the drivers at once.

Thanks for your help.

 

[Mike Brannigan [MSFT]]

Adam,

Remember to check with your Volume Licensing rep and the OEM if you can
replace the OEM license with a VL one at no cost (as per my other posts)

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

 

[Bruce Chambers]

Greetings --

You're welcome.

Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH

 

[Adam Kuhn]

Thanks for that tip. Unfortunately, I don't handle licensing for my company
(about 200 employees) but I have asked my manager to do just that.