Windows 10 Scripted Install Retain OEM Key
Hello All,
I have successfully created a scripted install that deploys Windows 10 and various applications to my companies workstations using the K2000. However, the newest batch of computers that we have purchased come with Windows 10 preinstalled. I am wondering how to alter my scripted install to use the already activated Windows 10 OEM key instead of using our volume license.
Thanks in advance
I have successfully created a scripted install that deploys Windows 10 and various applications to my companies workstations using the K2000. However, the newest batch of computers that we have purchased come with Windows 10 preinstalled. I am wondering how to alter my scripted install to use the already activated Windows 10 OEM key instead of using our volume license.
Thanks in advance
1 Comment
[ + ] Show comment
-
If the pre-installed Windows 10 is already activated just install the same version without a key. At first connection the newly installed Windows 10 will automatic be activated again based on the hardware "id" that is captured at the first activation. - anonymous_123154 8 years ago
Answers (4)
Answer Summary:
Please log in to answer
Posted by:
therealredzac
7 years ago
I've created a small script to set the "OA3xOriginalProductKey"
to the current windows key at os deployment.
UEFI must be activated to use this VBS.
Reboot after run
' SetOEMKey.vbs
on error resume next
dim OEMKey
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2")
Set colItems = objWMIService.ExecQuery( _
"SELECT * FROM SoftwareLicensingService",,48)
For Each objItem in colItems
OEMKey = objItem.OA3xOriginalProductKey
Next
IF OEMKey="" then
'No UEFI OEM Key found or UEFI is disabled
Err.Number="1"
WScript.Quit(Err.Number)
ELSE
'Set UEFI OEM Key
Set objShell = WScript.CreateObject("WScript.Shell")
objShell.Run """C:\Windows\System32\cscript.exe"" C:\Windows\System32\slmgr.vbs -ipk """ & OEMKey , 1, True
Set objShell = Nothing
WScript.Quit(Err.Number)
end if
WScript.Quit(Err.Number)
Posted by:
rileyz
8 years ago
I pretty sure you will need to change the WIM and the VLK media has a diff SKU. You will need to use consumer media Pro or Home, but this edition will be unable to connect to a domain.
To activate, just install with the generic licence key (for home or pro) - you can google that, once the machine is online, it will just grab its digital licence from the mothership (Microsoft).
Comments:
-
Thank you for your response. The OEM key that shipped with the computer was for Windows 10 Pro. I am not sure that using the consumer based media would be the correct solution. - jmiller99 8 years ago
-
Oh you can join 10 Pro to a domain, my bad.
Hummm, you could try and change the product key after install?
http://www.thewindowsclub.com/default-product-key-to-upgrade-from-windows-10-home-to-pro
So after image, change the key to the above, this is a default Win Pro key - the system should try and activate to grab its digital entitlement (OEM key) and activate correctly.
Im just not sure if you WIM will work, as mentioned, your image uses a VLK key which is Enterprise media (diff SKU) and the Pro that came with the laptop is a non-enterprise.
Give it a shot i say! All you can do really. Hopefully the key swap will do the the job and im proven wrong on the media front (: - rileyz 8 years ago
Posted by:
SMal.tmcc
8 years ago
I agree with rileyz, you will need to use win 10 pro to use the built in key, you can download that version from the MS-VLSC and use that version for the scripted install. You may have to link your MS Account with the digital license prior to imaging. This will allow you to re-activate that license on that machine.
Comments:
-
windows 10 key here: TGP3J-N7B4K-6K632-YMXHV-X766T from vanskeys. - vanskeys 6 years ago
Posted by:
jmiller99
8 years ago
Top Answer
The solution to my problem came by entering wmic path SoftwareLicensingService get OA3xOriginalProductKey into cmd of the soon to be imaged computer. This outputted the OEM key which could then be plugged in manually to deployed machine.