Hello Spireworks community!

I’m really stuck :frowning: any help would be greatly appreciated.

Created and deployed MSI Office (Click-to-Run) to domain computers end of 2018, patching updates via Desktop Central all happy days.

Users sign-in (Office Apps) and bingo it’s all good but not anymore.

Yesterday Users started reporting that Word, Excel etc are in View mode. See screen grab

We have O365 Business Premium all Users have Office enabled via Admin Portal.

Seems like the Office update has messed things up? or did i deploy the wrong installed a year ago? i’m lost…

Thank you for any help!

Leo.

4 Spice ups

I’d start by trying to fix with a user that has local admin rights. Update the Office software manually (file, account, update) and ensure the install is synced/authorized with the same user’s O365 account. The activation state may need to be reset:

https://blogs.technet.microsoft.com/odsupport/2015/05/01/how-to-reset-an-office-365-install-to-the-initial-activationinstall-state/

(Note the automated script link at the bottom of the article, haven’t tried it but might help.)

How did you do the original install? Did you download the small installer while logged in as a user and then use that on multiple machines?

Thanks @jonolson ​ i’ll give that a go. I’m Admin of my machine as domain user but will try as local Admin user too. When i tired to update Word manually i got an error so gave up but will try your suggestion and link etc. Thank you!

@da-schmoo ​ Hi ermmm no i don’t think so. I needed to remove Outlook and Access from the click and run installer and i couldn’t figure out the cmd scripted way so i found something on Github that provided a UI to create the MSI. I then deploy that silently. From memory it installs proplus click and run which then turns into Microsoft Office 365 Business. Hope that makes some sense. Thanks for your help :slight_smile:

No telling what that script you use did.

The link above should fix you up. Step 1 is all you should need to do and any Office app should prompt the user to activate next time it’s run.

I did encounter strangeness like this when having 32 and 64 bit installs and had to clean up fully and then re-install.

Look at the INFO - Office Account to get the Product installed version

Hmmmm, since you don’t know exactly what this script did, uninstall/reinstall would be the way I would go.

@da-schmoo %u200B @jonolson %u200B Well that didn’t go so well unfortunately :frowning: I ran the vb script but had no effect. I then worked through the article from top to bottom, again hoped step 1 would solve it but no joy, then carried on to the end. In removing items from regedit etc it has done something because it’s forced me to sign back in, see screen grab but it now errors so i think something is definitely broken/ i broke it.

I have a support ticket with Microsoft so will try that on a different machine. Obviously looking for a simple fix rather than uninstalling and re-installing on 50 plus computers. nightmare…

Thanks for your help regardless! :slight_smile:

Leo.

@da-schmoo @jonolson Hiya, well that didn’t go so well. I used the script but it didn’t resolve the problem. I then worked through the steps, item 1 didn’t solve it but it did remove the license according to the cmd output. I then worked through the rest of the steps. Something did work in terms of removing my sign-in but in doing so it’s broken something else. See attached.

I have a ticket open with Microsoft so i’m working that on another machine.

Obvs dont really want to uninstall and re-install on 50 plus computers and even if i do i’d need to compile a new msi somewhere to ensure this nightmare wont happen again…

Thanks for your help thus far!

Leo

Found a forum post from Susan Bradley (very knowledgeable about update problems):

The word on the street is that Outlook is wanting MFA. So either you have to turn on MFA or disable ADAL

Fix get them onto MFA or

Close Outlook
Open Regedit
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity

Create REG_DWORD
EnableADAL
0

https://answers.microsoft.com/en-us/msoffice/forum/all/trusted-platform-module-has-malfunctioned/cec115e3-5201-4aed-90b2-297c5604c1c9?auth=1

Thanks @jonolson ​ The Outlook App isn’t installed as part of the Office suite installed. It’s one of the Applications i excluded from the package. We use Outlook online. We use Microsoft MFA, not everyone but many and it’s not related in this instance. But, i have had issues with Mac Users and MFA so appreciate the complexity.

I’m using these resources to generate a new xml and deploy from our local deployment server.

https://config.office.com/officeSettings/

The above seems the standard way to do this which kinda explains why my github msi deployment has gone down the toilet.

Thanks all,

Leo.

This has now been resolved. Deployed the newly created package to all targets. No need to uninstall manually.
Thanks,
Leo.