
Re: Office 2000 Service Pack 3 not being detected by MBSA 1.2
Hi all,
Yup, I can confirm what Doug is saying too. All in all, it's a bit of a
nightmare, especially when OUTLCTLX.EXE appears to only copy one pesky
DLL! All that trouble for one DLL! I may try copying it with a script
one day, and see what happens.
You are also supposed to update the ACWZ*.MDE files too before applying SP3.
I really hope they fix this in Office 2000 SP4?
The whole thing is compounded by the fact MBSA cannot scan remote
machines for Office.
I also noted some strange behaviour related to post SP3 patches not
being recognized by MBSA on some machines, but were fine on others -
never got to the bottom of it.
Doug Neal [MSFT] wrote:
> Luca,
>
> Turns out this is a complicated problem that stems from the difference
> between an Administrator-installed version of Office and the user-installed
> version of Office. The steps below are somewhat invovled, but should be
> able to step you through the steps necessary to resolve this problem.
>
> ---------------------
>
> Office 2000 SP3 included an IExpress package, OUTLCTLX.exe that is not
> applicable to admin installations. That's why the patch is not shown as
> installed - and simply installing MAINSP3.MSP in the admin installation is
> not enough to consider SP3 installed. OUTLCTLX.EXE should also be installed
> on the machine. The fact that it is stating that an admin patch should be
> used is confusing, but is by design since the MAINPSP3 patch is installed in
> an admin image and the detection is trying to avoid a mixture of
> client/admin patches. The other problem related to this is that ART setup
> will change the InstallRoot of office and point somewhere else, thus
> breaking the detection of the IExpress package (which is another issue being
> considered by the Office team to change/update in a future version of the
> tool). A reinstall/repair of the product should fix this InstallRoot issue
> and fix the detection information.
>
>
>
>
>
> Here's a more step-by-step breakdown of the necessary steps on this issue
> for customers who may need more guidance:
>
>
>
> This is generally a problem with AdminApplicable patches vs. locally applied
> patches. To help clarify the details above, you may want to download the
> O2KSP3.EXE (Office 2000 SP3) patch and run it from a command-line with the
> following parameter
>
> O2KSP3 /C
>
> Once it is expanded, you will notice the OUTLCTLX.EXE and MAINSP3.MSI
> packages.
>
> Although the OUTLCTLX.exe that is not applicable to admin installations, the
> fact that this is not applied to the local machine is causing the problem
> with the SP3 patch not showing that it is installed. Simply installing
> MAINSP3.MSI in the admin installation is not enough to consider SP3
> installed. You need to also install OUTLCTLX.EXE on the local machine.
>
> Another problem users MAY have in this situation is that the ARTSP3.MSI
> (Admin installer) will change the InstallRoot of office and point somewhere
> else, which breaks the correct detection of SP3 (which the Office team is
> hoping to fix in the future). If you have already performed the steps above
> to install OUTLCTLX.EXE on the local machine and still have a problem
> correctly detecting SP3, the Office Team recommends a reinstall/repair of
> the product to fix the InstallRoot issue and fix the SP3 detection.
>
> Please let me know if this is helps clarify the necessary steps to solve
> this problem - and if you're able to solve the problem using this method.
>
>
--
Gerry Hickman (London UK)