On Nov 4, 2005, at 5:10 PM, Kathy Gach wrote: I'm using an application called Iceberg to make packages. I'm trying to make a package of the Microsoft Office Update 11.2.0 So I can remotely distribute it to my users. I am able to make the package And send it remotely, but the package seems to just copy the updater in the users hard drive. Once the package is successfully sent, I have to manually launch the installer.
Is there a way I can send it remotely and have it automatically install by itself?
The Updater is really only updating 2 files and creating a log file. I -think- you might have been trying to just insert their VISE package in to your package. If I am right then instead what you want to do is look at "logGen"
You would use logGen to see what the installer is updating and then use that to know what to put in your package. For the Office updates you don't have to do that step, but I do it for most things. Why don't you have to do it? Well there's a log that gets put in the office folder...
Friday, October 21, 2005 10:47 AM Beginning installation. Office 2004 11.2.1 Update Type of Install: Easy Install Installed Macintosh HD:Applications:Microsoft Office 2004:Microsoft Entourage Installed Macintosh HD:Applications:Microsoft Office 2004:Office:Microsoft Component Plugin Friday, October 21, 2005 10:47 AM The installation is complete.
From the above you know the 2 files that you need to insert in your package, and make sure that your machines all have Office in the same place. You could do some kind of test in a preflight script, but where I am we know Office is in the right place.. or someone gets what they deserve if they moved it... so I don't really test.
I do hope this helps you some.
-Josh |