G
Gerry Hickman
Hi,
Your setup sounds a bit strange; running Office XP with Outlook 2003
SP1. That's a mess.
It's hard to compare running the service pack against a client box and
running it against an Outlook MSI that's part of an AIP. What did the
relevant part of your log file say (the one you created on the command
line) and what error number was returned from MSIEXEC?
I've patched Office 2003 to SP2 on a build that includes Outlook 2003
and rolled it out on a big network without any problems. The main
difference is that I'm patching PRO11.MSI (or whatever). I seem to
remember there was a separate procedure for patching the OWC11.MSI
It's a bit strange your target isn't PRO11.MSI anyway; I mean usually
you apply a TRANSFORM with the components you want (e.g. Outlook only),
but it wouldn't be able to give the MSI file a different name. It's
almost as if you created an AIP for _Outlook_ as opposed to one for
_Office_ that only contains the Outlook App and nothing else...
Your setup sounds a bit strange; running Office XP with Outlook 2003
SP1. That's a mess.
It's hard to compare running the service pack against a client box and
running it against an Outlook MSI that's part of an AIP. What did the
relevant part of your log file say (the one you created on the command
line) and what error number was returned from MSIEXEC?
I've patched Office 2003 to SP2 on a build that includes Outlook 2003
and rolled it out on a big network without any problems. The main
difference is that I'm patching PRO11.MSI (or whatever). I seem to
remember there was a separate procedure for patching the OWC11.MSI
It's a bit strange your target isn't PRO11.MSI anyway; I mean usually
you apply a TRANSFORM with the components you want (e.g. Outlook only),
but it wouldn't be able to give the MSI file a different name. It's
almost as if you created an AIP for _Outlook_ as opposed to one for
_Office_ that only contains the Outlook App and nothing else...