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

[Jordan]

I am not using a Dell on an HP. I am not using retail with OEM. All the
computer that have had XP have come from the same vendor and they have
pretty much the exact same hardware other than a couple have faster
proceesors.

The vendor is small so they take the OEM CDs that MS sends out and includes
them in the shipments. If MS is on SP1, the image the PC with SP1. Same
for Release, SP1a, and SP2 and then they dump on the drivers for the
components. Nice and simple and no extra garbage like AOL or trial AV
software that I don't want.

It is not my fault that every other software package lets use your key with
patched version. If you can name one major package where they keep you from
using the key from the release with manufacturer patched version then you
might be half right, but there aren't any that I can think of. Not Oracle,
not PeopleSoft, not Pervasive, not Roxio, not Nero.

This is a new "feature" that has not been documented anywhere that I can see
so to jump ugly and say that I am mis-managing my duties is way out of line.

 

[Jordan]

Great answer! Go pay $199 - $259 for a license that I already have. And
these jokers as saying that I can't manage my resouces. If your the kind of
guy that they are looking for it is no wonder I can't get through to them
with logic.

 

[Michael Stevens]

Michael - I think you refer to the 26 Alpha numeric Product *Key* - not
the numeric Product *Id* as found in Control Panel system and which is
of no relevance in installing

LOL, You are right, don't know how I missed it and missed it and missed it.
BTW, that is 25 not 26 right?
--
Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm

 

[Michael Stevens]

"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.

Yes, because you have a history with the local vendor, that is why I said
you could "request". I don't think you would complain about it to Microsoft
would you? There is no requirement it has to be left on the outside of the
case by the end user. All that you as the end user has to make sure of is
each Product Key is used only once.

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.

Why do you need to know what SP of XP that shipped with the computer? All
you need is a slipstreamed XP CD with SP 2 corresponding to the type [OEM,
Branded OEM, Retail, Home, Pro] used on the computer. You DO NOT need to
first start with original CD.

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.

I never said anything about hardware
Some Branded OEM CD's will not accept a generic OEM PK.

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.

Never mentioned Recovery CD's.

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

They didn't have activation either.

 

[off2oblivion]

Okay, if you're patient, read what I have to say, everyone will learn
something new today.

First of all, Jordan is obviously not very tactful. But everyone should
admit that he is right: the whole cd key/coa sticker thing is a fiasco.
He explains it clearly here:

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

As for the COA being affixed to the PC, I should add: not only can a
disgruntled employee write it down, any employee can write it down,
period. Even someone visiting your office that sits near your desk
while you step out momentarily.

Eventually your cd key will end up being "activated" and when you least
expect it, it will not work. If the cdkey makes it to the internet,
kiss it goodbye. Your only option will be to call the activation
hotline and ask (in some cases, beg) to legitimize the key.

This could be prevented if the cd key were to remain private, just like
it used to work.

Now with that said, I have some good news for the original poster (and
everyone else; it is obvious no one here understands MS licensing, but
don't be ashamed, very few people do).

As of about two years ago, Microsoft relaxed their licensing terms.
This is how it works:

1 - Buy your computers from whoever, with the OEM cd, coa/cdkey,
manuals, etc
2 - Buy only 1 WinXPP license via open licensing (cdw, etc)
3 - Buy the vla OS media and SP of your choice for a small fee ($30-$40
bucks total)
4 - Now use this media with your corporate license key on any OEM
computer from IBM, Dell, Joe Blow's, etc

That's how you do it -- 100% MS legal.

Note: on #2, there is a minimum purchase; if you operate 100 computers,
surely you can find a few MS products that you will need; you must buy
at least one upgrade so you can get your corporate key. References:
http://download.microsoft.com/download/0/6/7/067ff52c-a552-4f6e-852c-03d086b41f68/reimaging.doc

Or: http://www.microsoft.com/licensing/resources/volbrief.mspx click on
reimaging.doc

"However, you can use copies of a Microsoft Windows® desktop operating
system made from volume licensing media in place of licensed copies of
the same software obtained from the OEM channel, even though they may
be of different product types (e.g., one may be an upgrade license and
the other a full license), provided that the other attributes are
identical." -end qoute

"Upgrade" meaning: desktop volume OS license (MS only sells upgrades
for desktops, no such thing as full desktop OS, but full server OS's
they do sell). And "full license" means: the OEM license (OEMs can only
sell FULL versions, never upgrades).

More...

"If a Volume Licensing customer has licensed Microsoft software
products from an OEM, through a retail source or under any agreement
other than its Microsoft Volume Licensing agreement, the customer may
use copies made from Microsoft Volume Licensing media in place of any
copies made from the media provided through that separate source, so
long as the following conditions are met:

- A separate license is obtained from the retail source for each
copy being replaced.
- The replacement copy and licensed copy are identical.

Open License customers must also acquire at least one license under
their Open License authorization number for any product a customer
plans to re-image." -end qoute

Note: you don't have to use XP, XPP OEM comes with downgrade rights:
2000, 98, NT. References:
http://download.microsoft.com/downl...9d-4996-b198-7b9d3fe15611/downgrade_chart.doc

Or: http://www.microsoft.com/licensing/resources/volbrief.mspx click
downgrade_chart.doc.

Use any media purchased or burned from anyone, even OEM CDs.

To be sure what I am saying is correct, call 800-426-9400 and hear it
from the horse's mouth. Tip: transfer to the "large organization"
extension (larger than 1000 employees, I forget). Don't talk to the
small fries, they're usually ill-informed, not to mention often rude.

The reason they did this is because companies were not going to pay
twice for the OS (OEM + volume upgrade) just to avoid WPA. At the same
time customers were fed up with having to pay twice for (the privilege
of) disk imaging. And it makes sense, just look at the problems it's
causing you? Imagine a company with 10,000 computers. Also, if you
downgrade and later change your mind, you can go back to XPP (contrary
to popular myth, because some OEMs forced you to pick between two
versions, back in the days).


If you (or anyone else) decide to call MS and the representative
disagrees, ask him to check with a higher up, if he/she still insists
you're wrong, ask to be transferred to a supervisor.

This is how I got confirmation. I went through two people, the first
said, "that's piracy!" (no joke) I then insisted that he check because
I read this in several articles. He came back and admitted I was right
and apologized (the guy was an idiot). Later I called again and spoke
with someone else. This person was also unsure. After waiting for about
three minutes, he too came back and said I was right. Good luck.

 

[Michael Stevens]

Damn you are stupid!

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

Actually you are the uninformed one.
You didn't comprehend or understand what this thread is about, sit back and
learn before posting embarrassing attacks. The OEM versions are exactly what
the OP should have been provided from the vendor and the retail versions
would have been the worst decision the OP could have made.
Jordan could have initiated the original post better, but the outcome of the
thread should be very informative to us all. That is the beauty of the peer
support newsgroups, we all learn from the collective knowledge of our peers.
--
Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm

 

[Jordan]

Thank you very much. The fine details are good to know. Are you certain
about the $30 to $40 per license because not that long ago I got quoted a
lot higher for XP pro. Maybe because my volume was low (under 100 since I
already had a lot of licenses).




Okay, if you're patient, read what I have to say, everyone will learn
something new today.

First of all, Jordan is obviously not very tactful. But everyone should
admit that he is right: the whole cd key/coa sticker thing is a fiasco.
He explains it clearly here:

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

As for the COA being affixed to the PC, I should add: not only can a
disgruntled employee write it down, any employee can write it down,
period. Even someone visiting your office that sits near your desk
while you step out momentarily.

Eventually your cd key will end up being "activated" and when you least
expect it, it will not work. If the cdkey makes it to the internet,
kiss it goodbye. Your only option will be to call the activation
hotline and ask (in some cases, beg) to legitimize the key.

This could be prevented if the cd key were to remain private, just like
it used to work.

Now with that said, I have some good news for the original poster (and
everyone else; it is obvious no one here understands MS licensing, but
don't be ashamed, very few people do).

As of about two years ago, Microsoft relaxed their licensing terms.
This is how it works:

1 - Buy your computers from whoever, with the OEM cd, coa/cdkey,
manuals, etc
2 - Buy only 1 WinXPP license via open licensing (cdw, etc)
3 - Buy the vla OS media and SP of your choice for a small fee ($30-$40
bucks total)
4 - Now use this media with your corporate license key on any OEM
computer from IBM, Dell, Joe Blow's, etc

That's how you do it -- 100% MS legal.

Note: on #2, there is a minimum purchase; if you operate 100 computers,
surely you can find a few MS products that you will need; you must buy
at least one upgrade so you can get your corporate key. References:
http://download.microsoft.com/download/0/6/7/067ff52c-a552-4f6e-852c-03d086b41f68/reimaging.doc

Or: http://www.microsoft.com/licensing/resources/volbrief.mspx click on
reimaging.doc

"However, you can use copies of a Microsoft Windows® desktop operating
system made from volume licensing media in place of licensed copies of
the same software obtained from the OEM channel, even though they may
be of different product types (e.g., one may be an upgrade license and
the other a full license), provided that the other attributes are
identical." -end qoute

"Upgrade" meaning: desktop volume OS license (MS only sells upgrades
for desktops, no such thing as full desktop OS, but full server OS's
they do sell). And "full license" means: the OEM license (OEMs can only
sell FULL versions, never upgrades).

More...

"If a Volume Licensing customer has licensed Microsoft software
products from an OEM, through a retail source or under any agreement
other than its Microsoft Volume Licensing agreement, the customer may
use copies made from Microsoft Volume Licensing media in place of any
copies made from the media provided through that separate source, so
long as the following conditions are met:

- A separate license is obtained from the retail source for each
copy being replaced.
- The replacement copy and licensed copy are identical.

Open License customers must also acquire at least one license under
their Open License authorization number for any product a customer
plans to re-image." -end qoute

Note: you don't have to use XP, XPP OEM comes with downgrade rights:
2000, 98, NT. References:
http://download.microsoft.com/downl...9d-4996-b198-7b9d3fe15611/downgrade_chart.doc

Or: http://www.microsoft.com/licensing/resources/volbrief.mspx click
downgrade_chart.doc.

Use any media purchased or burned from anyone, even OEM CDs.

To be sure what I am saying is correct, call 800-426-9400 and hear it
from the horse's mouth. Tip: transfer to the "large organization"
extension (larger than 1000 employees, I forget). Don't talk to the
small fries, they're usually ill-informed, not to mention often rude.

The reason they did this is because companies were not going to pay
twice for the OS (OEM + volume upgrade) just to avoid WPA. At the same
time customers were fed up with having to pay twice for (the privilege
of) disk imaging. And it makes sense, just look at the problems it's
causing you? Imagine a company with 10,000 computers. Also, if you
downgrade and later change your mind, you can go back to XPP (contrary
to popular myth, because some OEMs forced you to pick between two
versions, back in the days).


If you (or anyone else) decide to call MS and the representative
disagrees, ask him to check with a higher up, if he/she still insists
you're wrong, ask to be transferred to a supervisor.

This is how I got confirmation. I went through two people, the first
said, "that's piracy!" (no joke) I then insisted that he check because
I read this in several articles. He came back and admitted I was right
and apologized (the guy was an idiot). Later I called again and spoke
with someone else. This person was also unsure. After waiting for about
three minutes, he too came back and said I was right. Good luck.

 

[Jordan]

Yes, because you have a history with the local vendor, that is why I said

you could "request". I don't think you would complain about it to
Microsoft would you?

The problem first is that it is inappropriate for me to ask my vendor to do
something that they are not supposed to do, especially with a company like
Microsoft. Everyone knows that Windows is on 90% of the personal computers
out there so my vendor's doors will close if they get in trouble with MS and
somehow loose their ability to pre-install MS products.

There is no requirement it has to be left on the outside of the by the end
user.

If I could peal it off without ripping the key in pieces I would, but we
both know that the tags are designed to tear appart into several pieces if
tampered with. A torn up tag is an invalid tag.

Yes, if I were just a single end user I would not care if the tag is on the
PC or not, but in the corperate world it is a lot different. If your part
of a publicly traded company you probably heard about the new requirements
for corperate accountability called SOX (Sarbanes - Oxley). Most of this
deals with accounting controls but as part of the audits you are required to
show that you have your licenses and that you are living up to them. Our
auditors made sure they checked the sides of every PC case for the tags. I
had 2 very old Win 95 machines that are just used to run some test equipmemt
and they asked where the tag was. I had a hard time getting them to accept
the fact that I did not need it done in this case because these were not
OEMs.

The auditors were clear that these were not their rules and they agreed that
it was inconvenient as well, but they insisted that as long as "Microsoft"
made this a requirement then they had to give me a hard time over it. Its
not the auditors or the vendors fault that this is required by MS.

Why do you need to know what SP of XP that shipped with the computer? All
you need is a slipstreamed XP CD with SP.

That is what I thought before I made my original post but that has not
turned out to be true. Here are the results from a couple of tests that I
did in the mean time:

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 SP1(a) CD to SP2 and use SP1 key - FAIL

If you look deeper under a part of this thread you can see that
"off3oblivion" confirms this to be the case. He also posts more details of
the requirements. I think he is off on the pricing or is quoting XP home
becaue $30-40 seem very low for XP Pro and seem more like the home OEM Home
prices, but I can find that out later.

"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.

Yes, because you have a history with the local vendor, that is why I said
you could "request". I don't think you would complain about it to
Microsoft would you? There is no requirement it has to be left on the
outside of the case by the end user. All that you as the end user has to
make sure of is each Product Key is used only once.

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.

Why do you need to know what SP of XP that shipped with the computer? All
you need is a slipstreamed XP CD with SP 2 corresponding to the type
[OEM, Branded OEM, Retail, Home, Pro] used on the computer. You DO NOT
need to first start with original CD.

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.

I never said anything about hardware
Some Branded OEM CD's will not accept a generic OEM PK.

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.

Never mentioned Recovery CD's.

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

They didn't have activation either.

 

[Michael Stevens]

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.

Now if you would have explained it like this to begin with, we could have
all approached the question with a different perspective. I have not
encountered the problems you list, but I have not had first hand experience
with all the OEM media you list. Your experience is the first time I have
seen this issue in the newsgroups with the Product Keys not being accepted
from different SP versions. This I will concede could be a problem, but your
contention that the PK be affixed to the CD case is not a solution to your
managerial problems. You need to reassess that aspect of your beef.

--
Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm

 

[Jordan]

I would love to request that they put it in the case, but accourding to OEM
System Builders license section 8 the OEM builder cannot do that for me.

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.

I could try to peal the tag off, but that would tear it and accourding to MS
a torn tag is an invalid tag. I guess they feel that if it is torn it was
probably stolen and not an attempt by the real owner to protect their keys.

 

[R. McCarty]

Perhaps the wording doesn't preclude obscuring the actual code on
the label. Maybe you could get some opaque tape and place over
the code itself or write "Obscured for Security" on it.

I would love to request that they put it in the case, but accourding to OEM
System Builders license section 8 the OEM builder cannot do that for me.

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.

I could try to peal the tag off, but that would tear it and accourding to
MS a torn tag is an invalid tag. I guess they feel that if it is torn it
was probably stolen and not an attempt by the real owner to protect their
keys.

 

[Jordan]

I thought I might do that to but if the employee or guest is the type to
steal the key code in the first place I will bet they will have no problem
pealing the tape back to take a peak.

Thanks

Perhaps the wording doesn't preclude obscuring the actual code on
the label. Maybe you could get some opaque tape and place over
the code itself or write "Obscured for Security" on it.

 

[R. McCarty]

Your reply made me remember something we used to use back in
my Corporate IT days. We had small metallic surface stickers that
were guaranteed to be un-removable. If you tried to peel them off
the surface they would leave a coating that even "Goof-Off" wouldn't
remove.

Of course nothing will stop a determined thief, but like the retail
plastic packaging that needs dynamite or a hack-saw, you can make
getting at the code more difficult. Good Luck.

 

[off2oblivion]

reimaging.doc:
"Open License customers must also acquire at least one license under
their Open License authorization number for any product a customer
plans to re-image."

This is what you need:

Microsoft Windows XP Professional upgrade
CDW Part: 330231
Mfg. Part: E85-00425
Price: $179.00
http://www.cdw.com/shop/products/default.aspx?EDC=330231

Way over-priced, I know, but you only need one. Tip: use this as a
legitimate upgrade for one Windows computer (9x/NT/ME/2000) in your
company.

Then you buy one of the following media kits (all priced at $26.39):

Microsoft Windows XP Professional - media kit
CDW Part: 486767
Mfg. Part: E85-02008
Localization [not specified, but should be english]
http://www.cdw.com/shop/products/default.aspx?EDC=486767

Microsoft Windows XP Professional w/SP1 - media kit
CDW Part: 562232
Mfg. Part: E85-02010
Localization [not specified, but should be english]
http://www.cdw.com/shop/products/specs.aspx?EDC=562232

(Couldn't find SP2 - might not be offered)

Same as above, but different part numbers (? ... couldn't find XP
release, probably not offered):

Microsoft World Wide Fulfill MS Windows XP Professional w/SP1 - media
CDW Part: 479131
Mfg. Part: E85-01892
Localization English
http://www.cdw.com/shop/products/specs.aspx?EDC=479131

Microsoft World Wide Fulfill MS Windows XP Professional w/SP2 - media
CDW Part: 688652
Mfg. Part: E85-02839
Localization English
http://www.cdw.com/shop/products/specs.aspx?EDC=688652

This one is for Microsoft Select Licensing:

Microsoft Windows XP Professional - media kit
CDW Part: 482786
Mfg. Part: E85-01172
Localization English
http://www.cdw.com/shop/products/specs.aspx?EDC=482786

Why one set of media is "Select" and the other isn't, I don't know, but
I do know it will work with any corporate key. They are probably
phasing out "Select" media in favor of plain "VOL" (volume) media
because the cost is the same (?).

- I highly recommend you setup an account with CDW and double-check the
order codes with your sales rep.

- After you place your order you will get an email from Microsoft:
"Microsoft Open License Order Confirmation". In this email you will get
a) an Authorization Number, and b) a License Agreement Number.

And, there will be instructions on setting up an open account
(https://eopen.microsoft.com). Once you do this, a unique corporate key
will be assigned to you. Keep it confidential. Scramble the key so if
it winds up on the internet, it won't matter, eg:
ABCDE-FGHIJ-KLMNO-PQRST to ABCDF-EGHIK-JLMNP-OQRST (use your own cheezy
encryption).

- Remember, there is an initial, minimum purchase so ask your CDW rep,
I forgot what that was ($500, $1000? it's based on points; after the
initial purchase, there is no minimum throughout the term, which is two
years I believe).

- Nice thing about CDW is they keep a history of your licenses through
their Software License Tracker, good for MS, Symantec, Veritas and many
others.

Once again, you can use the XPP volume media in place of your XPP OEM
media, as long as the desktop is properly licensed. Yes, this really
does mean you do not have to pay twice for the OS ($140 OEM+$180
upgrade) just for the privilege of reimaging and/or avoiding WPA:

reimaging.doc:
"If a Volume Licensing customer has licensed Microsoft software
products from an OEM, through a retail source or under any agreement
other than its Microsoft Volume Licensing agreement, the customer may
use copies made from Microsoft Volume Licensing media in place of any
copies made from the media provided through that separate source"

Something to think about: Microsoft does not specifically say you can
grab a volume license CD and use it to install XPP, fresh on a properly
licensed OEM computer. They only say you can use volume license media
to re-image: "Re-imaging is the copying of software onto multiple
devices from one standard image using volume licensing media".

So does this mean you are only allowed to create just one image for all
of your computers and nothing more?

- I really don't think so. As explicit as reimaging.doc is, you would
think they would have pointed this out. Therefore, I think it's
implied.

- If however you're not entitled to use the media to fresh-install over
an OEM licensed PC (or upgrade it out of OEM stature to avoid WPA
and/or to standardize on one set of media), then this would make it a
very silly (and stupid) restriction because:

- Regardless, any competent tech can start with a base image on even
the most hardware-varied environments and build it to a working system.

Call MS licensing to be sure.

 

[Greg R]

Jordan those system that are preinstalled oem correct?

One that there is a hidden key. That most manufactures use to
install xp. All you need is the key viewer to find that key and
reinstall it. If you have one that is working before you repair
it.

Then change the key after you have the hardware and updates installed.
Call Microsoft tell them you added hardware. Then activate.

I also read you can call Microsoft and get re-certification if you
think you or your customer key has been compromised..

However, I don't have that number.


Greg R

 

[cquirke (MVP Win9x)]

On Fri, 14 Jan 2005 15:12:58 -0700, "Ken Blake"

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.

I disagree, in that these are discussion groups, not purely here as a
free support line. If fuss kicked up here rips damaging stuff out of
the next product revision, that's more worthwhile than shipping as-is
and then trying to step on ants one at a time forever thereafter.

-------------------- ----- ---- --- -- - - - -

Tip Of The Day:
To disable the 'Tip of the Day' feature...