Solved Windows Embedded Standard 7 Product Activation

[kmfraley]

Several month ago I obtained the Windows Embedded Standard 7 180-day evaluation package (DVDs). Using IBW and the Application Compatibility template, I was quickly able to generate an OS image that has been working very well. I have added a number drivers, 3rd party applications, our applications and services, etc. Life was good. After verifying that all this was working well, we went ahead and purchased the toolkit and a couple runtime product activation licenses (one WS7E and one WS7P) for the time being. Last week, with x-days left to activate, I attempted to activate the product using the Windows activation section of the Control Panel-->System and Security-->System page (see attached partial screen shot). When I clicked either link, I got and error message entitled C:\Windows\\system32\\slui.exe which contained "Windows cannot find 'C:\Windows\\system32\\slui.exe'. Make sure you typed the name correctly, and then try again." Sure enough slui.exe was not to be found in C:\Windows\system32 or anywhere else in the system. So, obviously, this method of product activation did not work.

Is it possible to perform product activation on an image built with IBW using WES 7 180-day evaluation? If not, can I capture the image with Imagex and modify it appropriately with DISM? If not, is there another method? Do I have to start over using ICE? Please help. Thank you.

Kris

 

[Jacee]

try this ... you can change the 'trial key' with your purchased license key from a command line using "slmgr.vbs /ipk key" command.

 

[kmfraley]

Jacee,

Sweet! It appears to have worked! You just saved me a bunch of time and aggravation. Though the initial bitmap background (where the various users are listed) still has "EVALUATION COPY" on it, the Windows activation section of the Control Panel-->System and Security-->System page (see attached partial screen shot) now says, "Windows is activated". Even VAMT 2.0.67.0 is telling me that my system is "Licensed". slmgr.vbs is nice.

THANK YOU!!!!!!

Kris

 

[kmfraley]

Ut oh ... hold the phone. My system now appears to be rebooting at roughly 20 minute intervals. I think I remember reading something about when the evaluation period expires, the system will reboot every 20 minutes. When I do "slmgr.vbs /xpr", I get a Windows Script Host message that says, "Windows(R) 7, Embedded edition: The machine is permanently activated.", but I don't think the OS is convinced that it is really licensed. Not good. Any ideas?

 

[Jacee]

Time to call MS so you know all is well with your key and activation.

Did you click on "change product key" and type the one you purchased in the boxes?

 

[kmfraley]

Re: Did you click on "change product key" and type the one you purchased in the boxes?

I'm not trying to be offensive, but if you re-read my original post, you'll realize that that just doesn't work ... neither before nor after running the "slmgr.vbs /ipk key" command.

Re: Time to call MS so you know all is well with your key and activation.

Again, I'm not trying to be offensive, but all is not well with this method of activation (so far). Not too many customers out there that would accept a system that reboots every 20 minutes.

Can any of the other "slmgr.vbs" switches be used to get this thing to stop rebooting (i.e., stop thinking its an expired eval image)? I'm pretty much willing to try just about anything. Is there another method? Calling Microsoft would cost more than the runtime product activation keys I bought.

Any of you Microsoft types monitoring this forum? Would love to hear from you on this! Really!

Kris

 

[Jacee]

Toll free activation numbers How to contact a Microsoft Product Activation Center

 

[Bill2]

Windows Embedded 2011 will have a new form of activation developed by Windows specifically for the needs of the Embedded market. It will be referred to as “Embedded Activation” or “Brand Activation”. Windows Embedded is now a unique Edition that’s part of the overall family of Windows products. This new method of activation is integrated into the edition, essentially "baked in" to Windows Embedded Standard 2011.

Key facts:
· Activation will happen automatically during setup of the reference or master image
· It will not require network or internet connectivity
· It will require the use of an OEM-specific or license-specific product key (included in the answer file or keyed in to the OOBE UI)
· The activation state persists through manufacturing and/or deployment
· Except in the case of license or kernel tampering, the activation status will be static -- once activated the OS remains activated
· End users will not see activation state notifications
· Includes a limited level of traceability should piracy occur

Similar to previous products, Windows Embedded Standard 2011 images set up using evaluation keys or without a product key cannot be activated and will only be functional for the pre-determined evaluation period.

Source: Activation of quebec

 

[kmfraley]

Well, Bill2, I needed someone to either educate me regarding how to properly activate my original WES 7 image created with IBW using the 180-day eval OR put the last nail in the coffin regarding the possibility. The statement ...

Similar to previous products, Windows Embedded Standard 2011 images set up using evaluation keys or without a product key cannot be activated and will only be functional for the pre-determined evaluation period.

... appears to have driven the nail. At least I can stop spinning my wheels in futile attempts to license this now perpetually rebooting eval image. May I ask, where did the quote come from? I would like to see it in its entirety.

Thanks for your help.

Kris

 

[Bill2]

Well in addition to the link I posted, here are some more.

Image Product Keys and Activation

Download details: Windows Embedded Standard 7 Release Notes

http://download.microsoft.com/downl...285249/WindowsEmbeddedLicensing-McAuliffe.pdf

It appears there is some kind of OEM-like licensing scheme but I couldnt find any details. Best to speak once to MS.

 

[kmfraley]

Thanks Bill2 you've been most helpful ... much appreciated!

 

[kc007]

Resolution?

Hello,

I was wondering if there was a final solution to this problem since I am in the same boat. I had purchased the WES7 toolkit key and created the image. But the new image says I only have 180 days eval. What do I need and how do I make this not an evaluation copy legitimately? Where would I enter the OEM specific license?

Thank you in advance for any pointers.
--kc

 

[kmfraley]

Hi kc007,

Bill2 (above) pretty much nailed it. The evaluation copy cannot be legitimately licensed. There is no legitimate path to activate an EVAL Image. The only solution is to build the OS with a Microsoft (MS) supplied 5x5 activation PID. After you submit your application to MS for a company PID, you will receive a 5x5 activation PID. You need to enter this MS activation PID EITHER in the IBW product screen when doing the OOBE OR enter it into the ICE tool in the Product-->Operating System-->Foundatin Core-->Windows Embedded Edition-->Shell-Setup-->Product Key setting for the Specialize configuration pass. Once you have done this and the build is now complete the resultant image is now an Activated and “Ready-to-Deploy” OS image. This final image is now capable of being captured and deployed to any and all target systems by using tools like ImageX / Ghost or whatever.

Hope that helps.

Kris

[FONT=&quot][/FONT]

 

[awsnap]

But where do you buy said "runtime product activation licenses"? Can you buy one as an end user (IT department) to create your own Gold Image to redeploy to thin clients?

 

[kmfraley]

Wow, this is an old thread dating back over 5 years. Glad I held onto some of those emails.

My company purchased activation licenses from bsquare.com. They are an authorized Microsoft Windows Embedded Distributor. Once I made the purchase, folks at bsquare.com were very helpful in getting my system up and running.

 

[awsnap]

Well thanks for the reply! So you said 'licenses' plural. Did you purchase them per end device or per image type?

Were you the end user or were you creating a product?

 

[kmfraley]

We were not the end user; we were creating a product. Unfortunately, it was a product that never came to fruition. We purchased them per image type. At the time, there were 3 SKUs: WS7E = Economical, WS7P = Professional, and WS7C = Consumer (for set top box guys). We purchased 1 WS7E and 1 WS7P. These were used to create a WS7E image and a WS7P image. If we would have needed to make 1000 WS7P devices, they all would have been copied from the same original image from the one license. However, each WS7P device would have needed its own official Microsoft sticker to show proof of royalty payment.