OEM Release vs. SP1 vs. SP2 Product Key issue

[Jordan]

I have about 50 PCs in a product test department that use the PCs with some
special software and hardware to test our products. We are revamping the
whole setup so the easiest thing to do would be to just format the computers
and use my RIS setup to reinstall windows and use Group Policies to
distribute the new software to the computers. I could have the whole
department done in a few hours except for one issue.....

The computers were purchased at various times over the past few years and
all came with OEM versions of Windows. Some with straight XP, some with Sp1
or 1a, and some with SP2. YES I will abide by the OEM agreement and only
use that product key on the computer on which it came, but the problem is:

1. If I try to install XP SP2 on all computers, the release, Sp1 and Sp1a
keys do not work.
2. If I slipstream SP2 into the release copy, the Sp1x keys and Sp2 do not
work.
3. If I slipstream SP2 into Sp1x, the release and SP2 keys do not work.

It would be very irritating have to have 3 versions of XP Pro SP2 (SP2,
release slipstreamed to SP2, SP1x slipstreamed to SP2) on my RIS server and
have to maintain them so is there some way to be able to use all my
legitimate keys on just one image?

 

[Shenan Stanley]

I have about 50 PCs in a product test department that use the PCs
with some special software and hardware to test our products. We
are revamping the whole setup so the easiest thing to do would be
to just format the computers and use my RIS setup to reinstall
windows and use Group Policies to distribute the new software to
the computers. I could have the whole department done in a few
hours except for one issue.....
The computers were purchased at various times over the past few
years and all came with OEM versions of Windows. Some with
straight XP, some with Sp1 or 1a, and some with SP2. YES I will
abide by the OEM agreement and only use that product key on the
computer on which it came, but the problem is:
1. If I try to install XP SP2 on all computers, the release, Sp1
and Sp1a keys do not work.
2. If I slipstream SP2 into the release copy, the Sp1x keys and Sp2
do not work.
3. If I slipstream SP2 into Sp1x, the release and SP2 keys do not
work.
It would be very irritating have to have 3 versions of XP Pro SP2
(SP2, release slipstreamed to SP2, SP1x slipstreamed to SP2) on my
RIS server and have to maintain them so is there some way to be
able to use all my legitimate keys on just one image?

If 1,2 or 3 you have given above are true - something must be going wrong
with your slipstream/integration. There is only one SP2 where Windows XP
OEM/RETAIL/MSDN/VOLUME licenses are concerned. Integrating the service pack
and subsequent critical updates into your installation media should *not*
effect the product key in any way. However - you should make sure you have
removed the OEM's modifications (winnt.sif/unattend.txt) before you begin -
although in truth - it should not matter.

Also - in a situation such as yours - it may be WELL worth the cost to look
into Volume Licensing. It would greatly simplify... everything.

 

[Jordan]

I did some digging and I found out that the problem lies in the SETUPP.INI
file on the different Windows XP disks. This file is what tells Setup
whether or not it is a OEM, Retail, or Upgrade CD and in the case of the OEM
whether or not it is SP2 or less. This then determines what key can be used
during setup.

SP1 and SP1a OEM CD has the following in the SETUPP.INI file:

[Pid]
ExtraData=786F687170637175716954806365EF
Pid=55274OEM


While SP2 OEM has the following in the SETUPP.INI file:

[Pid]
ExtraData=786F687170637175716954806365EF
Pid=76487OEM

When you install Windows it makes up the ProductId of following registry
keys based on the Pid in the SETUPP.INI file. For SP1x the Product ID is
55274-OEM-xxxxxxx-xxxxx and for SP2 it is 76487-OEM-xxxxxxx-xxxxx:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductId
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ProductId
HKLM\SOFTWARE\Microsoft\Internet Explorer\Registration\ProductId

In order to get this to work with RIS I just use my Windows XP2 CD image and
just used the SIF answer file to use the same CD key for initial setup.
Naturally if you go to activate 50 computers with the same key it will bomb
so you have to use the instructions in the MS Article to change to the key
code for that computer:

http://support.microsoft.com/kb/328874

Now they question is, what to do about the fact that when you try to change
the key and enter the SP1x key code using the above article. If you use any
of the listed MS methods your SP1x keycode will be denied or generate an
error if you use the vbscript if you did what I did and installed using an
SP2 image. You need to first change the Product ID codes in the 3 registry
keys to match the right version of Windows service pack keycode you are
trying to enter. I have successfully tested this by manually changing the 3
keys listed above to 55274-OEM-xxxxxxx-xxxxx after fully installing Windows.
The only thing I need to do now is to see if I can write a VB script to
modify these entries quickly.

 

[Mario Schmidt]

Also - in a situation such as yours - it may be WELL worth the cost to look
into Volume Licensing. It would greatly simplify... everything.

When he already has OEM licenses for all the computers, why buy
additional volume license? Throw money in Microsofts mouth? No, thanks.