Re: Office 2003 SP2 installation via AIP for future use with WSUS

Tech-Archive recommends: Fix windows errors by optimizing your registry

The only thing I can think of is a chained setup. However the downside is
that you can't call the pro11.msi directly with msiexec. You would have to
use the setup executable. Chained installs are kinda covered under
http://office.microsoft.com/en-us/assistance/HA011402051033.aspx

"David Chadwick" <david@xxxxxxxxxxxxxxx> wrote in message
news:uPq0JUAxFHA.596@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> My understanding is that WSUS and MU will fail to update Office 2003 if it
> has been installed from an administrative installation point that has been
> altered. Altered means if any service pack or other patch has been
> slipstreamed into the AIP.
>
> My goal is to use SMS to install Office 2003 with SP2 such that from that
> point on clients will use WSUS to patch Office.
>
> To get around the problem of retaining an RTM AIP (for compatibility with
> WSUS) I am installing Office with the following command:
>
> msiexec /qb TRANSFORMS=custom.mst /i pro11.msi PATCH=MAINSP2ff.msp
>
> This is a simplified command line as the one I am actually using obviously
> specifies the full UNC path to the MSI and MSP.
>
> This seems to work fine. Office 2003 is installed on clients and SP2 is
> installed right along with it at the same time. The administrative source
> is still RTM so WSUS should work (although I don't know for sure that it
> does yet).
>
> The final query I have is where does OWC11SP2.msp fit in with this? This
> patch file is in the Office 2003 SP2 download as well as the main file.
> I
> realise it is for Office Web Components (whatever this is), but I am not
> sure at what point I should be applying this patch.
>
> Obviously with my installation command above I am ignoring this patch
> completely. Is PRO11.MSI calling OWC11.MSI? Does that mean I have
> installed Office 2003 with SP2, but OWC is remaining as RTM on the client
> PC? That can't be good. Maybe OWC11.MSI isn't being installed at all? I
> have no idea whether it's part of a standard Office 2003 install or a
> totally separate component.
>
> If it IS being installed with a standard installation, how would I get my
> command line to upgrade OWC11.MSI to SP2 at the same time?
>
> Thanks,
> David
>
>


.

Relevant Pages

  • Re: POLL: SP2 - My Music issue; Respond only if you have experienc
    ... I have installed the sp2 from the windows update site after ... > after the installation of the HP Registry Patch with the following results: ... > If I were to try and fix the My Music problems without using the HP Patch, ...
    (microsoft.public.windows.mediacenter)
  • screend.conf - help an idiot
    ... > You might want to try the appropriate patch listed ... > Modification Type: NEW KIT ... > The Patch Kit Installation Instructions and the ... > 2 Special Instructions ...
    (Tru64-UNIX-Managers)
  • 9_Recommended error codes (specifically return code 5)
    ... * "return code 2" indicates patches are already installed. ... * "return code 25" means a patches requires another patch that is not yet installed. ... With or without using the save option, the patch installation process ... Installing 114008-01... ...
    (SunManagers)
  • SOLUTION: Q811493 crashes system at boot with BSOD C0000135 WINSRV.DLL could not be found
    ... I always had "Automatic Updates" running and downloaded every ... For some reasen, however, patch Q811493 kept ... had, but because KB824141 is also an update of critical KERNEL files, ... Spending 4 hours solving a MS bug (booting from the installation CD is ...
    (microsoft.public.win2000.general)
  • Re: Office 2003 SP2 installation via AIP for future use with WSUS
    ... I found that I had to specify the OWC11SP2ff.msp file on the command line as ... has been installed from an administrative installation point that has been ... Altered means if any service pack or other patch has been ... Office 2003 is installed on clients and SP2 is ...
    (microsoft.public.office.setup)