Chained install not working

B

Bill Bradley

I normally do a chained install of Office 2003 Pro Suite + Front Page + One
Note + SP3, and, it works fine.

I'm going to be installing onto computers that already have the Suite
installed, so, just need to install Front Page, OneNote, and SP3 for those
two components.

I tried modifying my setup.ini to install FP, then ONote, then SP3, but, the
chain stops after FP. I even tried the SetupFP.ini file, and set it up to do
the same, but, it stopped, too.

How do I install just these two products and SP3 for them in one batch?

Thanks!
 
K

Keith V. Klenke

Why dont you simplify it a bit & slipstream SP3 into
office/frontpage/onenote?
 
B

Bill Bradley

I wasn't aware that you COULD slipstream Office products (I do slipstream
other products)...<G>

But, even so, I would still need to chain at least FP and OneNote together.

Do the individual components simply not chain, if you don't begin with the
Suite?

I am chaining Visio and Project with SP3 (each component separately, but,
haven't tried chaining them together).

Here's my INI file that I'm trying to use. I started with the OfficePro ini
file, but, it didn't work, so, switched to the FP ini file:

; Microsoft Office SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must
be in
; the same folder as Setup.exe, and both must be in the root of the
installation
; tree.
MSI=FP11.MSI

[Product]
ProductCode={90170409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office FrontPage 2003
ProductVersion=11.0.5614.0
Recache=1

[MST]
; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
;MST1=D:\transforms\my transform.mst
MST1=echfp11.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company
;INSTALLLOCATION=C:\Program Files\MyApp

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
;Display=None
;CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name
unique
Template=Microsoft Office FrontPage 2003 Setup(*).txt
Type=piwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=500
WindowsBuild_1=2195
ServicePackLevel_1=3

[Cache]
; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE <predefined> Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end
of
; setup [0,1]
CDCACHE=auto
;LOCALCACHEDRIVE=C:\
DELETABLECACHE=0
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI

[ChainedInstall_1]
TaskType=msi
Path=ONOTE11.MSI
;Display=None
MST=ECHONOTE11.MST
;Cmdline=property=value

[ChainedInstall_2]
TaskName=SP3 Install
TaskType=EXE
Path=.\files\patches\ohotfix.exe
;Display=None
;MST=
;Cmdline=property=value
 
B

Bill Bradley

This is what I keep getting in the log file:

Successfully launched MsiExec....
10/30/2007 6:57:20 AM Chained install return code: 0


Looking for setup tasks to process.
Shutting down chained setup processing.


***** Setup exits
10/30/2007 6:57:20 AM
(return = 0)


Bill Bradley said:
I wasn't aware that you COULD slipstream Office products (I do slipstream
other products)...<G>

But, even so, I would still need to chain at least FP and OneNote together.

Do the individual components simply not chain, if you don't begin with the
Suite?

I am chaining Visio and Project with SP3 (each component separately, but,
haven't tried chaining them together).

Here's my INI file that I'm trying to use. I started with the OfficePro ini
file, but, it didn't work, so, switched to the FP ini file:

; Microsoft Office SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must
be in
; the same folder as Setup.exe, and both must be in the root of the
installation
; tree.
MSI=FP11.MSI

[Product]
ProductCode={90170409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office FrontPage 2003
ProductVersion=11.0.5614.0
Recache=1

[MST]
; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
;MST1=D:\transforms\my transform.mst
MST1=echfp11.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company
;INSTALLLOCATION=C:\Program Files\MyApp

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
;Display=None
;CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name
unique
Template=Microsoft Office FrontPage 2003 Setup(*).txt
Type=piwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=500
WindowsBuild_1=2195
ServicePackLevel_1=3

[Cache]
; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE <predefined> Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end
of
; setup [0,1]
CDCACHE=auto
;LOCALCACHEDRIVE=C:\
DELETABLECACHE=0
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI

[ChainedInstall_1]
TaskType=msi
Path=ONOTE11.MSI
;Display=None
MST=ECHONOTE11.MST
;Cmdline=property=value

[ChainedInstall_2]
TaskName=SP3 Install
TaskType=EXE
Path=.\files\patches\ohotfix.exe
;Display=None
;MST=
;Cmdline=property=value


Keith V. Klenke said:
Why dont you simplify it a bit & slipstream SP3 into
office/frontpage/onenote?
Click to expand...
Click to expand...
 
B

Bill Bradley

I setup a two-line batch and install just FP in the first line and ON with a
chained install to SP3 in the second line, and...THIS WORKS.

Soooo...why can't I chain FP + ON + SP3 all together in one INI?

Bill Bradley said:
This is what I keep getting in the log file:

Successfully launched MsiExec....
10/30/2007 6:57:20 AM Chained install return code: 0


Looking for setup tasks to process.
Shutting down chained setup processing.


***** Setup exits
10/30/2007 6:57:20 AM
(return = 0)


Bill Bradley said:
I wasn't aware that you COULD slipstream Office products (I do slipstream
other products)...<G>

But, even so, I would still need to chain at least FP and OneNote together.

Do the individual components simply not chain, if you don't begin with the
Suite?

I am chaining Visio and Project with SP3 (each component separately, but,
haven't tried chaining them together).

Here's my INI file that I'm trying to use. I started with the OfficePro ini
file, but, it didn't work, so, switched to the FP ini file:

; Microsoft Office SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must
be in
; the same folder as Setup.exe, and both must be in the root of the
installation
; tree.
MSI=FP11.MSI

[Product]
ProductCode={90170409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office FrontPage 2003
ProductVersion=11.0.5614.0
Recache=1

[MST]
; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
;MST1=D:\transforms\my transform.mst
MST1=echfp11.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company
;INSTALLLOCATION=C:\Program Files\MyApp

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
;Display=None
;CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name
unique
Template=Microsoft Office FrontPage 2003 Setup(*).txt
Type=piwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=500
WindowsBuild_1=2195
ServicePackLevel_1=3

[Cache]
; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE <predefined> Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end
of
; setup [0,1]
CDCACHE=auto
;LOCALCACHEDRIVE=C:\
DELETABLECACHE=0
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI

[ChainedInstall_1]
TaskType=msi
Path=ONOTE11.MSI
;Display=None
MST=ECHONOTE11.MST
;Cmdline=property=value

[ChainedInstall_2]
TaskName=SP3 Install
TaskType=EXE
Path=.\files\patches\ohotfix.exe
;Display=None
;MST=
;Cmdline=property=value


Keith V. Klenke said:
Why dont you simplify it a bit & slipstream SP3 into
office/frontpage/onenote?

--
http://abeNd.org - Novell News for IT Professionals
-
I normally do a chained install of Office 2003 Pro Suite + Front Page + One
Note + SP3, and, it works fine.

I'm going to be installing onto computers that already have the Suite
installed, so, just need to install Front Page, OneNote, and SP3 for those
two components.

I tried modifying my setup.ini to install FP, then ONote, then SP3, but,
the
chain stops after FP. I even tried the SetupFP.ini file, and set it up to
do
the same, but, it stopped, too.

How do I install just these two products and SP3 for them in one batch?

Thanks!
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Get rid of the "Cancel" button during Office chained installs 0
Error 1719 when trying to add Office Pro 2003 components.(bit long) 0
Going Bald Already Please help before I loose more hair 7
Making OHotFix.exe more silent 0
Office 2003 SP3 silent install issue 0
Another setup failure Chained install return code: 1603 0
Office 2007 Ultimate will not install on Windows 7 Ultimate 10
Office 2k3 Updates will not install 1

Top