Dynamic OS selection based on the embedded key

Having the default set to Windows Pro Retail probably covers 80-90% of deployments, but for the rest it would be great to see the OA3 data queried so that techs do not necessarily have to touch the OS Edition drop down menu and therefore reduce the chance for errors.

While the following works in Windows, SoftwareLicensingService is not active in WinPE and therefore does not work.

(Get-WmiObject SoftwareLicensingService).OA3xOriginalProductKeyDescription

I know David is looking to package the OA3 tool into WinPE, so perhaps this can be leveraged to obtain the OriginalProductKey and/or OriginalProductKeyDescription.

For example, our org purchased a batch of devices with the ProfessionalEducation SKU instead of Pro.

Since none of the publicly available ESD files contain ProfessionalEducation, it would be nice to see this value queried and added to the Edition drop down anyway. The device would be imaged with Pro and then later, SetupComplete logic (or similar phase), could then change the edition with the generic key for ProfessionalEducation: “changepk.exe /ProductKey 8PTT6-RNW4C-6V7J2-C2D3X-MHBPB” allowing the embedded key to activate without user intervention.

Another idea where volume licensing is required, could be to have OSDCloud search for a file containing MAK keys (example path: “$WinPE$\MAK_Enterprise” or $WinPE$\MAK_Education”) and then apply them with slmgr.vbs or similar.