D.Currie said:
I didn't get one either. It's oem, so you'd need an oem key. Maybe in with
the OPK kits they included; I haven't looked through everything yet. But
it's odd that everything else has a key attached.
Hmm, I've got an SP2 install going right now. I just looked through my
packaging and all the misc labels and junk that was included, no sign of
any product key. I just assumed it would accept the keys I was already
provided.
*sigh* Same deal, won't accept any of my keys.
In trying the new SP2 CD (before I discovered my keys don't work), one
machine got to approximately 9% of the install , then "drivers.cab"
failed to copy.
Here's the weird part though, I rebooted, reformatted, put in my
known-good home-built (WinXPsp1 + slipstreamed SP2) CD, it failed at
drivers.cab too. I'm installing WinXPSP1 (from my action pack, same as
was originally installed) and it is installing successfully.
The known-good one has installed several machines before, including the
one I'm using to post this message. It just seems odd that both CDs
would fail at the same file since the disk geometry is undoubtably
different between the home-grown slipstream and Microsoft's release.
Both CDs worked fine on another system though, which is how I got to
test to see that my keys don't work on the action pack one.
Ahh well, the goal was to reinstall the systems, not to install SP2, so
I guess it's all good, only 20-30 minutes wasted trying to get the
stupid OEM CD to install.
I can't say I'm real impressed with their throughness on this update,
according to the documentation I was supposted to get OneNote 2004, what
I got was another OneNote 2003 CD. Also, it said I'm supposed to get
"Office 2003 Pro re-release", and what I got was "Office 2003 Small
Business Edition" (which has one key on the back, instead of the usual 5
keys good for 2 activations each)
On the last updsate I was missing keys for Virtual PC, and I think
something else as well. Plus there was an insert that apologized for
forgetting Outlook BCM in a previous update, and that it was included in
this update. Well, it WAS included in the previous update, and was not
included in the update with the insert.
Does nobody at Microsoft sit down and look at the quarterly updates
before they go out?
Ahhh well.
Now I'm off to get SUS working for the first time. *grrrrrrr*