Office 2003 Administrative Install

[Frank Muk]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a rundown on
the CACHE settings of the setup.ini in case anybody else runs into
problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

 

[Frank Muk]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a rundown on
the CACHE settings of the setup.ini in case anybody else runs into
problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

 

[Frank Muk]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a rundown on
the CACHE settings of the setup.ini in case anybody else runs into
problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

 

[GMAN Slater]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a
rundown on the CACHE settings of the setup.ini in case anybody else
runs into problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

Well in my post I mention that to you BUT it should not work for installs ran from admin install points. On the that same page:

"Note These settings are applied only when Office is installed from the CD or an image of the compressed CD on the network. Administrative installation points do not support creation of a local installation source during Setup. When you run Setup with the /a option, Setup extracts the compressed CAB files on the network share. Setup does not run Office Source Engine (Ose.exe) to copy source files to users' computers; instead, Windows Installer uses the original source."

Are you saying that just by using the ENFORCECACHE=1 in the SETUP.INI file you got a LIS created. I had this in my SETUP.INI file ever since I switched to the new SETUP.EXE file. Which is what adds this new property BTW so you had to be using this new one too.

The only thing that worked for me (and the only thing MS says will work) is installing from a compressed CD image (i.e. copy the CD to a share as-is) NOT from an admin install point (i.e. setup /a). Sounds like you are using the compressed CD files, with the latest SETUP.EXE, and using ENFORCECACHE=1 in SETUP.INI file. This is the standard way of doing it.

On another note: For yet another discrepancy in the documentation, observe DELETEABLECACHE as listed here:
http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

and DELETABLECACHE as listed here:
http://www.microsoft.com/resources/documentation/office/2003/all/reskit/en-us/refa03.mspx

 

[GMAN Slater]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a
rundown on the CACHE settings of the setup.ini in case anybody else
runs into problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

Well in my post I mention that to you BUT it should not work for installs ran from admin install points. On the that same page:

"Note These settings are applied only when Office is installed from the CD or an image of the compressed CD on the network. Administrative installation points do not support creation of a local installation source during Setup. When you run Setup with the /a option, Setup extracts the compressed CAB files on the network share. Setup does not run Office Source Engine (Ose.exe) to copy source files to users' computers; instead, Windows Installer uses the original source."

Are you saying that just by using the ENFORCECACHE=1 in the SETUP.INI file you got a LIS created. I had this in my SETUP.INI file ever since I switched to the new SETUP.EXE file. Which is what adds this new property BTW so you had to be using this new one too.

The only thing that worked for me (and the only thing MS says will work) is installing from a compressed CD image (i.e. copy the CD to a share as-is) NOT from an admin install point (i.e. setup /a). Sounds like you are using the compressed CD files, with the latest SETUP.EXE, and using ENFORCECACHE=1 in SETUP.INI file. This is the standard way of doing it.

On another note: For yet another discrepancy in the documentation, observe DELETEABLECACHE as listed here:
http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

and DELETABLECACHE as listed here:
http://www.microsoft.com/resources/documentation/office/2003/all/reskit/en-us/refa03.mspx

 

[GMAN Slater]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a
rundown on the CACHE settings of the setup.ini in case anybody else
runs into problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

Well in my post I mention that to you BUT it should not work for installs ran from admin install points. On the that same page:

"Note These settings are applied only when Office is installed from the CD or an image of the compressed CD on the network. Administrative installation points do not support creation of a local installation source during Setup. When you run Setup with the /a option, Setup extracts the compressed CAB files on the network share. Setup does not run Office Source Engine (Ose.exe) to copy source files to users' computers; instead, Windows Installer uses the original source."

Are you saying that just by using the ENFORCECACHE=1 in the SETUP.INI file you got a LIS created. I had this in my SETUP.INI file ever since I switched to the new SETUP.EXE file. Which is what adds this new property BTW so you had to be using this new one too.

The only thing that worked for me (and the only thing MS says will work) is installing from a compressed CD image (i.e. copy the CD to a share as-is) NOT from an admin install point (i.e. setup /a). Sounds like you are using the compressed CD files, with the latest SETUP.EXE, and using ENFORCECACHE=1 in SETUP.INI file. This is the standard way of doing it.

On another note: For yet another discrepancy in the documentation, observe DELETEABLECACHE as listed here:
http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

and DELETABLECACHE as listed here:
http://www.microsoft.com/resources/documentation/office/2003/all/reskit/en-us/refa03.mspx

 

[GMAN Slater]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a
rundown on the CACHE settings of the setup.ini in case anybody else
runs into problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

Well in my post I mention that to you BUT it should not work for installs ran from admin install points. On the that same page:

"Note These settings are applied only when Office is installed from the CD or an image of the compressed CD on the network. Administrative installation points do not support creation of a local installation source during Setup. When you run Setup with the /a option, Setup extracts the compressed CAB files on the network share. Setup does not run Office Source Engine (Ose.exe) to copy source files to users' computers; instead, Windows Installer uses the original source."

Are you saying that just by using the ENFORCECACHE=1 in the SETUP.INI file you got a LIS created. I had this in my SETUP.INI file ever since I switched to the new SETUP.EXE file. Which is what adds this new property BTW so you had to be using this new one too.

The only thing that worked for me (and the only thing MS says will work) is installing from a compressed CD image (i.e. copy the CD to a share as-is) NOT from an admin install point (i.e. setup /a). Sounds like you are using the compressed CD files, with the latest SETUP.EXE, and using ENFORCECACHE=1 in SETUP.INI file. This is the standard way of doing it.

On another note: For yet another discrepancy in the documentation, observe DELETEABLECACHE as listed here:
http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

and DELETABLECACHE as listed here:
http://www.microsoft.com/resources/documentation/office/2003/all/reskit/en-us/refa03.mspx

 

[GMAN Slater]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a
rundown on the CACHE settings of the setup.ini in case anybody else
runs into problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

Well in my post I mention that to you BUT it should not work for installs ran from admin install points. On the that same page:

"Note These settings are applied only when Office is installed from the CD or an image of the compressed CD on the network. Administrative installation points do not support creation of a local installation source during Setup. When you run Setup with the /a option, Setup extracts the compressed CAB files on the network share. Setup does not run Office Source Engine (Ose.exe) to copy source files to users' computers; instead, Windows Installer uses the original source."

Are you saying that just by using the ENFORCECACHE=1 in the SETUP.INI file you got a LIS created. I had this in my SETUP.INI file ever since I switched to the new SETUP.EXE file. Which is what adds this new property BTW so you had to be using this new one too.

The only thing that worked for me (and the only thing MS says will work) is installing from a compressed CD image (i.e. copy the CD to a share as-is) NOT from an admin install point (i.e. setup /a). Sounds like you are using the compressed CD files, with the latest SETUP.EXE, and using ENFORCECACHE=1 in SETUP.INI file. This is the standard way of doing it.

On another note: For yet another discrepancy in the documentation, observe DELETEABLECACHE as listed here:
http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

and DELETABLECACHE as listed here:
http://www.microsoft.com/resources/documentation/office/2003/all/reskit/en-us/refa03.mspx

 

[GMAN Slater]

The trick was setting ENFORCECACHE=1 in the setup.ini. Here's a
rundown on the CACHE settings of the setup.ini in case anybody else
runs into problems.

http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

Cheers!

Well in my post I mention that to you BUT it should not work for installs ran from admin install points. On the that same page:

"Note These settings are applied only when Office is installed from the CD or an image of the compressed CD on the network. Administrative installation points do not support creation of a local installation source during Setup. When you run Setup with the /a option, Setup extracts the compressed CAB files on the network share. Setup does not run Office Source Engine (Ose.exe) to copy source files to users' computers; instead, Windows Installer uses the original source."

Are you saying that just by using the ENFORCECACHE=1 in the SETUP.INI file you got a LIS created. I had this in my SETUP.INI file ever since I switched to the new SETUP.EXE file. Which is what adds this new property BTW so you had to be using this new one too.

The only thing that worked for me (and the only thing MS says will work) is installing from a compressed CD image (i.e. copy the CD to a share as-is) NOT from an admin install point (i.e. setup /a). Sounds like you are using the compressed CD files, with the latest SETUP.EXE, and using ENFORCECACHE=1 in SETUP.INI file. This is the standard way of doing it.

On another note: For yet another discrepancy in the documentation, observe DELETEABLECACHE as listed here:
http://www.microsoft.com/office/ork/2003/ref/RefA03.htm#sub_9

and DELETABLECACHE as listed here:
http://www.microsoft.com/resources/documentation/office/2003/all/reskit/en-us/refa03.mspx