New
#140
Fellow geeks on any 17xxx build using subscription based Click-to-Run installed Office 2016 (O365 Personal / Home / Business / Enterprise), I would be very pleased if you would tell about what you see when running the following command in elevated Command Prompt:
cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /dstatus
In case you are running 64 bit Office, the command is:
cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus
Screenshot shows what you should see, one licensed Office installation:
(Click to enlarge.)
I've lately had a lot of issues with Office, it remains activated only five days then deactivating itself and giving continuous account errors when connecting to services like OneDrive, above command showing two SKUs / installations, one as in above "Everything OK!" screenshot (yellow highlight) and then another unlicensed "Grace Edition" with 5 day grace period (blue highlight):
(Click to enlarge.)
I am trying to get to the bottom of this weird issue, would appreciate any feedback from you guys. I suspect underlying issue has something to do with Windows Insider Preview builds, and probably also with the way I prepare my custom W10 deployment images.
Thanks in advance,
Kari