Office 2003 setup via GPO acts differently command line setup

Have English Enterprize edition of Office Professional 2003, Volume License

I deployed office 2003 per instruction of Step to Step deploy office 2003
and SP1 together. Also read Strategies for Updating Office 2003
Installations.
This is a compressed install. So following the instructions I copied cd to
share. Created a folder called Patches under the files folder. Downloaded
office2003sp1-client-enu.exe. Extracted msp file to patches which also
installs OHotfix.exe, ini and dll. Editted the setup.ini file, added
ChainedInstall_1 using the relative path to Ohotfix.exe and yes specified the
tasktype=EXE. Did the same for two other hotfixs for Office 2003. Set the
values in ohotfix.ini to display compared to quiet.

Used ORK tools for 2003 to create mst

Now...logon to workstation with admin permissions, from run command
\\server\share\setup.exe TRANSFORMS=\\server\share\2003.mst /qb-



Using this method office installs with sp1 and two other hotfixes. However
WebComponets dont install, OWC11.msi, yes it is in the setup.ini with a
relative path. Also get a display for each hotfix...sp1..etc

Edit ohotfix.ini and suppress messages with the q and sp1 and hotfixes dont
install.

2. Assign computer via GPO for office 2003 with MST modification. restart
computer. Managed software Office 2003 installing. 6 minutes and 770MB
later, prompted with logon screen, logon launch Word, no sp1 or hotfixes
installed.

Remember is using a compressed install and NOT an administrative install.

So...

1. In running from Run command, why doesnt OWC11.MSI install or via GPO?
2. Why running from run command with ohotfix.ini with certain values changed
to quiet does Office not install SP1 or other hotfixes ?
3. Why from Assigning application to computers via a GPO does sp1 nor the
hotfixes install ?

I havent tried an administrative install(why should I, this is suppose to be
better) i and never had a problem with Office XP administrative install since
thats all there is.

Are there some limitations using a compressed install and assigned via a GPO
? Any insite would be helpfull.

Thanks.

"Bob Dorn" wrote

snip...

1. In running from Run command, why doesnt OWC11.MSI install or via GPO?
2. Why running from run command with ohotfix.ini with certain values
changed
to quiet does Office not install SP1 or other hotfixes ?
3. Why from Assigning application to computers via a GPO does sp1 nor the
hotfixes install ?


snip...

Are there some limitations using a compressed install and assigned via a
GPO
? Any insite would be helpfull.


For #1 above, OWC11.MSI wasn't mentioned in your chained install section of
setup.ini, so when run from command line, it doesn't install. #2 is
similar - IF you are following the "step by step" you mentioned precisely,
then the chained install section is what takes care of whether the command
is a silent install.

#3 & final question revolve around "what is different about GPO install?" as
to whether SP1 gets installed? Specifically, GPO uses the MSI & MST, and
DOES NOT use SETUP.EXE or SETUP.INI. Since it doesn't use setup, it does
not know that you have added SP1 to the setup.ini install file, so... SP1
doesn't get installed. This is detailed on Office Online at:

http://office.microsoft.com/en-us/as...402011033.aspx

Glenn Fincher