/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Win 7 deployement

10/15/2012 3192 views

Hi,

I'm entirely new to deployment so I do appologize if something seems obvious.

Im trying to deploy win 7 images on a few Latitude E6430's using K2000.

I run sysprep with OOBE generalize shutdown options

I'm able to capture and deploy an image sucessfully, but unfortunately the system that the image is deployed on

boots up and windows is already activated, and I am not prompted to enter the serial key for windows.

Does any one know if that has something to do with the OEM version of windows that these systems come with, and there is some information out there suggesting that the windows sn#'s are embedded into the hardware?!

 

0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

2

prior to sysprep release the license key using slmgr /cpky /upk /rearm

http://technet.microsoft.com/en-us/library/ff793433.aspx

Answered 10/16/2012 by: SMal.tmcc
Red Belt

All Answers

0
Microsoft makes it illegal to use OEM for imaging and redeployment.  

I NEVER use the OEM OS install, but do the install with our KMS disc, all the apps installs and sysprep the image before capturing.  
Answered 04/12/2016 by: ColderIT
White Belt

0

Thanks for the tip, I will try it out and capture a new image

Answered 10/16/2012 by: kireberik
Senior White Belt

0

Well, I captured and deployed an image using slmgr /cpky /upk /rearm and then sysprep.

The box with the deployed image boots up with the windows already activated. 

I ran prod-u-key to check what serial it had, and it is saying product key not found.

Not sure what else could be causing this issue.

Answered 10/16/2012 by: kireberik
Senior White Belt

  • This content is currently hidden from public view.
    Reason: Removed by user request For more information, visit our FAQ's.
  • I think you are right that the oem version has the code branded in it.
    see
    http://community.spiceworks.com/topic/103437-sysprep-ing-an-oem-windows-7-image-for-wds
  • you could also try to put the KMS key in your answer file, and since you do not a kms server it should pop up to activate
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ProductKey>33PXH-7Y6KF-2VJC9-XBBR8-HVTHH</ProductKey>
    </component>

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ