Different Windows product numbers for service pack updates ?

Hi Everyone,

I have my original Dell WinXP Sp1a reinstall disk, that was shipped with
my computer , that already had Windows XP Pro installed. And the product key
is found on a sticker on my computer's case.
When I recently used the nlite program, to slipstream my original install
disk, with the SP3 update , I noticed that nlite displayed a different
product key number, for the slipstreamed build.
Which brings me to ask, if I should manually input the original product
key into the slipstreamed build , or does each progressive service pack
update have a different product key number , than prior service pack builds ?

This is very impotent , because if a incorrect product key number is
inputed into the slipstream build , it would fail to reinstall Windows when
needed.
Thanks !
--
your friend,
Larry

"leoliver" <leoliver@discussions.microsoft.com> wrote in message
news:25590774-F43E-4DA4-B6C4-67833DACFAE2@microsoft.com...
>
> Hi Everyone,
>
> I have my original Dell WinXP Sp1a reinstall disk, that was shipped with
> my computer , that already had Windows XP Pro installed. And the product
> key
> is found on a sticker on my computer's case.
> When I recently used the nlite program, to slipstream my original install
> disk, with the SP3 update , I noticed that nlite displayed a different
> product key number, for the slipstreamed build.
> Which brings me to ask, if I should manually input the original product
> key into the slipstreamed build , or does each progressive service pack
> update have a different product key number , than prior service pack
> builds ?
>
> This is very impotent , because if a incorrect product key number is
> inputed into the slipstream build , it would fail to reinstall Windows
> when
> needed.
> Thanks !
> --
> your friend,
> Larry

Use the original product key.

leoliver wrote:
> I have my original Dell WinXP Sp1a reinstall disk, that was
> shipped with my computer , that already had Windows XP Pro
> installed. And the product key is found on a sticker on my
> computer's case. When I recently used the nlite program, to
> slipstream my original install disk, with the SP3 update , I
> noticed that nlite displayed a different product key number, for
> the slipstreamed build. Which brings me to ask, if I should
> manually input the original product
> key into the slipstreamed build , or does each progressive service
> pack update have a different product key number , than prior
> service pack builds ?
>
> This is very impotent , because if a incorrect product key number
> is inputed into the slipstream build , it would fail to reinstall
> Windows when needed.

Slipstreaming a service pack into a given CD should not change the product
key for that CD.

There are known issues with performing a slipstream process (SP3 in
particular) on a Windows Vista machine for a Windows XP CD. My suggestion -
don't do it. Stick to using a Windows XP machine when slipstreaming a
service pack (or the other updates) into a Windows XP installation medium.

More simplified explanation... You start with an original Windows XP RTM
(Gold) version. Sold on the first day Windows XP was ever available to the
public.

- If you make a slipstream copy with SP1a using that CD - it still uses the
same product key it did before.
- If you make a slipstream copy with SP2 using that CD - it still uses the
same product key it did before.
- If you make a slipstream copy with SP2 and all the post-SP2 patches up
until SP3 (non-inclusive) using that CD - it still uses the same product key
it did before.
- If you make a slipstream copy with SP3 using that CD - it still uses the
same product key it did before.

The real question is how you ever saw a product key in the first place if
you were not installing at the time.

There is no connection (other than license type - OEM, VLK, Retail, Upgrade)
between the CD and the product key. The product key is not stored on the
media (unless it is written on the outside via marker or put in a winnt.sif
or unattended.txt fiule or manually put there some other way) - so for you
to have seen a product key at all - that CD would have to have been
previously modified (made into an unattended CD or a text file placed on it
so someone could remember the product key to input without searching for a
sticker/piece of paper, etc.)

Do not mistake Product ID with Product Key. The latter is used when
installing Windows XP. The former is generated partially based on the
hardware installed in the machine.

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

Often OEM PCs such as those from Dell, HP, etc will show a different product
key installed than the one on the COA, this is perfectly normal as they use
an image to load the drive with some type of OEM volume key, use the key
that nlite found, not the key on the sticker.

--

----
Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
How to ask a question http://support.microsoft.com/kb/555375



"leoliver" <leoliver@discussions.microsoft.com> wrote in message
news:25590774-F43E-4DA4-B6C4-67833DACFAE2@microsoft.com...
>
> Hi Everyone,
>
> I have my original Dell WinXP Sp1a reinstall disk, that was shipped with
> my computer , that already had Windows XP Pro installed. And the product
> key
> is found on a sticker on my computer's case.
> When I recently used the nlite program, to slipstream my original install
> disk, with the SP3 update , I noticed that nlite displayed a different
> product key number, for the slipstreamed build.
> Which brings me to ask, if I should manually input the original product
> key into the slipstreamed build , or does each progressive service pack
> update have a different product key number , than prior service pack
> builds ?
>
> This is very impotent , because if a incorrect product key number is
> inputed into the slipstream build , it would fail to reinstall Windows
> when
> needed.
> Thanks !
> --
> your friend,
> Larry

To answer your question : "The real question is how you ever saw a
product key in the first place if you were not installing at the time."

The nlite interface displayed a product key ( 5 sets of 5 digit numbers )
, on it's unattended set-up, general page . The program auto enters the
product key , so the user doesn't have to , during a actual install process .
But the user has to verify the product key numbers are correct before nlite
will make a bootable, slipstreamed iso. file . In my case the numbers were
not . I don't how it came up with the incorrect numbers , but I will manually
enter the correct numbers before I start the .iso build process .
Thanks for answering my question .

--
your friend,
Larry


"Shenan Stanley" wrote:

> leoliver wrote:
> > I have my original Dell WinXP Sp1a reinstall disk, that was
> > shipped with my computer , that already had Windows XP Pro
> > installed. And the product key is found on a sticker on my
> > computer's case. When I recently used the nlite program, to
> > slipstream my original install disk, with the SP3 update , I
> > noticed that nlite displayed a different product key number, for
> > the slipstreamed build. Which brings me to ask, if I should
> > manually input the original product
> > key into the slipstreamed build , or does each progressive service
> > pack update have a different product key number , than prior
> > service pack builds ?
> >
> > This is very impotent , because if a incorrect product key number
> > is inputed into the slipstream build , it would fail to reinstall
> > Windows when needed.
>
> Slipstreaming a service pack into a given CD should not change the product
> key for that CD.
>
> There are known issues with performing a slipstream process (SP3 in
> particular) on a Windows Vista machine for a Windows XP CD. My suggestion -
> don't do it. Stick to using a Windows XP machine when slipstreaming a
> service pack (or the other updates) into a Windows XP installation medium.
>
> More simplified explanation... You start with an original Windows XP RTM
> (Gold) version. Sold on the first day Windows XP was ever available to the
> public.
>
> - If you make a slipstream copy with SP1a using that CD - it still uses the
> same product key it did before.
> - If you make a slipstream copy with SP2 using that CD - it still uses the
> same product key it did before.
> - If you make a slipstream copy with SP2 and all the post-SP2 patches up
> until SP3 (non-inclusive) using that CD - it still uses the same product key
> it did before.
> - If you make a slipstream copy with SP3 using that CD - it still uses the
> same product key it did before.
>
> The real question is how you ever saw a product key in the first place if
> you were not installing at the time.
>
> There is no connection (other than license type - OEM, VLK, Retail, Upgrade)
> between the CD and the product key. The product key is not stored on the
> media (unless it is written on the outside via marker or put in a winnt.sif
> or unattended.txt fiule or manually put there some other way) - so for you
> to have seen a product key at all - that CD would have to have been
> previously modified (made into an unattended CD or a text file placed on it
> so someone could remember the product key to input without searching for a
> sticker/piece of paper, etc.)
>
> Do not mistake Product ID with Product Key. The latter is used when
> installing Windows XP. The former is generated partially based on the
> hardware installed in the machine.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

Now I'm really confused, one answear says don't use the nlite key, one
answear says to use the nlite key ?
--
your friend,
Larry


"David B." wrote:

> Often OEM PCs such as those from Dell, HP, etc will show a different product
> key installed than the one on the COA, this is perfectly normal as they use
> an image to load the drive with some type of OEM volume key, use the key
> that nlite found, not the key on the sticker.
>
> --
>
> ----
> Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
> How to ask a question http://support.microsoft.com/kb/555375
>
>
>
> "leoliver" <leoliver@discussions.microsoft.com> wrote in message
> news:25590774-F43E-4DA4-B6C4-67833DACFAE2@microsoft.com...
> >
> > Hi Everyone,
> >
> > I have my original Dell WinXP Sp1a reinstall disk, that was shipped with
> > my computer , that already had Windows XP Pro installed. And the product
> > key
> > is found on a sticker on my computer's case.
> > When I recently used the nlite program, to slipstream my original install
> > disk, with the SP3 update , I noticed that nlite displayed a different
> > product key number, for the slipstreamed build.
> > Which brings me to ask, if I should manually input the original product
> > key into the slipstreamed build , or does each progressive service pack
> > update have a different product key number , than prior service pack
> > builds ?
> >
> > This is very impotent , because if a incorrect product key number is
> > inputed into the slipstream build , it would fail to reinstall Windows
> > when
> > needed.
> > Thanks !
> > --
> > your friend,
> > Larry
>
>

leoliver wrote:
> Now I'm really confused, one answear says don't use the nlite key,
> one answear says to use the nlite key ?

Whatever key you have on your sticker is your legitimate key.

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

I haven't confirmed this as fact, just going on my experience, but if he
uses the key on the sticker and not the one the original Dell install media
uses, it is very likely he'll lose the Dell pre-activation when he does an
install using the slipstreamed CD he creates.

--

----
Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
How to ask a question http://support.microsoft.com/kb/555375



"leoliver" <leoliver@discussions.microsoft.com> wrote in message
news:C0C2E727-7685-44BF-B0C8-C174B3BC2BB4@microsoft.com...
> Now I'm really confused, one answear says don't use the nlite key, one
> answear says to use the nlite key ?
> --
> your friend,
> Larry
>
>
> "David B." wrote:
>
>> Often OEM PCs such as those from Dell, HP, etc will show a different
>> product
>> key installed than the one on the COA, this is perfectly normal as they
>> use
>> an image to load the drive with some type of OEM volume key, use the key
>> that nlite found, not the key on the sticker.
>>
>> --
>>
>> ----
>> Crosspost, do not multipost http://www.blakjak.demon.co.uk/mul_crss.htm
>> How to ask a question http://support.microsoft.com/kb/555375
>>
>>
>>
>> "leoliver" <leoliver@discussions.microsoft.com> wrote in message
>> news:25590774-F43E-4DA4-B6C4-67833DACFAE2@microsoft.com...
>> >
>> > Hi Everyone,
>> >
>> > I have my original Dell WinXP Sp1a reinstall disk, that was shipped
>> > with
>> > my computer , that already had Windows XP Pro installed. And the
>> > product
>> > key
>> > is found on a sticker on my computer's case.
>> > When I recently used the nlite program, to slipstream my original
>> > install
>> > disk, with the SP3 update , I noticed that nlite displayed a different
>> > product key number, for the slipstreamed build.
>> > Which brings me to ask, if I should manually input the original
>> > product
>> > key into the slipstreamed build , or does each progressive service pack
>> > update have a different product key number , than prior service pack
>> > builds ?
>> >
>> > This is very impotent , because if a incorrect product key number is
>> > inputed into the slipstream build , it would fail to reinstall Windows
>> > when
>> > needed.
>> > Thanks !
>> > --
>> > your friend,
>> > Larry
>>
>>