@dmatth01 This is what I tried this morning and it seems to be working well. I re-downloaded the installer from portal.office.com (365 subscription).
It updated an existing install without forcing the apps to close. I had Word and Excel open during the upgrade (ran via Casper Remote)....after the install I relaunched and saw the new version numbers. Didn't see any ill effects yet.
I wonder if the apps are currently being developed by different subgroups and/or if MS plans to release them as separate apps possibly when out of beta? That might explain the separate packages. It's nice in some ways to get updates to fix problems on one of the apps instead of waiting for a combined update that covers everything. It may indeed speed up fixes, which I would be happy to see...
Whats to stop us from downloading the 1.1gb Office 2016 15.13.1 install from portal.office.com and simply adding the placement of the com.microsoft.office.licensingV2.plist file? I just installed this package over the top after deleting the Office apps manually and with the licensing file in place and it came right up as expected.
I also used the method Rich describes here, but with the installer downloaded from the 365 portal and removing the update packages (removing them from the postinstall of course) and that seems to work as well.
The funny part is that I opened a case on Friday with premier support and got a reply on Monday that he will download the VL pkg and confirm what I saw and I never got a call back. And I asked him why shouldn't I just deploy 1.1GB every month instead of 3.x. No response either. Any test I did so far confirmed that deploying the 1.xGB o365 package with the plist works just fine. And instead of getting the update from the MS CDN via MAU the users get the update from a LAN based CasperShare.
It's good that Macs are still just a hobby in our organization (we only have 5 real users on OS X), but the Windows side doesn't look much better.
I did some testing, and if you have a volume license you can download only the updates and deploy those + the following three files and the fonts:
The installation scripts are identical in both the updated.pkg and the volume license installer. I opened them in pacifist and compared. You don't even need office installed to run the updaters! Just package up your updaters with the stuff listed above and deploy. Super easy.
It looks like Microsoft is not posting the new updates quickly enough on their new website. Latest Office release is 15.17.
I was able to grab the packages using the Ms AutoUpdate app by 'checking for new updates' and the download them.
Before installing the updates (when asks for admin password) all the pkg files can be found in /private/var/folders/ld/334qq26x4zj26nn_24885cqr0000gn/T/MSau_4850
Once the updates are applied the packages get deleted. The location varies from computer to computer after this /private/var/folders/
It can be /private/var/folders/hd/.... or somthing else/MSau_number number.
I hope this helps.
@maurie I am not sure where at on Microsoft's website you were looking but I had all of the 15.17 installers downloaded from Microsoft's website on day one. While in Microsoft AutoUpdate you can click on one of the updates in the list it will display a description of the update including a link to a KB article with more info. In the case of the 15.17 update the link was https://support.microsoft.com/en-us/kb/3119518. In that KB article you will see a list of links to download the updates for each individual application.
@psd_martinb Yes, I created one today. We don't use Casper at my place of work, I used to work at a school district and used it there... so, I guess I have to improvise... I make due with what I have. I will try and copy it over from our mac server and post it when I get a moment. Hopefully you know at least a bit of code so that you can tailor it to work in your environment.