M
matty
Well as it turns out, setting ENFORCECACHE=2 only gets rid of the error
messages about incorrect syntax. It does not seem to install the local
cache. We think this may have something to do with our corporate copy of
Office. Well back to the drawing board....
messages about incorrect syntax. It does not seem to install the local
cache. We think this may have something to do with our corporate copy of
Office. Well back to the drawing board....
matty said:Thanks Bob. However those two documents seem to only deal with modifying the
setup.ini file. For what we're trying to do we'd like to set the
ENFORCECACHE option from the command line. According to HA011402451033.aspx,
"...ENFORCECACHE must be set in the [CACHE] section of the Setup.ini file or
on the command line." However I was unable to find where the switches were
referrenced in the document. We've tried several permutations of
ENFORCECACHE (ENFORCECACHE, /ENFORCECACHE, /ENFORCECACHE=1, ENFORCECACHE=1)
with no luck. Also it seems that the enhanced setup package for Office fails
to include an updated .ini file with the installer.
!! After some experimentation we were able to get the enhanced setup to
install. It seems that since the enhanced setup package does not modify the
setuppro.ini which resides in ~\SETUP\FILES\setuppro.ini. This needs to be
renamed to setup.ini. As for ENFORCECACHE needs to be set to ENFORCECACHE=2.
Why this is, I have no idea as:
http://office.microsoft.com/en-us/assistance/HA011513671033.aspx
specifically references 0 or 1 as valid
values. I'm *so* glad this little caveat was included in the enhanced setup
documentation. Thanks MS!
Bob Buckland ?:-) said:Hi Matty,
It's related to the Office System 2003
'Local Install Source' (LIS) cache.
See if the information here helps:
http://office.microsoft.com/en-us/assistance/HA011402451033.aspx
http://office.microsoft.com/en-us/assistance/HA011513671033.aspx
=====
When installing O2K3 from the command line using the new setup.exe, what is
the switch to use the ENFORCECACHE option? >>