Jump to content
DeployCentral
DonS

Win 10 not Activating on new deployment

Recommended Posts

I created a VM image and deployed it without any probs. Had a hardware problem and had to install SD on new pc. Created a new VM image and activated Win 10. New deployments will

not activate now Win 10. Any suggestions?

 

Thanks

Don

Share this post


Link to post
Share on other sites

Hi Don,

Activating Windows on the reference VM has no bearing on whether it will activate on the target PC. The Sysprep\Generalize process which runs on every image at deployment time strips out any existing license info from the image. SmartDeploy provides two opportunities to enter a Windows product key - either in Capture Wizard (in which case it is hashed and written into the metadata of the image to be used at deployment time), or in Deploy Wizard (in which case it is written into the Sysprep Unattend.xml to be used at deployment time). If you do not provide a Windows product key at one of these times, then we cannot guarantee that the target device will activate.

If you have any questions, feel free to email us at support (at) smartdeploy.com

Regards,
Glenn

 

SmartDeploy Support

        888.7DEPLOY    toll-free

_____________________________

 

        SmartDeploy®

 

        Learn about our award winning

        Windows deployment solutions

        www.smartdeploy.com

        www.deploycentral.com
       

        Twitter: @SmartDeploy

        Facebook: SmartDeploy

        Spiceworks: Spiceworks

Share this post


Link to post
Share on other sites

no product key was entered in the answer file of the image that worked. After the new pc booted up, the OEM license would then be activated. Maybe I am missing something.

Is there a support telephone number that I can call?

Don

Share this post


Link to post
Share on other sites

Hi Don,

OEM licenses do not include reimaging rights from Microsoft. We have had some customers report success with such licenses, but it is inconsistent and unreliable (by design), as the license is only intended to be used to revert the device back to its original factory image. SmartDeploy has no interaction with this process, so we have no control over whether or not Microsoft allows the device to activate if you do not provide a license key for us to pass through at deployment time. Our recommendation is to look into getting a volume license. We are not a volume license reseller, but we can put you in touch with one - go ahead and email us and we can send you their info.

Regards,
Glenn

 

SmartDeploy Support

        888.7DEPLOY    toll-free

_____________________________

 

        SmartDeploy®

 

        Learn about our award winning

        Windows deployment solutions

        www.smartdeploy.com

        www.deploycentral.com
       

        Twitter: @SmartDeploy

        Facebook: SmartDeploy

        Spiceworks: Spiceworks

Share this post


Link to post
Share on other sites

As Support mentioned, volume licensing is the correct way to go about this. But we've had luck pulling the OEM key from BIOS using something like ShowKeyPlus, then activating with that key. There are ways to automate this with a PS script. 

Share this post


Link to post
Share on other sites

I ran into this issue as well. If you have a digital license key which you most likely do then you need to get an ISO for windows 10 and reinstall the OS, this will reactivate windows. Fully complete the initial "out-of-box" set up while connected to the internet (so it can connect to the Microsoft servers and activate the digital license). When you get to the desktop for the first time is when your digital key will be activated, you don't need to worry about preforming all of the windows updates before you image.  From there you can go ahead and image it. I would recommend setting your answer file to shutdown rather than restart after the image is complete. Make sure when you power the PC back on it is connected to the internet via ethernet cable or the digital key will not activate.

Share this post


Link to post
Share on other sites

I have deployed 50 OEM Windows 10 machines without a VL. What I noticed is that a few machines were activated immediately, whereas others had to be online for anywhere from 24-72 hours before they would activate. But everyone of them did eventually activate with the OEM license.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×