Activation stinks because I can't reinstall....

[Jordan]

"Since you get your systems from a local vendor If they assemble them you
could request they place the sticker inside the case."

Oh Yeah! Read Section 8 of the OEM System Builders License.
============================
http://oem.microsoft.com/downloads/sbLicense2004/English_SB_License.pdf

8. CERTIFICATE OF AUTHENTICITY (COA) LABEL/PROOF OF LICENSE (POL) LABEL. If
the individual software license includes a COA or combination COA/POL label,
the system builder who installs the individual software license must attach
the COA or combination COA/POL label, as applicable, to the outside of the
fully assembled computer system case in an easily accessible location.
============================

Notice how it says OUTSIDE and in an EASILY ACCESSIBLE LOCATION. Now maybe
you should finally admit that you were wrong for making stupid comments
about me not knowing what I am talking about now that it has been made clear
in B&W that you don't know the first thing about what you are talking about.

As for integrating the SP into the original install what don't you
understand????? I am still in the same boat because no matter what version
I patch to be up to the latest, that unpatched version to start must be the
same as the installed version on the computer getting the inplace upgrade.
That can be one of 4 versions of the hundred CDs that I have now.

Also, the hardware, etc have NOTHING to do with the OEM CD that ships from
MS. You can use any standard OEM cd no matter what the service pack to do a
"fresh" install and at no time will the hardware cause any invalid key error
so again you don't know what you are talking about.

You only get a error on hardware if you use a "Recovery CD" configured by
Dell, Sony, etc. The Recovery CD will check the hardware match prior to
installing because this is a copy of the shipped image. It is not an
install.

It wasn't this way in NT 4 or in Windows 2000. I could use a 2000 SPx
install to reinstall a system that shipped with any previous service pack
without a problem and this

 

[Bob I]

Bummer, suggest you try another line of work, this one is more than you
can manage.

"Since you get your systems from a local vendor If they assemble them you
could request they place the sticker inside the case."

Oh Yeah! Read Section 8 of the OEM System Builders License.

<<BIG SNIP>>

 

[Jordan]

More than who can manage???

Bummer, suggest you try another line of work, this one is more than you
can manage.



<<BIG SNIP>>

 

[Jordan]

I guess the message that the MVPs send here is that when MS has a stupid
policy, don't complain because you get ganged up on and insulted.

Why should I know what the exact "installed" SP version when most of the
asset tracking software does not bother to have a field for that. I have
access to SDS Help desk, BridgeTrak and a few others and all of them have
fields for the CURRENT Service Pack. S.O.P. for most companies is to check
the PC when it comes in and move it up to the CURRENT patches and record
that it was done. Also record any license numbers. None of the packages
have any indication on what the original installed SPs was.

All the Inventory software shows Current MAC, Current Printer, Current Video
card, Current Drivers, Current, Current, Current, Current, Current, Current,
Current, Current, etc. There are events for updating items, but even the
events only have the "To" versions for updates, not the "From" listed.

You guys are being a bunch of jerks just because someone dares to point out
something stupid that MS has done. I have been an MCSE for over 8 years, a
partner for about 5 now, and using their products almost exclusively for
about 10 or 11 years now and when they do something stupid I have every
right to point out how stupid it is if I feel like it.

It is STUPID for them to have the codes right on the computers in an easily
accessible place for all the world to see rather than leave them on the CDs
like before. It is also STUPID that they went out of their way to make it
so I cannot install SP2 with my valid Release, SP1, or SP1a key.

I know that I can find at least 100 XP licenses numbers on the Internet
right now if I wanted to. How do you think they got there? Do you think it
is the System Administrators putting them up there? Its dead beat employees
that now have full access to all the software keys the company has because
we have to stick them in an easily accessible place per MS instructions (OEM
System Builders License Section 8).

 

[Jordan]

The problem is not with XP itself. It's the way MS chose to make it so your
CD key would not work on different Service Pack levels. It wasn't this way
in 2000 or in NT and they did not even bother to document it either.

In the FAQs that you see on MS about installing SP2 they only mention that
they have done things to disrupt codes that have been invalidated because
they were leaked. The did not say that they were going to remove the
ability to do things like in place upgrades with the latest Service Pack
patched CDs even if you key is still valid but came on Release, SP1 or SP1a.

There's no reason for it and it just make Sys Admin's jobs more difficult.

 

[Jupiter Jones [MVP]]

Jordan;
Whether Microsoft could have a better system or not is a different matter.
However an "MCSE for over 8 years..." should know all about this and would
have taken steps to identify and protect the property.

You or your companies failure to maintain adequate inventories of you assets
could not have been helped unless someone came in there and properly marked
and stored your assets.
That is what your organization needed to do.
No matter how the computer is or is not marked or labelled will not change
your organizations asset control.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar/

I guess the message that the MVPs send here is that when MS has a stupid
policy, don't complain because you get ganged up on and insulted.

Why should I know what the exact "installed" SP version when most of the
asset tracking software does not bother to have a field for that. I have
access to SDS Help desk, BridgeTrak and a few others and all of them have
fields for the CURRENT Service Pack. S.O.P. for most companies is to
check the PC when it comes in and move it up to the CURRENT patches and
record that it was done. Also record any license numbers. None of the
packages have any indication on what the original installed SPs was.

All the Inventory software shows Current MAC, Current Printer, Current
Video card, Current Drivers, Current, Current, Current, Current, Current,
Current, Current, Current, etc. There are events for updating items, but
even the events only have the "To" versions for updates, not the "From"
listed.

You guys are being a bunch of jerks just because someone dares to point
out something stupid that MS has done. I have been an MCSE for over 8
years, a partner for about 5 now, and using their products almost
exclusively for about 10 or 11 years now and when they do something stupid
I have every right to point out how stupid it is if I feel like it.

It is STUPID for them to have the codes right on the computers in an
easily accessible place for all the world to see rather than leave them on
the CDs like before. It is also STUPID that they went out of their way to
make it so I cannot install SP2 with my valid Release, SP1, or SP1a key.

I know that I can find at least 100 XP licenses numbers on the Internet
right now if I wanted to. How do you think they got there? Do you think
it is the System Administrators putting them up there? Its dead beat
employees that now have full access to all the software keys the company
has because we have to stick them in an easily accessible place per MS
instructions (OEM System Builders License Section 8).

 

[Torgeir Bakken \(MVP\)]

The problem is not with XP itself. It's the way MS chose to make it so your
CD key would not work on different Service Pack levels. It wasn't this way
in 2000 or in NT and they did not even bother to document it either.

In the FAQs that you see on MS about installing SP2 they only mention that
they have done things to disrupt codes that have been invalidated because
they were leaked. The did not say that they were going to remove the
ability to do things like in place upgrades with the latest Service Pack
patched CDs even if you key is still valid but came on Release, SP1 or SP1a.

There's no reason for it and it just make Sys Admin's jobs more difficult.

Hi

Your assumption is incorrect, the CD key is *not* connected to the
service pack level on the CD in *any* way (disregarding invalided
pirated keys). SP2 is not the cause of your problem.

The CD key is connected to what *type* of OS license you have on the
CD (Generic OEM, Branded OEM, Retail, Volume License, MSDN etc.).

Using the CD key with the wrong type of OS license type will make the
OS installation fail.

 

[Richard Urban]

Excuse me!

You are beating a dead horse here.

I have taken my original Windows XP retail CD and slipstreamed SP1 into it.
I then install with the original key.

I then take the original CD and slipstream SP2 into it. I can STILL install
with the original install key.

What is your problem - other than you have an aptitude for getting various
versions of Windows XP, and their install keys, mixed up. YOUR PROBLEM - NOT
MICROSOFT'S!

Now, I also have a few various Windows XP Home retail CD's. It is up to ME -
and only me - to make sure I don't try to install XP Professional with one
of the Home install keys. It is up to ME to keep my records sorted to make
certain that this doesn't occur.

It is also up to YOU to do the same for all computers and CD's under YOUR
care.

Don't whine because you are not up to the task. Maybe your company should
hire someone who can perform as you are in way over your capabilities!


--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you thought you know,
You would realize that you don't know what you thought you knew!

 

[Ken Blake]

In

I guess the message that the MVPs send here is that when MS has
a
stupid policy, don't complain because you get ganged up on and
insulted.

I'm not the MVP you were replying to, but here's *my* message:
Microsoft undoubtedly has many policies that I disagree with. But
if you don't like a Microsoft policy, a peer-to-peer support
newsgroup like this one is not the place to complain about it--it
does no good, it creates ill-will, and by increasing the traffic
here it makes it harder for those looking for help to get it.

 

[Jordan]

That is an excellent, well thought, simple point and you are absolutely
correct. I as sorry you have to be bothered by all of this. It is
unfortunate that the "professionals" here cannot act professionally.

I don't think that my original post was out of line even though it did
complain a little but that is no reason for MVPs to be insulting. I only
respond because of the ignorant insults about my abilities.

 

[Jupiter Jones [MVP]]

Jordan;
If you have suggestions for Microsoft, this is not the place since Microsoft
does not officially monitor these newsgroups.
When Microsoft is here, it is on their own time.

Here are a few ways to contact Microsoft about suggestions:
http://support.microsoft.com/?kbid=114491

http://register.microsoft.com/mswis...=/isapi/gomscom.asp?target=/mswish/thanks.htm

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar/

I guess the message that the MVPs send here is that when MS has a stupid
policy, don't complain because you get ganged up on and insulted.

Why should I know what the exact "installed" SP version when most of the
asset tracking software does not bother to have a field for that. I have
access to SDS Help desk, BridgeTrak and a few others and all of them have
fields for the CURRENT Service Pack. S.O.P. for most companies is to
check the PC when it comes in and move it up to the CURRENT patches and
record that it was done. Also record any license numbers. None of the
packages have any indication on what the original installed SPs was.

All the Inventory software shows Current MAC, Current Printer, Current
Video card, Current Drivers, Current, Current, Current, Current, Current,
Current, Current, Current, etc. There are events for updating items, but
even the events only have the "To" versions for updates, not the "From"
listed.

You guys are being a bunch of jerks just because someone dares to point
out something stupid that MS has done. I have been an MCSE for over 8
years, a partner for about 5 now, and using their products almost
exclusively for about 10 or 11 years now and when they do something stupid
I have every right to point out how stupid it is if I feel like it.

It is STUPID for them to have the codes right on the computers in an
easily accessible place for all the world to see rather than leave them on
the CDs like before. It is also STUPID that they went out of their way to
make it so I cannot install SP2 with my valid Release, SP1, or SP1a key.

I know that I can find at least 100 XP licenses numbers on the Internet
right now if I wanted to. How do you think they got there? Do you think
it is the System Administrators putting them up there? Its dead beat
employees that now have full access to all the software keys the company
has because we have to stick them in an easily accessible place per MS
instructions (OEM System Builders License Section 8).

 

[Jordan]

Thanks, but I don't know if that is correct because I don't have any retail
purchases of XP. They all came with XP installed and all the tags on the
side of the computers say OEM right on them. Unfortunatley none of them say
XP OEM SP???.

A friend says that he may have a utility that might be able to tell by the
first couple of groups on the key what the release was. Hopefully that
works for future reinstalls.

Thanks again for your input.

 

[Jordan]

First of all, I an not trying to use and XP Home key so don't start making
stupid comments just to make an arguement that you were wrong to start. You
keep bringing up slip streaming because you cannot comprehend the problem.
How many times do I have to explain this to you...

If you have a release key you can re-install the release or release with
slipstreamed SP1, SP1a, or SP2 with no problem. DUH??????

If you have a key and you don't know whether it was release, SP1, SP1a, or
SP2 you cannot just slip stream any version into an install. The base setup
is not working with the key if it is differnet.

Here is a real life example for your little brain. You have 4 computers:
1 Shipped with Release
2 Shipped with SP1
3 Shipped with SP1a
4 Shipped with SP2

Can you make one slipstream for all 4??? NO YOU CAN'T because if you used
Release to create the slipstream you cannot use that setup for 3 of the
other computers. Do you finally GET IT!!!!!

 

[Jordan]

That is all you had to say if you did not like the "minor" complaint. You
do not need to get insulting about my abilities when you don't know me.

 

[Richard Urban]

You're the one who doesn't get it - and yes, you most certainly CAN!

I will make a slipstreamed version (SP2) of the retail version (3 years old)
and put it on any computer, even if it never had a copy of Windows XP on it
at all! I don't care what version is on it now! I don't care if it's OEM or
retail! And I will use my original install key to do it!

What you can't do is perform a repair install without jumping through hoops.
What you can't do is start the install while in Windows XP. What you must do
is boot from the CD. What you must do is perform a format/install.

As I said, you are beating a dead horse. Get your records in order.

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you thought you know,
You would realize that you don't know what you thought you knew!

 

[Guest]

You have 100 computers to take care of but you can't seem to maintain your own!

Sounds like a line of bull shi* to me.

 

[Jordan]

You keep posting with examples that have NOTHING to do with the original
problem. I have already explained it in detail to you so anyone with half a
brain can get it. You keep saying that you can slipstream a retail or
release with SP2 and that key will work - DUH??? Of course it will because
you are using the key from the original version disk. Of course the the
install will work on any hardware because the retail and generic OEMs that
you get in the MS package are not coded for any particular hardware. Stop
being an idiot and open your eyes and READ.

You CAN NOT take a CD that YOU did not slipstream such as an OEM CD with SP2
on it and use a release, SP1 or SP1a CD key. Do you get it?

Slipstream a release CD to SP2 and use release key - OK
Slipstream a SP1 CD to SP2 and use SP1 key - OK
Install or repair with SP2 CD and use retail key - FAIL
Install or repair with SP2 CD and use SP1a key - FAIL
Install or repair with SP2 CD and use SP1 key - FAIL
Slipstream a release CD to SP2 and use SP1 key - FAIL
Slipstream a SP1a CD to SP2 and use SP1 key - FAIL

Is that plain enough for you? Do you understand now? Why don't you go
slipstream a OEM release CD with SP2 and use a CD key that came with an OEM
CD that came with SP2 already on it from Microsoft and tell me then what you
get!!!!

Don't be to embarrased to post that you were wrong, but after posting so
many messages showing that you can't comprehend the problem I guess I can't
expect you to do anything other than keep going off in different directions
trying to avoid the fact that you were wrong all along.

 

[Richard Urban]

I can do it with the retail version. I am in the process, as I type, of
installing a Windows XP Professional retail SP2 CD (purchased 2 months ago)
into Virtual PC. I just entered my original Windows XP Professional retail
install key from 3 1/2 years ago. The install is continuing fine - it seems.

All of your complaints seem to boil down to using OEM CD's. So, in all of
this nonsense you are trying to install maybe an OEM CD from one
manufacturer (HP) on another manufacturers (DELL) computer (or even a home
built computer)? If that is the case I agree - it probably will not work, no
matter what the revision is. And it has nothing to do with Microsoft. It has
everything to do with the way the OEM's alter the operating system for their
computers.

It still boils down to what quite a few people have told you. It is YOU who
have to keep your records straight (anyway you can) to prevent this
condition from occurring.

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you thought you know,
You would realize that you don't know what you thought you knew!

 

[Jordan]

Another one. Nice.

Have you ever upgraded a system before? So what sounds like bull to you
smart guy?

I'm managing networks for 10 years now in the real world and you guys are
out hear begging MS for freebies trying to answer questions with half ass
answers you pull out of the MS Knowledge base. Have you ever even seen 10
computers in the same room other than at a computer show or in high school.

Too bad if your so in love with the stupid idea of keeping your labels on
your computer for all the world to steal. Its a bad idea and everyone knows
it. One of the first things I learned over 10 years ago was to keep
licenses safe and secure by locking them up and not letting my users know
them so the company doesn't get ripped off. Now MS decides on their own
that they are going to change that all around and you guys just follow it
blindly like sheep and God forbid anyone has an opinion on the matter.

All the helpdesk packages only list what the current SPs are for the
software installed. If you upgraded there are events in the logs for what
you upgraded to, not from. Apparently you have not seen any helpdesk
packages from your mother's basement.

When you guys get a real job and start following industry practices then you
will see what a pain something like this is. No other package that I am
aware of will not let you install your valid codes just because you are
using a CD with the service pack already incorporated into it.

Not one of you clowns has even come close to backing up that this policy is
a good idea so either post examples of how great this is or stop posting
ridiculous attacks that you can't back up.

 

[Guest]

Damn you are stupid!

Quit messing with the OEM CD's and buy a retail copy and be done with your
inane bullsh*t!