Yesterday we were able to license a user on a non-domain standalone laptop so this points to a possible problem with our infrastructure. 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. This issue is logged with MS Support however they've so far asked me to try various troubleshooting scenarious. In the interim, I have had to license these users under my Office 365 subscription so they can continue working. 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. I myself do not have this problem and neither do the rest of my colleages in my IT Team. 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. When signing in with their 365 credentials in an Office application they get stuck in an endless activation loop. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |