jordan

Hey Microsoft,

Here is a great idea. If your going to change the ability of Windows to
only accept certain key codes depending on the SP number, why don't you put
the stupid SP number on my CA keycode tag so I know what disk to grab when I
need to do a reinstall on my system or when one of your other programs make
me put the XP disk in the system.

Now that SP2c for XP is out it won't take SP2 codes, nor will SP2 take SP1
codes. Great! Really, how hard is it to add this to the label.

smlunatick

Don't know what you are talking about but most Windows XP Pro CD key
codes work with every SP levels so far (unless the CD Key is part of
the known list of Volumen License keys that are commonly used for
pirated copies.)

ed covney

Think ... "Sharpie" permanent markers!

jordan

No, that is not correct. The SP2C disks that I just got which prompted me to
post this message came with a special bulletin in it specifically stating
that the keycodes of previous versions of XP will not work with this CD and
vice versa. Microsoft has also done this in SP2 because of leaked keys so
Original, SP1 and SP1a keys can only work with those levels. SP2 keys can
only work on SP2, and SP2c keys only work on its version as well.

Now you CAN slipstream SP2 into an original, SP1 or SP1a image and the < SP2
key will work because of a special line in one of the setup files that I do
not want to identify here. BUT that slipstreamed image will not accept the
SP2 or SP2c key because of that special coding in one of the files.

Get a CD with < SP2 and try to use a key from and SP2 CD and you will see.
Vice versa as well.

On Mar 24, 2:44 pm, "Jordan" <n...@here.com> wrote:


Don't know what you are talking about but most Windows XP Pro CD key
codes work with every SP levels so far (unless the CD Key is part of
the known list of Volumen License keys that are commonly used for
pirated copies.)

jordan

So should I deface my computer or the CA tag? Should I also write all the
stuff from all of my other apps all over the computer as well?

Personally I like to keep all my keycodes and information in my auditing
software and not a notebook. But like everything else it only has so many
features. This package tells me its current SP level, not the one it
shipped with. Maybe some others do, but they don't do some of the things I
need.

I am trying to be a good doobee and use all the MS tools like RIS, WSUS and
GPO to manage my network, but I can't understand why the company that is
promoting all these great methods of managing the network is the same one
throwing a wrench into my system.

ed covney

A "sharpie" is a felt tip pen not an etching tool.

I put the code keys on the CDs - that way I never have
a problem matching the tags and the CDs (note: the CDs
have the SP level recorded on them). Capeche?


Depends, the back & bottom of my cases have lots of info
scribbled in with a sharpie on an avery labels. AND, When I
build new system, I write a DVD(rw) with all the necessary
device drivers and tape it to the inside of the case.


Giving your original question I suspect that is not working
out very well for you.

But if you hold your breathe long enough, I'm certain MS
will eventually cave-in to your demands for a more informative
tag! ))

Ed

jordan

One of the problems with the sharpie method is the ever so common situations
now where you do not get media now unless you purchase retail. The last 12
OEM mfg units we got in had no media for Windows XP, Vista, office 2003, nor
office 2007.

I guess I am really more upset that the SP2c Code will not work on a
slipstreamed original or other image. I use RIS to deploy all my systems
since 2000 and all I had to do before was just have one image and when I got
new hardware I would just merge the drive controller into the TXTSETUP.SIF
file, update the ris sif file with the path to the added drivers and I was
off and running and could make every single system no matter what the
hardware have the same software, patches, etc.

Now since SP2 MS almost forces me to have a few images to handle each of the
service packs. I say "almost" because I have developed a little trick to
allow me to do a RIS install and full deployment of all my software via GPO
then install the proper Windows XP keycode after. I don't know if this is
going to work with SP2c now which is the most irritating part.

anteaus

I've also found that some OEM-sticker keys don't work. Period.