Unable to activate Office 365 ProPlus E3

%3CLINGO-SUB%20id%3D%22lingo-sub-185126%22%20slang%3D%22en-US%22%3EUnable%20to%20activate%20Office%20365%20ProPlus%20E3%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-185126%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20currently%20running%20a%20Windows%2010%20trial%20with%20some%20users%20from%20our%20business%20and%20some%20users%20are%20unable%20to%20fully%20activate%20their%20Office%20365%20E3%20ProPlus%20Office%202016%20license%20on%20their%20computers.%20When%20signing%20in%20with%20their%20365%20credentials%20in%20an%20Office%20application%20they%20get%20stuck%20in%20an%20endless%20activation%20loop.%3C%2FP%3E%3CP%3EHaving%20run%20the%20command%20%22cscript.exe%20ospp.vbs%20%2Fdstatus%22%2C%20the%20user%20is%20only%20assigned%20the%20%22Office%2016%2C%20Office16O365ProPlusR_Grace%20edition%22%20license%2C%20rather%20than%20the%20%22Office%2016%2C%20Office16O365ProPlusR_Subscription1%20edition%22%20license.%20I%20myself%20do%20not%20have%20this%20problem%20and%20neither%20do%20the%20rest%20of%20my%20colleages%20in%20my%20IT%20Team.%20The%20users%20that%20have%20this%20problem%20initially%20had%20the%20license%20working%20for%20them%20and%20then%20when%20they%20last%20reset%20their%20on-premise%20passwords%20their%20Office365%20license%20appears%20to%20have%20reset%20itself.%3C%2FP%3E%3CP%3EIn%20the%20interim%2C%20I%20have%20had%20to%20license%20these%20users%20under%20my%20Office%20365%20subscription%20so%20they%20can%20continue%20working.%20This%20issue%20is%20logged%20with%20MS%20Support%20however%20they've%20so%20far%20asked%20me%20to%20try%20various%20troubleshooting%20scenarious.%3C%2FP%3E%3CP%3ESo%20far%20we%20have%20tried%20using%20cscript%20to%20remove%20any%20old%20licenses%2C%20cleared%20credential%20manager%20and%20removed%20identities%20and%20license%20info%20from%20liceses%20and%20app%20data%20locations.%20Yesterday%20we%20were%20able%20to%20license%20a%20user%20on%20a%20non-domain%20standalone%20laptop%20so%20this%20points%20to%20a%20possible%20problem%20with%20our%20infrastructure.%20One%20thing%20to%20note%20is%20that%20we%20login%20to%20our%20computer%20with%20ourdomain.co.uk%20however%20our%20email%20address%20is%20ourdomain.com%20and%20this%20is%20what%20is%20used%20for%20our%20O365%20sign-in%20identity%20-%20Microsoft%20suggested%20that%20our%20windows%20sign-in%20might%20be%20conflicting%20and%20suggested%20that%20our%20AD%20environment%20is%20likely%20the%20root%20cause%20of%20this%20issue.%20I%20tried%20changing%20a%20users%20on-premise%20login%20to%20ourdomain.com%20but%20that%20made%20no%20difference%20in%20regards%20to%20activation.%20Yes%20myself%20and%20my%20other%20IT%20colleagues%20as%20mentioned%20above%20have%20no%20problem%20activating%20office%20on%20affected%20users%20computers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-192179%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20activate%20Office%20365%20ProPlus%20E3%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-192179%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHave%20you%20tried%20creating%20this%20registry%20key%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%5BHKEY_CURRENT_USER%5CSoftware%5CMicrosoft%5COffice%5C16.0%5CCommon%5CIdentity%5D%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%20%22DisableADALatopWAMOverride%22%3Ddword%3A00000001%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EFor%20your%20referece%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4025962%2Fcan-t-sign-in-after-update-to-office-2016-build-16-0-7967-on-windows-1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4025962%2Fcan-t-sign-in-after-update-to-office-2016-build-16-0-7967-on-windows-1%3C%2FA%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

We are currently running a Windows 10 trial with some users from our business and some users are unable to fully activate their Office 365 E3 ProPlus Office 2016 license on their computers. When signing in with their 365 credentials in an Office application they get stuck in an endless activation loop.

Having run the command "cscript.exe ospp.vbs /dstatus", the user is only assigned the "Office 16, Office16O365ProPlusR_Grace edition" license, rather than the "Office 16, Office16O365ProPlusR_Subscription1 edition" license. I myself do not have this problem and neither do the rest of my colleages in my IT Team. The users that have this problem initially had the license working for them and then when they last reset their on-premise passwords their Office365 license appears to have reset itself.

In the interim, I have had to license these users under my Office 365 subscription so they can continue working. This issue is logged with MS Support however they've so far asked me to try various troubleshooting scenarious.

So far we have tried using cscript to remove any old licenses, cleared credential manager and removed identities and license info from liceses and app data locations. Yesterday we were able to license a user on a non-domain standalone laptop so this points to a possible problem with our infrastructure. One thing to note is that we login to our computer with ourdomain.co.uk however our email address is ourdomain.com and this is what is used for our O365 sign-in identity - Microsoft suggested that our windows sign-in might be conflicting and suggested that our AD environment is likely the root cause of this issue. I tried changing a users on-premise login to ourdomain.com but that made no difference in regards to activation. Yes myself and my other IT colleagues as mentioned above have no problem activating office on affected users computers.

1 Reply

Hi,

 

Have you tried creating this registry key:

 

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity]
"DisableADALatopWAMOverride"=dword:00000001

 

For your referece - https://support.microsoft.com/en-us/help/4025962/can-t-sign-in-after-update-to-office-2016-build-16-...