XPe licenses

[Fenster]

Does anyone know if there is, or if there should be, any connection
between the CoA numbers and the product key that accompanies them?

For example, as long as I keep buying more licenses for the boards that
I ship do I need to keep producing new target images built with the new
product keys or I can keep using the same image for pack after pack of
licenses?

Also, what's the position regarding software updates? If I ship a board
with (licensed) XPe and my application but want to update the
application in the future using a new, complete target image do I need
to ship a second license? Is the answer to that question different if
the new target image has been built with a new/different product key?

Thanks for any comments/help.

 

[Gordon Smith \(eMVP\)]

Does anyone know if there is, or if there should be, any connection
between the CoA numbers and the product key that accompanies them?

For example, as long as I keep buying more licenses for the boards
that I ship do I need to keep producing new target images built with
the new product keys or I can keep using the same image for pack
after pack of licenses?

Also, what's the position regarding software updates? If I ship a
board with (licensed) XPe and my application but want to update the
application in the future using a new, complete target image do I need
to ship a second license? Is the answer to that question different if
the new target image has been built with a new/different product key?

Thanks for any comments/help.

The #'s on the COA's don't relate to the Product Key other than a paper
trail. In other words, if MS ever audits you and finds a device with COA #:
XYZ, they can track it back to OEM ABC. They can also know what Product
Keys were given to OEM ABC.

However, from an image perspective? No - no relation that I know of.

Your second question - I *may* be wrong, but I can get a correct answer from
our licensing guy. I'm 99% sure that the answer is if you replace your XPE
image with an XPE image you don't need to worry about buying a second
license. However, if you in the future replace it with whatever comes after
XPE (Windows 2112 as an example for you Rush fans), you will most likely
have to buy a seperate license for the new OS.

 

[Martin Grossen, eMVP [AVNET Silica]]

Hi "Fenster" (Hört sich irgenwie Deutsch an..)

The COA PID is not related to the image.
You had to sign a Embedded OEM CLA prior
to get the COAs. So you are a OEM and have the same
rights as an OEM.

That meens, you can update the images in the field
(by recovery media) with any of the PIDs you have.
Even from another envelope.

Please note, that we as distributor have to report
to microsoft which OEM (CLA number) buyed how
many COAs (Also, we have to track the serial nubers).

So this OEM channel is quantity related, not singel PID
(Like systembulder or retail channel)

Nice and easy, isn't it?



--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Fenster]

Hi "Fenster" (Hört sich irgenwie Deutsch an..)

Irgenwie? My schoolboy German doesn't extend much past fenster and
spiegelei (although they usually ended up under the tabelle rather than
near the fenster), I had to visit Google Translate and even that
couldn't complete.