Chained Installation

R

rbcc

My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
Click to expand...
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
Click to expand...
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
Click to expand...
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
Click to expand...
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
Click to expand...
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
Click to expand...
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
Click to expand...
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
Click to expand...
 
D

Dian Chapman, MVP, MOS

The word "pray" comes to mind. Although I like Milly's suggest of
www.magicbeans.com as a solution.

The reason being that what you're asking is a lot. Although you can
automation the deployment, having all the apps and fixes also applied
can be a bit tricky.

The details for all this stuff are in your Office Resource Kit. If you
don't have one, you will want check out the MIcrosoft Technet site.
I'd suggest you start with this URL.

Microsoft Solution Accelerator for Business Desktop Deployment
Office XP and Office 2003 Feature Team Guide
http://www.microsoft.com/technet/itsolutions/cits/dsd/bdd/bddxp03.mspx

By the way, posting all the dir details was unnecessary.

Good luck...

Dian D. Chapman, Technical Consultant
Microsoft MVP, MOS Certified
Editor/TechTrax Ezine

Free Tutorials: http://www.mousetrax.com/techtrax
Free Word eBook: www.mousetrax.com/books.html
Optimize your business docs: www.mousetrax.com/consulting
Learn VBA the easy way: www.mousetrax.com/techcourses.html



My installation is in these directories:
E:\Office 2003\Office--|
|-Project
|-Setup.exe
|-One
|-Setup.exe
|-Visio
|-setup.exe
|-Front
| |-Front
| |-Setup.exe
|-Hotfixes
|-Addins
|-Files
|-Setup
|-setup.ini

The setup.ini looks like this:

; 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=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 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


[Options]
; The option section is used for specifying individual
Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company




[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 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=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI
@echo on
echo Installing other MS OFFice Apps
@echo off

[ChainedInstall_1]
TaskType=exe
Path =.\office 2003\office\PROJECT
CmdLine = /qb

[ChainedInstall_2]
TaskType=exe
Path =.\office 2003\office\ONE
CmdLine = /qb

[ChainedInstall_3]
TaskType=exe
Path =.\office 2003\office\Front\Front
CmdLine = /qb

[ChainedInstall_4]
TaskType=exe
Path =.\office 2003\office\ork
CmdLine = /qb

[ChainedInstall_5]
TaskType=exe
Path =.\office 2003\office\VISIO
CmdLine = /qb

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = hotfixes.bat

[ChainedInstall_6]
TaskType=bat
Path =.\office 2003\office\SETUP
CmdLine = addins.bat

How do I chain all the installations together so when
Office gets through the installation proceedure, then One
note starts and when its done, then Front Page,ect ?

And then when all they are done the hotfixes automatically
start and then the addins?

John
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

2003 Deployment 9
[ChainedInstall_1] not working with Office 2003 0
Can't reinstall Office Pro 2003 2
Language of this installation package is not supported by your sys 0
Deploy Office 2003 and SP2 with Transform 0
Help! Using an MST file to modify installation with group policy 2
Error 1719 when trying to add Office Pro 2003 components.(bit long) 0
Going Bald Already Please help before I loose more hair 7

Top