Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
OK so it's now December and MAU 4.18 has come out along with Office 16.32. None of these are working under auto-update so I've downloaded them manually off the MS website and I'm in the process of manually installing them onto my MAC.
Just noticed something that I overlooked before...
Please correct me if this is wrong.
When you use MAU, it tries to download the packages for each application using it's own MAU programming and logic. And that's what fails. By the logs, it shows that it does determine that the packages installed are out of date and need to be updated but then as it goes to download them it does get them downloaded but then fails a checksum error of some kind and cannot proceed. This all happens under the control of MAU.
Now when I download these packages manually, I download a package that contains all applications for office 365 and that downloads fine - it works as a part of the normal procedures under Safari and whatever else Safari uses to download the packages - they download no problem.
And I have looked at the logs and am convinced that these two approaches - auto and manual take these packages off the same MS server - the link provided on the MS website just lets me download from that resource server manually.
But now when I opened that package to install - I have already passed the failure point that we're having trouble with - the package downloaded onto my desktop and is ready to install.
And it does install - it runs under the Apple installer which is called by the MS package, and the install goes fine. (there it just finished while I was typing and all applications are now 16.32 and running fine.
So there is no issue with the packages on the MS server - they are the same. And there is no issue with installation - that's the same basic utilities. The problem is with MAU and how it downloads the packages and accounts for successful download.
Now you can say that's an Apple problem if you want but when MS can't download a package successfully from their own server on a Mac that can otherwise download and install that package, I would say that's a problem that MS should be solving. Even if they find that Apple did something wrong, they're going to save face with a hell of a lot of MS 365 paying customers.
OK I get it - not enough 365 customers are impacted and we're willing to 'take the heat' from a few paying customers who have a problem that just isn't on our radar - kind of like TRUMP logic - hey, yes they paid us and we didn't give them a fully functional application that we promised, but go tell them not to be such babies - you babies!!! - suck it up, as far as we're concerned we keep all our promises - most of them.
Sorry for the "tyrade" now I sound just like all the other babies and complainers - I hate when I do that. Complaining never fixes anything and it certainly doesn't motivate people who could fix this. And what we work on is usually a management decision anyway and not the guys who fix things.
So as an old FS guy, I get it. I will just keep posting stuff I believe is helpful and hoping that someone will get an inspiration.
Regards.