Windows 10 Enterprise activation error with Intune

%3CLINGO-SUB%20id%3D%22lingo-sub-1960614%22%20slang%3D%22en-US%22%3EWindows%2010%20Enterprise%20activation%20error%20with%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1960614%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Folks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eim%20working%20for%20a%20project%20where%20all%20devices%20(currently%20running%20with%20Windows%2010%20LTSC%201809%2C%20LTSB%20or%20Windows%207)%20are%20migrated%20to%20Windows%2010%20Enterprise.%20The%20goal%20is%20to%20manage%20all%20devices%20with%20intune.%20As%20the%20update%20path%20from%20all%20those%20versions%20to%20Windows%2010%20Enterprise%20is%20kinda%20difficult%20we%20are%20reinstalling%20them%20with%20a%20fresh%20Windows%2010%20Image.%20So%20far%20so%20good.%20The%20autounattend.xml%20is%20filled%20with%20a%20generic%20Windows%2010%20Enterprise%20Key%2C%20I%20want%20Windows%20to%20license%20the%20device%20with%20the%20Microsoft%20E3-License%20which%20is%20assigned%20to%20my%20user.%20The%20problem%20is%2C%20the%20device%20is%20not%20going%20to%20activate%2C%20saying%20KMS-Server%20isnt%20reachable.%20What%20am%20I%20doing%20wrong%20at%20that%20point%3F%20I%20bet%20its%20some%20kind%20of%20Logic%20error%20or%20I%20dont%20get%20the%20way%20microsoft%20is%20activating%20their%20devices%20with%20intune.%20Another%20problem%20i%20was%20thinking%20about%20is%20that%20the%20generic%20key%20makes%20the%20device%20to%20use%20the%20digital%20key%20which%20is%20of%20course%20a%20LTSC%20Key%2C%20not%20a%20Enterprise%20Key.%20Do%20you%20have%20any%20ideas%2C%20what%20I%20am%20doing%20wrong%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1960614%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1962274%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20Enterprise%20activation%20error%20with%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1962274%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F366035%22%20target%3D%22_blank%22%3E%40sebamedo%3C%2FA%3E%26nbsp%3BCan%20you%20check%20this%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fcommon-troubleshooting-procedures-kms-dns%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Edocument%3C%2FA%3E%3F%26nbsp%3B%3C%2FP%3E%3CP%3EI%20guess%20you%20have%20a%20KMS%20DNS%20SRV%20record%20in%20place%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20check%20this%20article%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fmattsoseman.wordpress.com%2F2018%2F09%2F21%2Fintune-upgrade-windows-from-pro-to-enterprise-automatically%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EIntune%3A%20Upgrade%20Windows%20Pro%20to%20Enterprise%20AUTOMATICALLY!%20%7C%20Matt%20Soseman's%20Blog%20(wordpress.com)%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hey Folks,

 

im working for a project where all devices (currently running with Windows 10 LTSC 1809, LTSB or Windows 7) are migrated to Windows 10 Enterprise. The goal is to manage all devices with intune. As the update path from all those versions to Windows 10 Enterprise is kinda difficult we are reinstalling them with a fresh Windows 10 Image. So far so good. The autounattend.xml is filled with a generic Windows 10 Enterprise Key, I want Windows to license the device with the Microsoft E3-License which is assigned to my user. The problem is, the device is not going to activate, saying KMS-Server isnt reachable. What am I doing wrong at that point? I bet its some kind of Logic error or I dont get the way microsoft is activating their devices with intune. Another problem i was thinking about is that the generic key makes the device to use the digital key which is of course a LTSC Key, not a Enterprise Key. Do you have any ideas, what I am doing wrong?

1 Reply

@sebamedo Can you check this document

I guess you have a KMS DNS SRV record in place? 

 

Also check this article: Intune: Upgrade Windows Pro to Enterprise AUTOMATICALLY! | Matt Soseman's Blog (wordpress.com)