Windows 10: Product keys and naming?
-
@x23piracy That’s one way, but I’m using an actual Win10 enterprise key with fresh Win10 enterprise images.
-
Yeah I think I have understand the fact that I must upgrade/clean install Windows 10 (and enter key) before the machine is “upgraded”.
So what do you guys do about embedded Windows keys on laptops? Do I really have to dig em all out 1 by 1?
But just to be clear, once the machine is upgraded - the product key part on FOG should work - yes?
-
@MadsMagnus once a windows 10 has been activated (embedded or upgraded) there is no need to enter a key it will just activate fine.
I have a lot upgraded pc’s and when i image key can also be empty it will activate the stored information on the ms activation servers.
Regards X23
-
@x23piracy said in Windows 10: Product keys and naming?:
@MadsMagnus once a windows 10 has been activated (embedded or upgraded) there is no need to enter a key it will just activate fine.
I have a lot upgraded pc’s and when i image key can also be empty it will activate the stored information on the ms activation servers.
Regards X23
While true without fog, this is not true in the sense of the FOG Client and how it operates.
If the key in the FOG DB does not match the local key, the client will change it and then activate it.
-
When you say product key, you mean the newly generated product key from Windows 10 yes? Because right now I am trying to get this running by using our Windows 7 COA keys.
-
@MadsMagnus I don’t believe there’s currently a way to extract the upgraded W10 key because they’re stored solely on W10 servers and all you get on your PC is a dummy key.
-
@MadsMagnus No mater how the key got there on the local host - if there is a different key set in the host’s Product Key field in the FOG DB, the new client will change the host’s key to the one from the FOG DB and then activate it.
If you don’t want that to happen, leave the product key in FOG blank, or make sure the key stored matches (somehow).
Also - going to ask @jbob to clairify when he gets time. Because of course I’ve been totally wrong before. But if I remember right, this is what he said about it.
-
Do you know if it is the OA/OEM key that you fx would find on the COA of a machine - or the “translated” product key that is used once a machine is running W10? Because I cannot seem to find my original key anywhere once W10 is installed.
-
@MadsMagnus the key value you put in the fog GUI is the very familiar 25 character Windows cd key nearly everybody is made aware of. If the machine you’re seeing this came with Windows 7 originally, the product key should be on the machine or with the user documentation/disks/books or whatever from when you got the machine. OEM keys are often stored in a SLIC format and the BIOS is queried to verify and activate the key automatically. In regards to Windows 8/8.1/10 I’m not sure how it knows what to do but it is usually automated and OEM still follows a very similar form.
-
@Tom-Elliott Windows 8 often reads the key straight from BIOS if I’m not mistaken (assuming there is one in BIOS), Windows 10 checks with Microsoft servers if your computer is registered or not. (in other words, once registered, you no longer need the Windows 7 keys since it will activate off of the Microsoft servers).
However, I don’t know how it works if you want to use W7 keys to activate it. How does FOG enter the product key? Does it use the registry?
-
@Quazz That is a question best left for answer by @joe-schmitt.
I don’t understand C# code, but I can follow “logic” paths so, if you’re anything like me in the sense of reading:
If I’m reading into this properly, it would appear it’s using Windows native DLL’s to perform the checks and activation process.
-
@Quazz it uses slmgr.
Example:
private static bool InstallProductKey(string key) { Log.Entry(LogName, "Installing Product key"); return RunSLMGR("/ipk", key) == 0; }Check Windows + R > slmgr.vbs /?
Regards X23
