Office 2003 setup

[TOM]

I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Bob Buckland ?:-\)]

Hi Tom,

It's not clear what patch your adding to the Office 2003
installation (Office 2003 is at SP1 rather than SP3).
Office Service Packs would usually be in MSP rather than MSI format.

Generally, you'd create your Office Admin Point first then
apply the updates to the Admin Point so that when you install
from the Admin point with your MST the client computer would
receive the updated version at first install.

This article has additional options you can choose for applying
Office updates
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm

============
I created my .mst file with Custom Installtion Wizard (CIW), I'd like add in
step 16 (Add Installations and Run Programs) SP3 and patch for spam
filter.But I dont know how can I add MSI packages. Can you help?
At least a link to article which describe this problem.

Thanks Tom >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob

 

[Rob Moore]

Tom,

Your best bet (for a patch) is to use ohotfix.exe and call this from a
'Chained Install' section in your Setup.ini (or setuppro.ini etc) file which
is located in <source> \files\setup\

[ChainedInstall_1]
TaskType=exe
PATH=e:\files\patches\ohotfix.exe
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

for additional .MSI to be chained create a
[ChainedInstall_2]
TaskType=msi
PATH=X:\files\patches\example.msi
DISPLAY=
Reboot=0
;MST=
;CMDLINE=SOURCELIST=\\server2\share admin_install_point\1036

[ChainedInstall_n]
Install an additional package (MSI file) or other executable file (such as
an EXE file or a BAT file) as part of the Office installation. Add a
[ChainedInstall_n] section to Setup.ini for each chained installation;
replace the placeholder n with a consecutive number. Chained packages are
installed in order after the core Office package is successfully installed.

To customize the chained installation, set the following properties:

TaskName
Assign a friendly name to the installation (optional). Setup uses this name
in the Setup log file.

Path
Specify the path and file name of the MSI file or an executable file
(required).

TaskType
Identify whether the chained installation is an MSI file or EXE file
(required).

MST
Specify the path and file name of a transform to apply to the chained
package (for MSI files only). You can specify only one transform in this
entry; to specify multiple transforms, add the TRANSFORMS property to the
Cmdline entry.

Display
Specify a display setting for the chained installation; may differ from
global display level set for the core Office package. If this value is not
set, Setup uses the display level set for the core Office package.

CmdLine
Add other options to the command line that Setup passes for the chained
package. The value of CmdLine is limited to 1239 characters. Setup truncates
the command line after it reaches that limit.

Note that you cannot use CmdLine to override the installation type (/j or
/i) set for the primary package; that setting is automatically applied to all
chained packages.

Reboot
To restart the computer after a chained installation completes, set this
option to 1; Setup restarts and resumes the installation process. The default
setting is 0, which suppresses computer restarts prompted by files in use.

IgnoreReturnValue
To continue to install successive chained installations even if this
installation fails, set this property to 1.

Rgds

Rob