2003 Deployment

S

Schlafly

I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
Click to expand...
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
Click to expand...
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
Click to expand...
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
Click to expand...
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
Click to expand...
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
Click to expand...
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
Click to expand...
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
Click to expand...
 
G

Gerry Hickman

Hi

Have you actually read the deplyment guide? Your question seems confused to
me. The MST is just a settings transform.

If you mean you want to "slipstream" service packs and patches into a single
Administrative Installatoin Point, and then deploy the fully patched Office
from there, then I think you are going about it the wrong way, especially
your ChainedInstall_1 section..

In the above scenario, you first create, SP and patch the AIP, then give it
an MST to play with when it's time to roll it out to the clients.


--
Gerry Hickman
SSRU SysAdmin

Schlafly said:
I am currently trying to Deploy Office 2003 with SP1. I was not succesful in
trying to combind the install throught the .MST file so I am trying through
the setup.ini file. Now when I run the setup through the .ini I get "The
language of this installation package is not supported by your system." I
have no ideal why this is coming up. Any help would be Greatly appreciated.

This is a copy of my setup.ini:

; 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={HV9G6-Y6BJP-98PHP-D3K7J-K44DY}
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_name\public\Microsoft Corporation\Office 2003\2003Pro.mst"
;MST1=D:\transforms\my transform.mst

[Options]
; The option section is used for specifying individual Installer Properties.
;USERNAME=
;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 2003 Setup(*).txt
Type=piwaeo
Path=c:\temp\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

[ChainedInstall_1]
TASKTYPE=exe
PATH="\\Server_name\public\Microsoft Corporation\Office
2003\FILES\PATCHES\ohotfix.exe"
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

Chained Installation 9
Can't reinstall Office Pro 2003 2
Help! Using an MST file to modify installation with group policy 2
Word/Excel 2003 viewers installation 1
Error 1719 when trying to add Office Pro 2003 components.(bit long) 0
Office 2003 Admin Installation Point 0
Office 2003 Setup failure 9
group policy deployment of Office2003 SP3 fails 0

Top