Windows 10: Deploying Windows 10 using MDT and a OEM key?

Hi,

First off, I will apologize for the complicated nature of this thread.

I have several machines that have OEM licenses of Windows 8.1 Pro. What I would like to do is do the following:

1. Install Windows 8.1 Pro onto them.
2. For each machine, I will need to activate using their own product key that is tied to the BIOS, as I don't have a VL or individual licenses.
3. Install an in-place Windows 10 Pro installation.

Preferably, I would like to do this all with a MDT Task Sequence.

From what I have read, Microsoft will not let people use OEM licenses with deployment. However, what I gather is that MS misunderstands what people want to do, and they think that they want to install Windows using a single OEM product key off a machine to multiple other PCs, and that's not what I want to do at all.

A MS Rep was asked about this on the website Spiceworks, and he responded with this:

What I am trying to do (for each of the machines individually, so not using a single OEM activation key to activate multiple PCs) is install Windows 8.1 on a computer that already had it on it, activate it using the legit key it came with installed into the BIOS, and upgrade to Windows 10 in a single task sequence.

Any advice?

:)

 

Need help with combining Powershell with WDS

I use the MDT (Microsoft Deployment Toolkit) to accomplish this.

https://docs.microsoft.com/en-us/windows/deploy...

You combine MDT with the WDS

https://www.techrepublic.com/article/how-to-dep...

When you do that you can use the MDTs task sequence to generate a task that will allow you to drop scripts in during pre and post deployment.

 

Media creation tool for windows 10

The Media Creator tool isn't for that (it will just create a standard install media disc or USB stick for you), but the tools to do what you want do exist. You could check out

how to create a Windows 10 reference image,
how to deploy an image using MDT (one of many management tools), or for more discussion, check Microsoft's IT forums where

professionals that do this daily like to chat.

 

As far as I know and heard of....the only way to accomplish what you are asking is to use the VL media and key.

 

Why are you making it so complicated?

You can just install latest version of 10 pro on each pc, by creating a single usab installation drive, and activate using 8.1 oem key.

Probably take longer to set up your mdt etc.

If pcs are identical, you could use an image backup tool and simly restore same image to each pc.

 

A 'retail' installation of Windows will not accept a OEM key, from what I've read. I also need to use MDT for this, so that's why I am asking this question.

 

This is incorrect - there is absolutely no difference in the installation procedure or software whether using a retail or oem key for standard licences (non VLKs).

Only restriction is oem key (whether 7/8/10) must not have been used on a different pc prior to using it on current pc.

So install 10 pro, use 8.1 oem pro key to activate. That's it.

Of course, 8.1 key has to be the one that was originally used on same pc.

Use showkeyplus to extract key if 8.1 pro is currently installed, noting which key is for which pc.

Re need to use MDT - why?

 

Since the OEM sticker is no longer on the computer, it is up to us to find our legit OEM key that came with the computer.

SLIC 3.0 embeds the the OEM key into the motherboard and uses it for activation. You can run a powershell command to find what your key is.

Powershell this command:
(Get-WmiObject -Class SoftwareLicensingService).OA3xOriginalProductKey

This will give you your unique key for that machine. Combine this into a Powershell command during the task sequence at the end of deployment, and Windows 8/8.1 should activate. You might be able to directly install Windows 10 with the same command if it is still accepting Windows 8 keys on a clean install.

Use this powershell command near the end of your task sequence in MDT, or on its own:
$key=(Get-WmiObject -Class SoftwareLicensingService).OA3xOriginalProductKey
iex "cscript /b C:\windows\system32\slmgr.vbs /upk"
iex "cscript /b C:\windows\system32\slmgr.vbs /ipk $key"
iex "cscript /b C:\windows\system32\slmgr.vbs /ato"

 

Well, here's the deal. Only computers that came from the factory with Windows 8 or later will have usable product keys stored in BIOS. IF there is a usable Windows 8 or later product key stored in bios, then a clean install of the corresponding edition of Windows 10 (build 10586 - the "November update") will automatically read that product key in bios and use it for installation and activation. It will not ask the user for a product key or which edition of Windows 10 to install.

 

Here's the deal....

VL media will not automagically activate just by running an install. To use your PAID for OEM key, one must run the powershell command.

 

My mistake, thank you for the correction.