Re: Cloning OEM XP PC's?



Kerry Brown wrote:


"R. McCarty" <PcEngWork-NoSpam_@xxxxxxxxxxxxxx> kirjoitti
viestissä:%23io$SXNIGHA.2680@xxxxxxxxxxxxxxxxxxxxxxx
You've run up against once of those openings in a process that is
now plugged up. There is a problem with the unauthorized use of
Product Keys on OEM PCs. While the license key is valid, it is not
used at the factory.There the OEMs use a master image (Different
Product Key)
and then apply the individual license sticker to the case or
underside of the notebook. To stop this use of the OEM keys,
Microsoft has
the product activation disabled - forcing a phone call to
activate. The major OEMs (HP, Dell & Gateway) may be affected but
seems to
vary between vendors. A Volume License version would be a better
choice

"William Stokes" <will@xxxxxxxxxxxxx> wrote in message
news:OUW4HRNIGHA.2948@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I am trying to clone XP SP2 pc's that are purchased from HP with
Windows XP OEM licence. (Atleast it think so because there's the
-OEM- part in the product ID.)
All PC's have the XP product key sticker with the original
product key in it.

After image restore (with Ghost 8.3 and Sysprep run) the XP
want's me to activate the it. When I try activate it with the
original product key from the sticker the key is invalid!

Why is that? Do one need to have Volume Licenses in order to
clone XP pc's? Is there some way to get rid of the whole
activation when cloning several pc's? Can OEM XP's be cloned at
all?



Thanks
-Will

Sorry for the snipped reference, but for some reason (?) google
wouldn't let me reply/post to the OP's append.

I ran into this exact issue with the small lab of 25 computers I am
trying to set up for the school my daughter attends. Here's the link
to the topic where I was asking about the issues with Sysprep and the
"three try" limit:

http://snipurl.com/nepo

Anyway, I found that the limit is true, and Sysprep seems to be
shutting off access to the internet, thus requiring telephone
activation. I can't believe that I'm sitting in a room full of 25
computers, all with valid product license decals on them -- and
minisetup asks for the license key -- but that's not good enough. I
now have to make 25 six-minute phone calls keying in a 42 digit number
two times for each machine. That's 2.5 hours of time wasted.

There is no way we are spending money on a volume license when we
already have valid licenses on each OEM machine. I think MS really
missed the boat here and put a whole lot of folks who do this
small-scale customization/cloning of a few machines for small offices
or labs at a real disadvantage.

-Chris

.



Relevant Pages

  • Re: Installing Win XP Pro (just use another product key)
    ... machine - I assume this is an OEM license). ... The recovery disks that were supplied with the laptop were unable ... I have a genuine OEM Win XP Pro SP2 disc (from when I built my ... when I was asked to input the product key I ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Emergency Installation of XP - How to Solve Activation Problem
    ... product key sticker is still on some of these donated computers, ... Professional, Retail vs. OEM, and Full vs. Upgrade. ... you can move the installation ... license ties it permanently to the first computer it's installed on. ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: No OS disk with purch refurb laptop
    ... to install with, and then register/validate with this product key. ... supply the product key of my own license during ... then you will need an OEM Windows distribution to install from. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: No OS disk with purch refurb laptop
    ... but I am not sure if the license is transferrable. ... then you will need an OEM Windows distribution to install from. ... If your product key is on a sticker on the machine itself - there's a VERY ...
    (microsoft.public.windowsxp.setup_deployment)
  • RE: prompt new owner to enter XP product key ?
    ... Investigate using sysprep with Home Edition. ... However since you are an OEM, you may want to investigate Microsoft's OEM ... > Is it possible to remove reference to the product key from ...
    (microsoft.public.windowsxp.setup_deployment)