Also located here (https://social.technet.microsoft.com/Forums/en-US/273efe97-a282-443b-9629-2ce5afd7f688/mdt-2013-8-image-buildingdeploying?forum=mdt), feels like this question might be better suited here. idk

2 questions

Context for question 1

I have everything automated for image building but skiping the activation part in oobe. MDT's wizard detcts the machine with sql and it mac address and applys all the settings and base configs that will be deployed to any and all 8 physical devices later on.

Question 1

I need to know how to skip the system activation in 8.1's oobe after mdt reboots. is using a gval allowed or is there something else I can do?

link to gval hxxps://technet.microsoft.com/en-us/library/jj612867.aspx

(stuck waiting till verfication.)

Context for Question 2

i am using WDS and MDT to UEFI pxe boot (enabled the uefi network stack in the bios/uefi, secure boot is on) but i am prompted with the oobe activation on a Dell machine that came with 8.1 installed. the key is on the machine and it works if i use a usb boot. just not pxe. my current work around is to skip and run a power shell script that gets the key off the board and applys it.

Question 2

What would be the recomended way for mdt/wds to properly detect and apply the key.

$key = (Get-WmiObject -query `select * from SoftwareLicensingService`).OA3xOriginalProductKey

$computer = gc env:computername

$service = get-wmiObject -query "select * from SoftwareLicensingService" -computername $computer

$service.InstallProductKey($key)

$service.RefreshLicenseStatus()

Hi,

Well, Since OEM key is not public and hosted by Manufacturers, I think here is a rub on this, seems like the generic product key in that link you posted wont tell Windows 8.1 whether to look into the BIOS or not. Some users says that we could workaround this by simply skip the whole oobe step (but I think your workaround is better).

https://technet.microsoft.com/en-us/library/ff716280.aspx

Here are some discussion on this, just for your reference.

http://www.msfn.org/board/topic/171423-win8-autounattendxml-skip-product-key/

Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Since OEM key is not public and hosted by Manufacturers, I am not sure if we could apply this in XML, and I noticed that you already posted same thread in MDT forum (they might get more effective suggestion from there).

And thanks for you script, it actually is a good workaround and your experience will help other community members facing similar problems.

Regards,

D. Wu

Thanks D. W for the reply.

Skip oobe looks promising if it was not being deprecated. I know it works for now, but i would like to advoid using it because it might not exist in 10 in the short comming future.

The forum post, i am not too sure how relevant it is for me as MDT builds the answer files for you. (yes you can add your own edits) And it seems this is people building their own deployment methoids when MDT already supports this.

So some clarification, I need to know if i am allowed to use the GVAL/KMS keys in the list for image building (a vm that is auto started once a month and auto captures. it is never used in production) and image deployment (just to get past the oobe because windows 8/8.1 skipoobe is being deprecated) to get past the product key oobe part. And finaly if microsoft is ok with the above script running to change out the key to the one on the device.

It sounds like you are looking for SkipRearm. Put this setting in your answer file for the Generalize phase and the licensing and activation status of the image will not be reset.

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

• Edited by Brandon RecordsModerator 16 hours 35 minutes ago Removed accidental link.

You should also give this document a read: Licensing brief: Reimaging rights.

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

It sounds like you are looking for SkipRearm. Put this setting in your answer file for the Generalize phase and the licensing and activation status of the image will not be reset.

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

• Edited by Brandon RecordsModerator Wednesday, June 10, 2015 2:48 PM Removed accidental link.

Hi,

Thanks for your reply.

I talked with my colleague who is working on Windows 10 and there is no information that Skiping oobe is being deprecated in new system. In Windows 8.1 it should be a solution and I always suggest skip the whole oobe For this kind of issue.

For your clarification, as I know GVLK key should be able to skip the activation Phase, not sure if it works on OEM machine (I thought it should work till now, saw the discussion and your issue), and notice that to use the keys (GVLKs), you must first have a KMS host running in your deployment.

Regards,

D. Wu