How to disable MSOCACHE / Remove MSOCACHE post installation

[Reju Nair]

Hi All,

I am currently working at a customer location working on an engagement for
migration from Office 2000 to Office 2007. The deployment technology used by
the customer is Marimba and the way Marimba works, it creates separate
channels for each software to be deployed, when a channel is subscribed by
the client, the entire source folder for that software is copied to the
desktop. This source folder is maintained on the desktop till it is
subscribed to the channel. Any changes to the folder would result in
re-applying the software to the desktop.

As I understand with Office 2007, we also maintain a cache of the source
file in the MSOCACHE folder, this results into duplication and additional
consumption of disk space across the entire desktop estate.

Please let me know if there is a way around to remove the MSOCACHE folder or
disabling caching during installation.

Regards,
Reju Nair

 

[Eric A.]

The MSOcache cannot be disabled for Office 2007. Furthermore the MSOcache
should not removed after 2007 is installed. The MSOcache is required for
future patches/repairs etc.

If you do remove the MSOcache folder you will be in an unsupported state.

 

[Reju Nair]

Hi All,

Another question coming out of the current user scenario at one of the
customer locations is, if we create a cache of the Installation Source on one
Desktop using the <LIS CACHEACTION="CacheOnly" option in the config.xml and
copy the MSOCACHE folder to other desktops and run the install from the
setup.exe from the copied MSOCACHE Folder, will that work?

I have faced problems where running the setup.exe from desktop where the
MSOCACHE originated from ran as expected, but copying the same folder content
to another desktop and running the setup throws up unexpected error.

Regards,
Reju

 

[Eric A.]

Well it should be mentioned that you shouldn't run setup directly from the
msocache. What you probably want to do is share out a directory with a copy
of the source and run setup from there on the machines. The bandwith used in
that process will be comparible to copying the source to each machine anyway.

It is not recommended to manually copy the msocache to each machine. Let the
install create the msocache.