Issue with Office for Mac 2011 14.3.9 Update

I flattened my file using the above documented procedure. Still getting failures, BUT some successes. The further it goes, the higher the rate of successes. I wonder if this is because the http delivery had partially downloaded files that resumed and failed? The latest ones are getting my flattened file and succeeding.
Just a thought…

I just wanted to add something that i forgot to mention that may explain why i've had success on every update. I'm on JSS v9, i install from cache at Logout and SS. But with SS, i run an AppleScript that requires the user to quit all MS apps before running. Just wanted to add that last bit since i left it out on my previous comment. Seems like that might be important to it's success.

Hi Guys;

used def flounder method mentioned by bmwarren above. 100% success using:

1. Casper remote: 9 machines, 3 users logged in, 3 no one logged in, 3 being installed with another package
2. ARD we are using Casper Suite ver 8.62,

This bit us today.

Flatterning the pkg didn't seem to help.

Is that definitely the fix?

8.73 btw..

@bentoms][/url - Something tells me "flatterny" will get you nowhere with this :-D

Kidding aside, I haven't tested expanding then re-flattening the package, so I can't say if that's the definitive fix myself. But I suspect wrapping the original installer up in a new package as its payload, say to "Waiting Room" should work to bypass the issue if re-flattening is bringing you no joy.

@bentoms][/url][/url,

I've been expanding, editing the Office2011_all_quit_14.3.x.combo.pkg/Scripts/preinstall script, then flattening again. That has prevented issues for me.

The process I'm using is described here:

http://derflounder.wordpress.com/2012/09/26/removing-the-office-2011-installers-application-quit-function/

@mm2270 ha ha. But that waiting room idea might work.

@rtrouton, the issue is with deploying over HTTPS to cached.. So not getting as far as the quit apps bit yet (but not needed as we install @ logout).

Will try again tomorrow. Other PKG's are fine.

So far, once I expanded and flattened the package it has deployed ok. I cannot say this is a sure fix. It just happens that here it seems to have worked. But I don't have that many systems. Although, before, it would not work at all.

The 14.3.9 update may itself have issues. On a 10.6.8 box with all apple-updates, but without jamf, I did fresh install of office2011 (never had any office on it at all before this). Let Microsoft-Update do all updates up to 14.3.8 but not 14.3.9. For 14.3.9 downloaded the dmg and ran update. After that, Word hung on launch, and on launch excel through a fatal error message about a missing file. Ran 14.3.9 from the dmg a 2nd time, and now word and excel run ok again. Go figure.

No Issues here with deploying from an AFP distribution point. I Uploaded the "Office 2011 14.3.9.pkg" into Casper Admin and deployed..
JSS 8.73

I'm pretty sure this is an http deployment issue.

@aamjohns, agreed & with this pkg for some reason. (Others are fine).

We had the same problem on Casper 8.7.1, with a caching policy using https. Repackaging the MS Office package as described with bmwarrens two commands described above resolve the issue for us (using https).

Very interesting and I need to try this out. I've been uninstalling office and re deploying it for workstations out of hours and self service for laptops.

FWIW: JSS @ 8.7.3. DPs via SMB. Flattened pkg via Rich's process. 0 issues so far. This may be the one (and likely only time) I am glad we have not migrated to http yet. :)

Ran into this issue as well (JSS 8.62). Added the 14.3.9 pkg file to Casper Admin at the same that I added some Xerox print driver .pkg files. The Xerox packages cached and then installed correctly, but the Office 14.3.9 update package failed to cache with the "The package could not be found on the server" error. Changing the policy to force AFP instead of http fixed it.

I'd like to add to this, I still get these error frequently with Office 2011 updaters past 14.4.x.
I think 14.3.x and earlier didn't have any issues, and currently its on 14.4.8.

I gave up on this for a while because I haven't yet found this thready (oddly), but just revisited it today.
At least with the latest 14.4.8 I have noticed that the error seems to only happen with 10.6 clients.
With 10.8, 10.9, and 10.10 clients, a policy-executed pkg update appears to work correctly.

Haven't seen this a long time. Have you tried to change permissions on the Updater pkg, and ensure its name has no spaces before uploading via Casper Admin?