Change Windows 10 from volume license (VLK Pro/Enterprise key) to use the key machines built-in key

-
Felt a bit stupid today (again). Have been struggling with some Microsoft Surface Go devices. Love the device but, when they are shipped with Windows 10 1803 version you will use some time updating them. So my brilliant idea was to reinstall them clean with the latest updated ISO from a stick. Smart right?, jupp except that I download the business VLK version.
So should I wipe and reload? (again). No, I am too lazy for that. There is then a couple of options.
  • Reset the license key information
  • Get the key from bios
Let's start with the easiest way that I did go for in this case. Reset the license key information.
I knew that you can force in the default keys for Windows 10, it's the same process as downgrading from Enterprise as explained in this blogpost: Downgrade Windows 10 Enterprise to Professional

It is possible to this sexier by using command lines of course:

Start a command prompt in administrator mode and type the following
  • slmgr -ipk VK7JG-NPHTM-C97JM-9MPGT-3V66T
  • slmgr -ato
Funny thing is that this the key explained should not be able to activate, but it did activate following the mentioned blog (did not try the command lines at this point, but more to follow on that ;-)  I presumed that this was just working since it had automatically gone into the bios and gotten the right key. This the default behavior it would have done using this type of keys with MDT or SCCM.

I wanted to try another method for fun, that I used a lot of times with Windows 7 machines that had license key in Bios. I remembered using wmic command line, script and a Nirsoft tool at different times.

A quick talk to Mr.Google and I found this nice blog post: How to find your original Windows 10 key
Lots of different ways. Going for the sexy command-line style we have these options:
  • From the command prompt:
    wmic path softwarelicensingservice get OA3xOriginalProductKey
  • From PowerShell:
    powershell "(Get-WmiObject -query ‘select * from SoftwareLicensingService’).OA3xOriginalProductKey"

And it was now I realize something wasn't right. It shows me the "VK7JG-NPHTM-C97JM-9MPGT-3V66T" key

The benefit with Nirsoft tool is that it shows both your active key and your bios key.
And as suspected the keys were different. So I copied the "Bios OEM" key and used the slmgr commands.
  • slmgr -ipk <Bios OEM Key>
  • slmgr -ato
Tried the Wmic command and the Nirsoft tool again and everything are now looking like it should. Sweet. Time saved, and I used the time to write this ;-)

It might happen that the product key would have been updated automatically, but it is better to be sure. Drop me a line if you know that it will do this, and I will update and give you credit for it.
   

Popular posts from this blog

Installing Android on a Hyper-V virtual machine

-
Image
Working with mobile device management (MDM) require a lot of testing. With Windows 10 testing is no problem (except those things that demand to be done on a physical device by different reasons), they can easily be run virtual. But when it comes to phones and tablets it have not been that easy. Visual Studio and some other solutions where out there, but they did not come with Store access or they had dependence which excluded Hyper-V from running. Some Emulators runs in a Hyper-V VM with Windows 10, but not on the host itself. So, if you got it to work it was usually slow and painful.
Read more

Quick guide on how to run BgInfo background as Group Policy login

-
Image
I know, it's simple. But I always forget some minor details when it have been a while since last time. So this blogpost is more a reminder to my self. Goal = Get same background picture an all PC (and/or Server) Doing it very simplified and easy in this guide, but you should normally use  folder structure for the files and a suitable Group Policy or more for the setting themself.
Read more

MDT: TimeZoneName and index number list

-
Remebering time zone name and number are a hasle so here are the list for the next time you (or I) need it. Norwegian settings for MDT are: TimeZone=110 TimeZoneName=W. Europe Standard Time (InputLocale=0414:00000414) (KeyboardLocale=nb-NO) The complete list are as following:
Read more