Windows Embedded Standard 7 Serial Key and Activation Question

Discussion in 'Windows Embedded' started by jedinight2002, Aug 9, 2011.

  1. jedinight2002

    jedinight2002 MDL Novice

    Jun 8, 2008
    45
    4
    0
    #1 jedinight2002, Aug 9, 2011
    Last edited: Aug 9, 2011
    We have bought a bunch of HP Thin Clients that come with WES7 installed - but NOT with WES7 SP1 which we want. We also need to cusomise the OS including altering the sysprep unattended file. So ultimately, i want to use the toolkit or image builder wizard (IBW) to create a new image.

    However, even after pulling the serial key from one of the thin clients, when entering that into the image builder wizard or toolkit, it says that its not valid? Can anyone explain why this is?

    That would imply that a general license key is issued by MS for creating the images using one of the 2 tools, but that the final image has a DIFFERENT serial key once the OS is installed onto the device - is that correct?

    1: Can anyone suggest another way to get a serial key from our purchase/licensed devices, to create a new image?
    2: If we were to use a serial key that worked, sourced from the internet, would we be breaking any rules? Could said serial keys be black listed at a later date?

    Background: We are having issues getting MS to give us serial keys for the OS, even though we have bought the through HP and HP are refusing to give us any keys sayind speak to MS - VERY ANNOYING!!! We pay both these companies 5 or 6 figure sums annually...........

    Many thanks.
     
  2. 100

    100 MDL Expert

    May 17, 2011
    1,346
    1,541
    60
    #2 100, Aug 9, 2011
    Last edited: Aug 9, 2011
    As mentioned in my other post, the keys for the Toolkit and for the WES7 OS are different, but you should be able to use the key obtained from your WES7 installation when setting up a new image.

    Building a different OS image would most likely violate some EULA terms though, as WES7 is not licensed to end users directly, but to OEMs like HP. OEMs will also only want to provide support for devices running their own OS images.
    I believe runtime keys are only issued one key per OEM agreement, so it's possible that all of those HP Thin Client models use the same key. Blacklisting would therefore be pretty much impossible to do.
     
  3. 100

    100 MDL Expert

    May 17, 2011
    1,346
    1,541
    60
    That key you pulled from your HP thin client, is it ...-VKJD2 by any chance?
    Just to check if it might be a single key they're using on all of these devices.
     
  4. jedinight2002

    jedinight2002 MDL Novice

    Jun 8, 2008
    45
    4
    0
    Who is they? HP?

    Are they allowed to do that?

    Are WE allowed to do that?
     
  5. 100

    100 MDL Expert

    May 17, 2011
    1,346
    1,541
    60
    Yeah, I mean HP. This is the way WES7 is licensed, the OEM gets issued just one key for use with their runtime images, so it's likely that HP's preinstalled thin client installations all use the same one. They also don't need to be activated with MS at all.

    It's basically the same way regular Windows 7 installations are preinstalled by OEMs, each one gets issued an SLP key that is then used on all the machines they ship. (The key on the COA label attached to the case is a unique key, but the preinstalled OS uses the generic OEM:SLP key, and not the COA key).
    This is the reason these keys can't get blacklisted, because that would invalidate the key on all of the machines legitimately using it.

    Whether we are allowed to use it: I haven't read through it, but I'm sure that is explained in great detail in the EULA ;)