It is defined in the SKU specific EditionMatrix.xml & UpgradeMatrix.xml - you can find them under %windir%\servicing\Editions. In newer builds, Microsoft introduces clubbed up licenses for similar adjacent SKUs so that switching from one to another is seamless & doesn't require servicing methods by DISM, but those rules aren't part of these matrices. For a particular build, available SKUs may be different & thus the matrices may change. Those are defined in the pkeyconfig digital license. @Enthousiast Unfortunately my test PCs already have Pro digital entitlement, thus need to spawn a VM to test it. Regarding upgrading (technically switching) from Pro to ProWS using -XD863 on certain builds is possible because it's key ranges are defined on those builds' pkeyconfig. AFAIK, when RS3 is finalized that range is dropped, thus you can't parse the key using 16299(.15) pkeyconfig.
I never activated using a digital license before but tried now in a VM with build 16281 and the key that ends with XD863 to activate and then copy over GenuineTicket file to a 16299.15 Pro WS VM, it activated fine. Does anyone know if it would be possible to install 16299.15 Pro WS on a PC and then activate using a Windows 8 key? Or do I have to do the same procedure I did in VM?
I did the initial 16257.1 install and the upgrade to 16296 with the en-US iso's but i didn't have the 16299.15 iso ready to go in en-US so i used my Dutch AIO iso for the final clean install, should also work with en-US, For my 16278 > 16299.15 test i am preparing all iso's in en-US.
Common, how many times is that already posted? I posted the manual way months ago and again a few weeks ago when i discovered that the key activated it at 16251 or 16257, iirc @ambidav posted it last week too, easiest way is to simply use @s1ave77's wes (WIM EDITION SWITCHER), it does all for you.
For those who don't care about 100% genuine activation, yes Establishing the HWID is just for learning, i don't even have hardware that needs it to be run, and it kept me out of the streets
I think it is THE ULTIMATE TEST since if Microsoft thinks it is activated, then surely it is really activated!
Not for testing how to establish a hwid, as said, he can install it on any hardware and when he uses his linked MSA it will be activated by transferring the HWID to the newly used hardware.
Microsoft does not like me and so KMS is my only solution. I have used the previously mentioned key numerous times in the older builds (also previously mentioned) and while that key will activate (in the older builds), I cannot obtain hardware activation upon the upgrade. Furthermore, once I upgrade, I'm told that key is no longer good and that I need a new one (and no, I am not entering the key in the newer build either).