Windows 10 Licensing
-
@dafyre said:
If you already have a KMS server, why worry with extracting the BIOS keys?
Because legally you still need to upgrade the OEM license on a machine before you can install your Open License version of Windows 10 on the machine.
While you can physically skip this step, legally you can't.
-
I would have had this done but our Hyper-V lab/WDS stuff is messing up.
-
@Jason said:
I would have had this done but our Hyper-V lab/WDS stuff is messing up.
I'm still considering options of what media to use? Can a KMS key be used with the generally available ISOs?
-
-
@Dashrender said:
@Jason said:
I would have had this done but our Hyper-V lab/WDS stuff is messing up.
I'm still considering options of what media to use? Can a KMS key be used with the generally available ISOs?
Not legally, if you are imaging.
-
@Jason said:
@Dashrender said:
@Jason said:
I would have had this done but our Hyper-V lab/WDS stuff is messing up.
I'm still considering options of what media to use? Can a KMS key be used with the generally available ISOs?
Not legally, if you are imaging.
Not sure why that would be the case? But assuming that's right, and our goal is to install Windows 10 only once, we'd what?
Deploy an image of an Open License media based install, once in the OS, change the key to the Windows 8.1 key, activate with MS (hopefully), then change the key again this time to KMS keys and activate against our KMS server?
-
@Dashrender said:
@Jason said:
@Dashrender said:
@Jason said:
I would have had this done but our Hyper-V lab/WDS stuff is messing up.
I'm still considering options of what media to use? Can a KMS key be used with the generally available ISOs?
Not legally, if you are imaging.
Not sure why that would be the case? But assuming that's right, and our goal is to install Windows 10 only once, we'd what?
Deploy an image of an Open License media based install, once in the OS, change the key to the Windows 8.1 key, activate with MS (hopefully), then change the key again this time to KMS keys and activate against our KMS server?
That's kinda what we are looking at trying.. There's nothing from MS that forbids that way.
The reason that isn't legal is imaging rights require the use of both Volume Keys and Volume Media.
-
@Jason said:
The reason that isn't legal is imaging rights require the use of both Volume Keys and Volume Media.
While I'm sure that's the idea (and it's likely that KMS keys won't work with OEM'ish media) I don't recall reading anything specific about the use of Open License/Volume media.
-
@Dashrender said:
@Jason said:
The reason that isn't legal is imaging rights require the use of both Volume Keys and Volume Media.
While I'm sure that's the idea (and it's likely that KMS keys won't work with OEM'ish media) I don't recall reading anything specific about the use of Open License/Volume media.
I think it will work.. It's not a technical limitation but a licensing one. Imaging rights strickly require Volume Keys and MEDIA.
-
Well I'm building a machine right now, slipping in some apps, then I'll take an image before trying to replace the key with window 8.1
-
OK just tried it.
Windows 10 Volume License media with a Windows 8.1 OEM key (pulled from the BIOS).
The error: You are running Windows 10 Pro. The product key you entered cannot be used to activate this edition.
Error Code:0x004f210Looks like we are still stuck upgrading like normal first.
-
They really need a tool to handle this.
