The only way to do it would be to build a package that actually deploys the 14.1.pkg into a location like /private/tmp/ and then uses a postinstall script to do something like: installer -pkg /private/tmp/Office201_114.1.pkg -target / -allowUntrustedĮdit: Lol, and I posted nearly identical responses. Just so I try to answer one of your questions above though, the Casper Suite's installation process doesn't use the -allowUntrusted flag when using the built in function, and there is no way I know of to make it use that flag. In that case, you'll have no choices other than deploying 14.1, and then the current updates, or just re-installing Office cleanly on their Mac.
Office for mac 2011 updates update#
The only reason you would need to use this 14.1 package is if you already have clients out there with versions like 14.0.2 or something horribly old and you are trying to update them to 14.1 first. So before anything else, I'd really look into getting a more current installer version. I forget now if this has to do with Apple revoking some older developer certificates a while back due to some security issues, or if its just because its expired. Assuming you mean you are deploying it as a full installation and not an update to an existing install.Īs you've found, the certificate that was being used for that installer is now no longer valid.
You really shouldn't be trying to deploy/install Office 14.1 at this point as that is a very old version.
So first off, if you have a volume license of Office 2011 with Microsoft, you should be able to obtain a full installer package that is much more current, like 14.3.9 or something like that.