"sai.an" has successfully cloned his installed WinXP OS onto another
HD, and it tests out OK on the original system. Now he wants to
transfer the HD that contains the clone into a similar system, for which
he has purchased another license. What is the procedure, and will
there be any problems? I would expect that he will have to at least
re-activate the clone OS because it will see the change in CPU and
DRAM. Can he apply his 2nd license's confirmation ID at this point?
Should he even bother to do that? Here is what he said:

> - machine B has a slightly different environment (same mobo as A,
> but different version of Athlon XP, different DRAM)
> - for machine B I have already acquired a supplementary XP Pro
> license, and in the course of my previous "experiments" I managed
> to go far enough for activating this product (which means that my
> machine B configuration had generated an equipment ID which has
> enabled me to obtain from Microsoft a Confirmation ID) ; I have
> kept on a USB key a copy of the last wpa.bak and wpa.dbl files
> that could be obtained from machine B.

*TimDaniels*

Timothy Daniels wrote:
> "sai.an" has successfully cloned his installed WinXP OS onto another
> HD, and it tests out OK on the original system. Now he wants to
> transfer the HD that contains the clone into a similar system, for
> which he has purchased another license. What is the procedure, and
> will there be any problems? I would expect that he will have to at
> least re-activate the clone OS because it will see the change in
> CPU and DRAM. Can he apply his 2nd license's confirmation ID at
> this point? Should he even bother to do that? Here is what he said:
>
>> - machine B has a slightly different environment (same mobo as A,
>> but different version of Athlon XP, different DRAM)
>> - for machine B I have already acquired a supplementary XP Pro
>> license, and in the course of my previous "experiments" I
>> managed to go far enough for activating this product (which
>> means that my machine B configuration had generated an
>> equipment ID which has enabled me to obtain from Microsoft a
>> Confirmation ID) ; I have kept on a USB key a copy of the last
>> wpa.bak and wpa.dbl files that could be obtained from machine B.
>
> *TimDaniels*

Assuming RETAIL/VOLUME licenses...

Put the drive in the other machine...
Perform a repair installation for the different hardware...
(and change the key if needed.)
Activate.
Utilize.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

"Shenan Stanley" wrote:
> Timothy Daniels wrote:
>> "sai.an" has successfully cloned his installed WinXP OS onto another
>> HD, and it tests out OK on the original system. Now he wants to
>> transfer the HD that contains the clone into a similar system, for
>> which he has purchased another license. What is the procedure, and
>> will there be any problems? I would expect that he will have to at
>> least re-activate the clone OS because it will see the change in
>> CPU and DRAM. Can he apply his 2nd license's confirmation ID at
>> this point? Should he even bother to do that? Here is what he said:
>>
>>> - machine B has a slightly different environment (same mobo as A,
>>> but different version of Athlon XP, different DRAM)
>>> - for machine B I have already acquired a supplementary XP Pro
>>> license, and in the course of my previous "experiments" I
>>> managed to go far enough for activating this product (which
>>> means that my machine B configuration had generated an
>>> equipment ID which has enabled me to obtain from Microsoft a
>>> Confirmation ID) ; I have kept on a USB key a copy of the last
>>> wpa.bak and wpa.dbl files that could be obtained from machine B.
>>
>> *TimDaniels*
>
> Assuming RETAIL/VOLUME licenses...
>
> Put the drive in the other machine...
> Perform a repair installation for the different hardware...
> (and change the key if needed.)
> Activate.
> Utilize.
>
> --
> Shenan Stanley
> MS-MVP


When you say "change the key", do you mean to input
the key from the newly purchased installation CD?

According to this website:
http://www.michaelstevenstech.com/XPrepairinstall.htm,
the Repair Install uses the WinXP Installation CD. Does
it matter whether one uses the CD for the original OS
(the one cloned) or the CD for the newly purchased OS?

Since the Original Poster has the wpa files from an earlier
installation from his new OS (that has been wiped), will
those wpa.dbl and wpa.bak files activate the clone OS
if the new OS's CD was used for the Repair Install?
Or do they require that the OS came from the new CD?

*TimDaniels*

Timothy Daniels wrote:
> "Shenan Stanley" wrote:
>> Timothy Daniels wrote:
>>> "sai.an" has successfully cloned his installed WinXP OS onto
>>> another HD, and it tests out OK on the original system. Now he
>>> wants to transfer the HD that contains the clone into a similar
>>> system, for which he has purchased another license. What is the
>>> procedure, and will there be any problems? I would expect that
>>> he will have to at least re-activate the clone OS because it will
>>> see the change in CPU and DRAM. Can he apply his 2nd license's
>>> confirmation ID at this point? Should he even bother to do that? Here is
>>> what he said:
>>>> - machine B has a slightly different environment (same mobo as A,
>>>> but different version of Athlon XP, different DRAM)
>>>> - for machine B I have already acquired a supplementary XP Pro
>>>> license, and in the course of my previous "experiments" I
>>>> managed to go far enough for activating this product (which
>>>> means that my machine B configuration had generated an
>>>> equipment ID which has enabled me to obtain from Microsoft a
>>>> Confirmation ID) ; I have kept on a USB key a copy of the last
>>>> wpa.bak and wpa.dbl files that could be obtained from machine
>>>> B.
>>>
>>> *TimDaniels*
>>
>> Assuming RETAIL/VOLUME licenses...
>>
>> Put the drive in the other machine...
>> Perform a repair installation for the different hardware...
>> (and change the key if needed.)
>> Activate.
>> Utilize.
>>
>> --
>> Shenan Stanley
>> MS-MVP
>
>
> When you say "change the key", do you mean to input
> the key from the newly purchased installation CD?
>
> According to this website:
> http://www.michaelstevenstech.com/XPrepairinstall.htm,
> the Repair Install uses the WinXP Installation CD. Does
> it matter whether one uses the CD for the original OS
> (the one cloned) or the CD for the newly purchased OS?
>
> Since the Original Poster has the wpa files from an earlier
> installation from his new OS (that has been wiped), will
> those wpa.dbl and wpa.bak files activate the clone OS
> if the new OS's CD was used for the Repair Install?
> Or do they require that the OS came from the new CD?

You can use a repair installation to change the product key you used.

You can also use this tool:
The Genuine Advantage Product Key Update Tool is only valid for
users attempting to change their current non-genuine Product Key
to a genuine COA sticker or genuine Product Key - all without a reinstall!
http://go.microsoft.com/fwlink/?Link...46&clcid=0x409

The repair install *is* a necessity in this case because they are changing
hardware. They *might* get lucky and the chipset/etc is the same - but it's
just not worth it - repair install makes sure everything is correct.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

"Shenan Stanley" wrote:
> Timothy Daniels wrote:
>> "Shenan Stanley" wrote:
>>> Timothy Daniels wrote:
>>>> "sai.an" has successfully cloned his installed WinXP OS onto
>>>> another HD, and it tests out OK on the original system. Now he
>>>> wants to transfer the HD that contains the clone into a similar
>>>> system, for which he has purchased another license. What is the
>>>> procedure, and will there be any problems? I would expect that
>>>> he will have to at least re-activate the clone OS because it will
>>>> see the change in CPU and DRAM. Can he apply his 2nd license's
>>>> confirmation ID at this point? Should he even bother to do that? Here is
>>>> what he said:
>>>>> - machine B has a slightly different environment (same mobo as A,
>>>>> but different version of Athlon XP, different DRAM)
>>>>> - for machine B I have already acquired a supplementary XP Pro
>>>>> license, and in the course of my previous "experiments" I
>>>>> managed to go far enough for activating this product (which
>>>>> means that my machine B configuration had generated an
>>>>> equipment ID which has enabled me to obtain from Microsoft a
>>>>> Confirmation ID) ; I have kept on a USB key a copy of the last
>>>>> wpa.bak and wpa.dbl files that could be obtained from machine
>>>>> B.
>>>>
>>>> *TimDaniels*
>>>
>>> Assuming RETAIL/VOLUME licenses...
>>>
>>> Put the drive in the other machine...
>>> Perform a repair installation for the different hardware...
>>> (and change the key if needed.)
>>> Activate.
>>> Utilize.
>>>
>>> --
>>> Shenan Stanley
>>> MS-MVP
>>
>>
>> When you say "change the key", do you mean to input
>> the key from the newly purchased installation CD?
>>
>> According to this website:
>> http://www.michaelstevenstech.com/XPrepairinstall.htm,
>> the Repair Install uses the WinXP Installation CD. Does
>> it matter whether one uses the CD for the original OS
>> (the one cloned) or the CD for the newly purchased OS?
>>
>> Since the Original Poster has the wpa files from an earlier
>> installation from his new OS (that has been wiped), will
>> those wpa.dbl and wpa.bak files activate the clone OS
>> if the new OS's CD was used for the Repair Install?
>> Or do they require that the OS came from the new CD?
>
> You can use a repair installation to change the product key you used.
>
> You can also use this tool:
> The Genuine Advantage Product Key Update Tool is only valid for
> users attempting to change their current non-genuine Product Key
> to a genuine COA sticker or genuine Product Key - all without a reinstall!
> http://go.microsoft.com/fwlink/?Link...46&clcid=0x409
>
> The repair install *is* a necessity in this case because they are changing
> hardware. They *might* get lucky and the chipset/etc is the same - but it's
> just not worth it - repair install makes sure everything is correct.
>
> --
> Shenan Stanley
> MS-MVP


Interesting. And does the CD used for the Repair Install have to be
the one used to install the original OS, or the newly purchased OS,
or does it not matter?

*TimDaniels*

Timothy Daniels wrote:
> "Shenan Stanley" wrote:
>> Timothy Daniels wrote:
>>> "Shenan Stanley" wrote:
>>>> Timothy Daniels wrote:
>>>>> "sai.an" has successfully cloned his installed WinXP OS onto
>>>>> another HD, and it tests out OK on the original system. Now he
>>>>> wants to transfer the HD that contains the clone into a similar
>>>>> system, for which he has purchased another license. What is the
>>>>> procedure, and will there be any problems? I would expect that
>>>>> he will have to at least re-activate the clone OS because it
>>>>> will see the change in CPU and DRAM. Can he apply his 2nd license's
>>>>> confirmation ID at this point? Should he even bother to do
>>>>> that? Here is what he said:
>>>>>> - machine B has a slightly different environment (same mobo as
>>>>>> A, but different version of Athlon XP, different DRAM)
>>>>>> - for machine B I have already acquired a supplementary XP Pro
>>>>>> license, and in the course of my previous "experiments" I
>>>>>> managed to go far enough for activating this product (which
>>>>>> means that my machine B configuration had generated an
>>>>>> equipment ID which has enabled me to obtain from Microsoft a
>>>>>> Confirmation ID) ; I have kept on a USB key a copy of the
>>>>>> last wpa.bak and wpa.dbl files that could be obtained from
>>>>>> machine B.
>>>>>
>>>>> *TimDaniels*
>>>>
>>>> Assuming RETAIL/VOLUME licenses...
>>>>
>>>> Put the drive in the other machine...
>>>> Perform a repair installation for the different hardware...
>>>> (and change the key if needed.)
>>>> Activate.
>>>> Utilize.
>>>>
>>>> --
>>>> Shenan Stanley
>>>> MS-MVP
>>>
>>>
>>> When you say "change the key", do you mean to input
>>> the key from the newly purchased installation CD?
>>>
>>> According to this website:
>>> http://www.michaelstevenstech.com/XPrepairinstall.htm,
>>> the Repair Install uses the WinXP Installation CD. Does
>>> it matter whether one uses the CD for the original OS
>>> (the one cloned) or the CD for the newly purchased OS?
>>>
>>> Since the Original Poster has the wpa files from an earlier
>>> installation from his new OS (that has been wiped), will
>>> those wpa.dbl and wpa.bak files activate the clone OS
>>> if the new OS's CD was used for the Repair Install?
>>> Or do they require that the OS came from the new CD?
>>
>> You can use a repair installation to change the product key you
>> used. You can also use this tool:
>> The Genuine Advantage Product Key Update Tool is only valid for
>> users attempting to change their current non-genuine Product Key
>> to a genuine COA sticker or genuine Product Key - all without a
>> reinstall! http://go.microsoft.com/fwlink/?Link...46&clcid=0x409
>>
>> The repair install *is* a necessity in this case because they are
>> changing hardware. They *might* get lucky and the chipset/etc is
>> the same - but it's just not worth it - repair install makes sure
>> everything is correct. --
>> Shenan Stanley
>> MS-MVP
>
>
> Interesting. And does the CD used for the Repair Install
> have to be the one used to install the original OS, or the
> newly purchased OS, or does it not matter?

The CD must be of the same *type* as the new product license.
OEM, Retail, etc...

Looks like they did get lucky and the hardware *was* practically the same -
so it was not necessary to repair install.
The link above may help the OP (from original thread) change the product key
if needed.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

"Shenan Stanley" wrote:
> Timothy Daniels wrote:
>> "Shenan Stanley" wrote:
>>> You can use a repair installation to change the product key you
>>> used. You can also use this tool:
>>> The Genuine Advantage Product Key Update Tool is only valid for
>>> users attempting to change their current non-genuine Product Key
>>> to a genuine COA sticker or genuine Product Key - all without a
>>> reinstall! http://go.microsoft.com/fwlink/?Link...46&clcid=0x409
>>>
>>> The repair install *is* a necessity in this case because they are
>>> changing hardware. They *might* get lucky and the chipset/etc is
>>> the same - but it's just not worth it - repair install makes sure
>>> everything is correct. --
>>> Shenan Stanley
>>> MS-MVP
>>
>>
>> Interesting. And does the CD used for the Repair Install
>> have to be the one used to install the original OS, or the
>> newly purchased OS, or does it not matter?
>
> The CD must be of the same *type* as the new product license.
> OEM, Retail, etc...
>
> Looks like they did get lucky and the hardware *was* practically
> the same - so it was not necessary to repair install.
> The link above may help the OP (from original thread) change the
> product key if needed.
>
> --
> Shenan Stanley
> MS-MVP


Thanks, Shenan.

*TimDaniels*