Change from local KMS to M365 E3 Windows activation fails

%3CLINGO-SUB%20id%3D%22lingo-sub-291568%22%20slang%3D%22en-US%22%3EChange%20from%20local%20KMS%20to%20M365%20E3%20Windows%20activation%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291568%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20past%20we%20used%20a%20local%20KMS%20server%20for%20our%20Windows%2010%201803%20Enterprise%20installations.%20Now%20we%20have%20M365%20E3%20subscribtions%20and%20moved%20the%20laptops%20to%20AAD.%20If%20I%20do%20a%20slmgr%20%2Fxpr%20it%20Always%20shows%20an%20end%20date%20of%20the%20License.%20I%20did%20slmgr%20%2Fipk%20NPPR9-FWDCX-D2C8J-H872K-2YT43%20and%20a%20logoff%2Flogon%20with%20username%20and%20Password%20but%20still%20get%20an%20error%20like%20the%20KMS%20server%20of%20your%20organisation%20is%20not%20found...%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20can%20I%20do%20to%20motivate%20Windows%20to%20go%20to%20M365%20to%20validate%20the%20License%3F%20Thanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309816%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20from%20local%20KMS%20to%20M365%20E3%20Windows%20activation%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309816%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20you%20were%20having%20a%20similar%20issue%20to%20us%20but%20with%20a%20little%20more%20complication%2C%20turns%20out%20the%20device%20needs%20to%20have%20an%20activated%20license%20to%20apply%20the%26nbsp%3BWindows%2010%20Enterprise%26nbsp%3Bsubscription%20license.%26nbsp%3B%20Fortunately%20for%20us%20the%20devices%20all%20have%20bios%20level%20licenses%20so%20I%20just%20wrote%20a%20quick%20powershell%20script%20that%20rips%20out%20the%20un-activated%20KMS%20license%20and%20pulls%20the%20one%20from%20the%20BIOS%2C%20adds%20it%20and%20activates%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309423%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20from%20local%20KMS%20to%20M365%20E3%20Windows%20activation%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309423%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20no%20solution%20yet%2C%20we%20are%20still%20working%20with%20Microsoft%20to%20fix%20it.%20We%20have%20issues%20with%20Lenovo%20Thinkpads%20if%20they%20have%20no%20Windows%20Key%20in%20BIOS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%20Marcel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309128%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20from%20local%20KMS%20to%20M365%20E3%20Windows%20activation%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309128%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20manage%20to%20work%20this%20out%2C%20I%20am%20seeing%20devices%20that%20are%20running%20enterprise%201803%20with%20a%20KMS%20key%20and%20when%20a%20Windows%2010%20Enterprise%20user%20with%20a%26nbsp%3Blicence%20logs%20in%20it%20does%20not%20convert%20to%20M365%20licence%20it%20just%20shows%20error%20that%20it%20can%20not%20contact%20KMS%20server%20(Road%20warrior%20user%20that%20has%20not%20access%20to%20internal%20network).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-654781%22%20slang%3D%22en-US%22%3ERe%3A%20Change%20from%20local%20KMS%20to%20M365%20E3%20Windows%20activation%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-654781%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F246156%22%20target%3D%22_blank%22%3E%40Marcel100%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehave%20you%20had%20a%20response%20yet.%20I%20too%20have%20a%20project%20that%20involves%20your%20steps%20and%20was%20wondering%20how%20you%20were%20going%20about%20it.%20Windows%2010%201703%20KMS%20Enterprise%20moving%20to%20M365%20E5.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20process%20I%20was%20thinking%20was%20to%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20remove%20KMS%20key%3C%2FP%3E%3CP%3E2.%20interrogate%20bios%20for%20Pro%20Key%3C%2FP%3E%3CP%3E3.%20install%20and%20activate%20Pro%20Key%3C%2FP%3E%3CP%3E4.%20following%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fdeploy-enterprise-licenses%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fdeploy-enterprise-licenses%3C%2FA%3E%26nbsp%3Bto%20activate%20enterprise.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20script%20below%20hopefully%26nbsp%3B%20will%20perform%201-3%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%40echo%20off%3CBR%20%2F%3Eecho%20Remove%20KMS%20Key%3CBR%20%2F%3Eslmgr.vbs%20%2Fupk%3CBR%20%2F%3EFOR%20%2FF%20%22skip%3D1%22%20%25%25A%20IN%20('wmic%20path%20SoftwareLicensingService%20get%20OA3xOriginalProductKey')%20DO%20(%3CBR%20%2F%3ESET%20%22ProductKey%3D%25%25A%22%3CBR%20%2F%3Egoto%20InstallKey%3CBR%20%2F%3E)%3CBR%20%2F%3E%3AInstallKey%3CBR%20%2F%3EIF%20%5B%25ProductKey%25%5D%3D%3D%5B%5D%20(%3CBR%20%2F%3Eecho%20No%20key%20present%3CBR%20%2F%3E)%20ELSE%20(%3CBR%20%2F%3Eecho%20Installing%20%25ProductKey%25%3CBR%20%2F%3Echangepk.exe%20%2FProductKey%20%25ProductKey%25%3CBR%20%2F%3E)%3C%2FP%3E%3CP%3Eslmgr.vbs%20%2Fato%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Enot%20sure%20if%20this%20helps%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

In the past we used a local KMS server for our Windows 10 1803 Enterprise installations. Now we have M365 E3 subscribtions and moved the laptops to AAD. If I do a slmgr /xpr it Always shows an end date of the License. I did slmgr /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43 and a logoff/logon with username and Password but still get an error like the KMS server of your organisation is not found... 

 

What can I do to motivate Windows to go to M365 to validate the License? Thanks

 

4 Replies

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

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.

Hi @Marcel100 

 

have you had a response yet. I too have a project that involves your steps and was wondering how you were going about it. Windows 10 1703 KMS Enterprise moving to M365 E5. 

 

The process I was thinking was to; 

 

1. remove KMS key

2. interrogate bios for Pro Key

3. install and activate Pro Key

4. following https://docs.microsoft.com/en-us/windows/deployment/deploy-enterprise-licenses to activate enterprise.

 

The script below hopefully  will perform 1-3 

 

@echo off
echo Remove KMS Key
slmgr.vbs /upk
FOR /F "skip=1" %%A IN ('wmic path SoftwareLicensingService get OA3xOriginalProductKey') DO (
SET "ProductKey=%%A"
goto InstallKey
)
:InstallKey
IF [%ProductKey%]==[] (
echo No key present
) ELSE (
echo Installing %ProductKey%
changepk.exe /ProductKey %ProductKey%
)

slmgr.vbs /ato

 

not sure if this helps you.