@abbodi1406 Yah, I have tried that too. Setting VL in ei.cfg even displays the VL license agreement, but installs the same key . BTW, the alternate way is rather cryptic @s1ave77 Thanks for confirming.
@All, specially abbodi1406 or s1ave77 or murphy78 Please maintain a thread for CC, CCSL, CCCS & PS SKUs.
Good to see you already do it . As abbodi already mentioned that would need MS to release them first . Only generated ones so far.
The package contains the default OEM/Retail key Enterprise and Pro VL has extra "Security-SPP-Component-SKU-*-GVLK-Package" which contains the gVLK key other editions don't without the product.ini, no chance
Hmm... yah you're right. Unless we get a leak of a vl build or something, I don't see that happening. Maybe we'll get a product.ini somehow... When do we typically get those? evaluation builds?
Try one of those generated gVLK (kms keys) from abbodi's unofficial kms script. Then activate with MTK.
I'll see what I can do... I was planning on sharing the img files with a certain nefarious website, so we can just use the same magnets since they won't be modified.
Should be applicable for all Core builds (equal whether Connected or not). Would guess the Pro Student should be 180 .