- This topic has 4 replies, 5 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
Anyone try to install Office 2008 and then install the security update that just came out? The security update runs but doesn’t actually install anything as far as I can tell. I emailed on a Mac Business Unit email list about it hoping someone from MS would see. Figured I’d post here too.
I don’t have an answer, but it’s clear there’s some craziness in their packages that basically copy stuff to a tmp place and then install. You probably won’t be able to deploy this using instadmg as is.It’ll probably need to be repackaged or go into a “install this on first boot” type of process.
I’ve spun home brew packages for Office 2008, the first test (really small) update, and the significant 12.0.1 update.
I have had little difficulty installing and then working with the applications after the install.
My packaging method involves logGen for system snapshots, pkgGen for collecting the files, then PackageMaker for building the PKG installer.
I am building on Tiger now. I have not explicitly tested by Office 2008 pkgs on Leopard.
I use an MPKG to install the base application suite, update 1, then the 12.0.1 update.
Not sure about what Josh mentions. I do know the first update replaces the Auto Update utility, found in /Library/Application Support/Microsoft. (They call it MAU 2.0 now.)
Does this information help?
I am having the same problem with the Auto Update 2.1.1. Word installs fine, but the updates do not seem to work. I tried installing Word 2008 and Office update 12.0.1 and it doesn’t look like it was applied. Now I can’t even run the MAU to run the Auto Update 2.1.1. I tried to repackage Auto Update 2.1.1 with Packagemaker, but it doesn’t do anything. I want to run them in the InstaDMG script, but for now will run them after the first boot.
- You must be logged in to reply to this topic.