Hi Scrappo,
You mentioned that you have also tried it without ZenWorks. In that scenario what is the command line you're using and even with
ZenWorks are you using just the msi or running the Office Setup program?
What happens (errors, etc) on the machines where it fails and at what point?
(If Office 2003 'appears' to be installed on a PC then rerunning with an MST file would generally fail the 'first time install' test
that is made).
Anything common or unique on the machines where it's failing? (Domain, server, controller, Windows version, etc)?
You're chaining the SP2 update to the clients rather than updating the admin point with it and then deploying or recaching as your
preferred approach then?
==========
Thanks for getting back to me Bob
ok
Yes i created a MST file and configured the setup.ini. All are on a Network
drive called H:\ of which i have given the users all sorts of rights (in
order to try anything to get this to work)
The deployment is being sent out via Zenworks using the admin package path as:
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)
The SETUP.INI path is
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\Files\SETUP\SETUP>INI
Transform (MST) Path
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.MST
I also applied the SP2 (i have tried with and without this) which is placed
in:
H:\MSO2003\SP2 MSP file\MAINSP2ff.msp
The setup.ini file is shown here
; 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=H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.mst
[Options]
; The option section is used for specifying individual Installer Properties.
USERNAME=Browne Construction
COMPANYNAME=J Browne Construction Company Limited
;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=\\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
The problem is that this works on all but a 1/3 of the pc's/laptops we have.
Anything else you need?
Thanks
Scrappo>>
