MS says you should deploy Office2003 by running setup (not running msi directly), to make use of the cache feature.

However, if you use AD to deploy Office2003, then it does not cache the source.

Does anyone know of a way to deploy Office 2003 by AD, and also to have caching done?

The only way i can think of is to create a MSI wrapper to execute the setup executable. Is there any other way?


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


When you create the admin point, I think you can modify the setup.ini file there and change the cache options.
Answered 11/18/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
Here's the downside to compressed source setup vs. administrative installation point installs with Office 2003.

If you create an administrative installation point, you CANNOT have your install create a LIS.

If you use a compressed source installation, you can use LIS, but will not be able to patch your installation to the latest and greatest updates.

If you wish to deploy Office 2K3 through GPO and use LIS, you should be able to with a tool from the Office 2003 Resource Kit. You should be able to do it like this:

1. Copy the entire Office 2003 CD to your installation point.
2. Download & install the office 2003 resource kit
3. Run the Custom Installation Wizard to create a custom transform. In step 8 of 24, you will be able to specifiy LIS options.
4.Set GPO to install the PRO11.msi with the custom mst applied. It should cache it for you

This works on Office 2003 Professional Enterprise edition. Your mileage may vary... I'm not sure if a VLA/VLK is required for all this to work...

Something to add that I thought of after posting this.... You may be able to launch an application during the install (there is an option for this in the Custom Installation Wizard) that could manually install the LIS. You may also be able to look into the LIS tool to see what changes are made to your target system when you manipulate the cache. With the data you collect from there you may be able to make a custom MSI to perform the LIS as Office setup would.
Answered 11/18/2005 by: CoreyClamp
Yellow Belt

Please log in to comment
Hiya CoreyClamp

Thanks for the info.
I actually tried this before, and didn't cache it.
I tried several test, such as self-repair, and trying to add additonal programs, such as outlook. (I removed outlook as default installation). Also, im using STD11.MSI. Dont think that should make much difference. Can you confirm that the steps you mentioned has worked for you?


Answered 11/20/2005 by: kory
Senior Yellow Belt

Please log in to comment