Forum Discussion

Peter Holzinger's avatar
Peter Holzinger
Copper Contributor
Feb 15, 2019

M365 Win 10 E3 activation issue

Hi!

 

We have deployed M365 in a hybrid environment.

But we have problem to activate six computers with the Win 10 E3 license. 

We get this activation problem: 

The language above is Swedish, but it says that the subscription is active, but the activation has not been activated. The error code is 0x8007232b.

 

From the beginning these six computers had Win 10 version 1709 but they are now upgraded to 1803. They are all hybrid joined in Azure AD (with GPO).

 

I've read all the MS documentation (i.e. https://docs.microsoft.com/en-us/windows/deployment/deploy-enterprise-licenses#win-10-activated-subscription-active) but I can't find any solution.

 

 

I really appreciate if someone could help me 🙂

 

Kind regards,

Peter Holzinger

  • derek_poon's avatar
    derek_poon
    Copper Contributor

    Peter Holzinger 

    I deployed customized Win10 Pro images via MDT.  Server 2019 are set up with a .local domain and UPN added for connecting to Azure Domain.  Once the machine (client PC with Win10 Pro) installed and joined the domain, as I assigned Microsoft 365 E3 + Win10 Enterprise E3 to the users (domain\user), the Win10 Enterprise activated.  My question is that the Office 365 installed via Office Deployment Tool still in GRACE period of 5 days counting down.

    How to solve this issue ?

    dsregcmd /status returned the Machine is Hybrid Azure AD joined.

    • Mark Masiak's avatar
      Mark Masiak
      Copper Contributor

      derek_poon 

       

      the user needs to login to their Office 365 Account in Word/Excel

       

      Either in the top right hand corner

      or

      File...Account

       

  • Mark Masiak's avatar
    Mark Masiak
    Copper Contributor

    Option 1 

    Microsoft E3/E5 needs Windows 10 Pro Licence on first to install Windows 10 Enterprise, if you didn't have W10Pro then you need to purchase and install that first. 

     

    Option 2

    "Cannot connect to server" this sounds like it has registered a KMS instead of a MAK key. 

     

    See if it is looking for a KMS Server:

    Open CMD as an administrator. At the command prompt, type the following command, and then press ENTER: nslookup -type=all _vlmcs._tcp>kms.txt

    Open the KMS.txt file that is generated by the command.

     

    Option 3

    Sometimes there are registration delays in validating licences, keep trying and also check to see if the client isn't being blocked by your firewall

     

    Option 4

    the Microsoft E3/E5 requires the PC to be Azure Joined and the user to have rights to join Azure, make sure the registered user has permission in AAD. 

     

    Option 5

    Make sure the PC is up to date with the latest updates AAD has a minimum requirement

    is updates fail, delete the Windows Update Cache and run this in elevated CMD

    wuauclt.exe /detectnow /updatenow

     

     

    • FarmhouseNetworking's avatar
      FarmhouseNetworking
      Copper Contributor

      My client purchases WIndows 10 Home computers from big box stores. We run the update to Windows 10 Pro via the Microsoft Store ($99) then connect the computer to Azure AD as all users have Microsoft 365 licenses. I thought the upgrade would be to Windows 10 Business, so why does it show Enterprise and not able to activate? Mark Masiak 

    • Peter Holzinger's avatar
      Peter Holzinger
      Copper Contributor

      Hi!

       

      My issue was that this computer was purchased with a Win 10 Home license. I've purchased a Pro-license and after that everything works fine.

       

      Thank you all for your replies!

       

      //Peter

      • ahughs's avatar
        ahughs
        Copper Contributor

        Peter Holzinger- This was super helpful! We had a very similar issue. What ended up happening for us, was that the imaged machine was refurbished and the product key wasn't able to be queried via wmic due to the refurbishing process. To resolve it, we entered the product key manually based on what was on the sticker on the computer itself. After re-entering this key the Activation worked.

  • Tommy1949's avatar
    Tommy1949
    Copper Contributor
    Please disconnect me from Office365. I cannot do that myself.

Resources