Forum Discussion
Change from local KMS to M365 E3 Windows activation fails
Did you manage to work this out, I am seeing devices that are running enterprise 1803 with a KMS key and when a Windows 10 Enterprise user with a licence logs in it does not convert to M365 licence it just shows error that it can not contact KMS server (Road warrior user that has not access to internal network).
Hi
Sorry no solution yet, we are still working with Microsoft to fix it. We have issues with Lenovo Thinkpads if they have no Windows Key in BIOS.
Regards, Marcel
- Ben HosJan 07, 2019Copper Contributor
Looks like you were having a similar issue to us but with a little more complication, turns out the device needs to have an activated license to apply the Windows 10 Enterprise subscription license. Fortunately for us the devices all have bios level licenses so I just wrote a quick powershell script that rips out the un-activated KMS license and pulls the one from the BIOS, adds it and activates it.