I distribute mine from the software deployment portal and use run from network. But there are pros/cons accordingly, it works for us but we're in no hurry to force it out - yet. I found this on the Internet, maybe this will help you. 1. From the network installation point, use Notepad to open the config.xml file, which is located in the core product folder (e.g., Pro.WW for Office Professional 2007 -or Office12\Enterprise.WW\setup.xml). 2. Find the [LIS] element, and uncomment the line by deleting the opening [!-- and closing --] tags. 3. Set the [CACHEACTION] attribute to "CacheOnly". The line in Config.xml should look like [LIS CACHEACTION="CacheOnly" /] 4. Save the config.xml file. 5. Run setup.exe on users' computers, specifying the fully qualified path to the modified config.xml. For example, \\[server]\[share]\Office12\setup.exe /config \\[server]\[share]\Office12\Pro.WW\Config.xml
I would definately use the Office Resource Kit to customize the install and also you can always refer to AppDeploy for addiitonal information http://www.appdeploy.com/packages/detail.asp?id=860.
I have been able to successfully decrease the deployment size of Office 2007 from 2.5gb to about 800mb
These are the files/folders we are deploying.
For most software titles there is a .WW folder (ex Word.WW) these folders seam to hold the different language packs for that particular module. and if you are deploying it in english, they are unneeded.
I have created the Distrobution task as an exe with the following switch /config "\\PathToConfig\config.xml" /adminfile "\\PathToMSP\office2007.msp"
and it seams to work well.
We are deploying Access, Excel, Outlook, PowerPoint, Publisher and Word right now through this method. for some reason when i pulled out all the folders above that i did not think i needed (visio, project, ect) i got an error from the msp. might have something to do with how it was created.
Hope this helps someone in the future.
Are you guys aware of the -admin command line parameter for the office 2007 setup.exe? Am I stating the obvious!!?
if im not mistaken, -admin will create the msp.
Oh yes, i missed you mentioned you had created an msp file.
Well it just turned out my install disk was all sorts of crazy. I ended up redownloading office from the Microsoft website and the file size for office is down to: 827mb, including the SP1 update msp. Good Luck to all and your Journey
even with the regular-sized install, I've seen a fair number of people 7zip the whole distribution into a single file, then unzip before running (requires batch file distribution method with the .7z file defined as an additional file).
This is trading network transfer time for disk i/o and cpu beating when the install happens, depends what's more important to you.
any idea how small it is when you do that?