Midtown Computer Systems Enterprise

Convenient web based access to our favorite computer related Usenet groups.
MCSE.MS is not affiliated with Microsoft corporation, Cisco corporation, Oracle, CompTIA or any other vendor.
Check our Computer Hardware forum | Cell Phones reviews

Go Back  MCSE > Microsoft software reviews > Computer Security reviews > Baseline Analyzer
This is Interesting: Free Computer Magazines Now Free shipping to

Baseline Analyzer microsoft.public.security.baseline_analyzer

 
 
Thread Tools Display Modes
  #1  
Old 03-31-04, 06:51 PM
Luca
Office 2000 Service Pack 3 not being detected by MBSA 1.2
Even though Office 2000 Sevice pack 3 has been applied to a Windows 2000
system with Office 2000, the MBSA scan results are stating Service Pack 3 is
missing. Any information is appreciated.


  #2  
Old 03-31-04, 09:02 PM
Doug Neal [MSFT]
Re: Office 2000 Service Pack 3 not being detected by MBSA 1.2
Can you provide the exact error message?  Can you also provide the versions
of both the "Security update database version" and the "Office update
database version" as displayed at the top of your completed scan report for
this machine. The numbers should be

2004.3.9.0
11.0.0.6318

--


Doug Neal [MSFT]
dugn@online.microsoft.com

If newsgroup discussion with experts and MVPs is unable to solve a problem
to your satisfaction, feel free to contact PSS for the Microsoft Baseline
Security Analyzer (MBSA) at the following link:
http://support.microsoft.com/default...s;Prodoffer20a

This e-mail address does not receive e-mail, but is used for newsgroup
postings only.


"Luca" <louis.luca@newline.com> wrote in message
news:%23ywSS%232FEHA.1128@TK2MSFTNGP11.phx.gbl...
> Even though Office 2000 Sevice pack 3 has been applied to a Windows 2000
> system with Office 2000, the MBSA scan results are stating Service Pack 3

is
> missing. Any information is appreciated.
>
>



  #3  
Old 04-01-04, 12:48 PM
Luca
Re: Office 2000 Service Pack 3 not being detected by MBSA 1.2
Here is what the report says:

Office Security Updates - 2 security udates are missing.

Access 2000 Snashot Viewer Patch: KB826292 (English Version)
This update requires Office 2000 Service pack 3 (English Version) to be
installed first.

Office 2000 Service Pack 3 (English version)


The versions you mention below are the same versions I see on the report.
2004.3.9.0
11.0.0.6318

Thanks

"Doug Neal [MSFT]" <dugn@online.microsoft.com> wrote in message
news:uJ%23Jlj3FEHA.3856@TK2MSFTNGP12.phx.gbl...
> Can you provide the exact error message? Can you also provide the

versions
> of both the "Security update database version" and the "Office update
> database version" as displayed at the top of your completed scan report

for[color=blue]
> this machine. The numbers should be
>
> 2004.3.9.0
> 11.0.0.6318
>
> --
>
>
> Doug Neal [MSFT]
> dugn@online.microsoft.com
>
> If newsgroup discussion with experts and MVPs is unable to solve a problem
> to your satisfaction, feel free to contact PSS for the Microsoft Baseline
> Security Analyzer (MBSA) at the following link:
> http://support.microsoft.com/default...s;Prodoffer20a
>
> This e-mail address does not receive e-mail, but is used for newsgroup
> postings only.
>
>
> "Luca" <louis.luca@newline.com> wrote in message
> news:%23ywSS%232FEHA.1128@TK2MSFTNGP11.phx.gbl...
3
> is
>
>



  #4  
Old 04-01-04, 07:17 PM
Doug Neal [MSFT]
Re: Office 2000 Service Pack 3 not being detected by MBSA 1.2
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.


--


Doug Neal [MSFT]
dugn@online.microsoft.com

If newsgroup discussion with experts and MVPs is unable to solve a problem
to your satisfaction, feel free to contact PSS for the Microsoft Baseline
Security Analyzer (MBSA) at the following link:
http://support.microsoft.com/default...s;Prodoffer20a

This e-mail address does not receive e-mail, but is used for newsgroup
postings only.


"Luca" <louis.luca@newline.com> wrote in message
news:OPIm1JAGEHA.624@TK2MSFTNGP10.phx.gbl...[color=blue]
> Here is what the report says:
>
> Office Security Updates - 2 security udates are missing.
>
> Access 2000 Snashot Viewer Patch: KB826292 (English Version)
> This update requires Office 2000 Service pack 3 (English Version) to be
> installed first.
>
> Office 2000 Service Pack 3 (English version)
>
>
> The versions you mention below are the same versions I see on the report.
> 2004.3.9.0
> 11.0.0.6318
>
> Thanks
>
> "Doug Neal [MSFT]" <dugn@online.microsoft.com> wrote in message
> news:uJ%23Jlj3FEHA.3856@TK2MSFTNGP12.phx.gbl...
> versions
> for
problem[color=blue]
Baseline[color=blue]
2000[color=blue]
Pack
> 3
>
>



  #5  
Old 04-01-04, 07:17 PM
Gerry Hickman
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)
  #6  
Old 04-01-04, 07:17 PM
Luca
Re: Office 2000 Service Pack 3 not being detected by MBSA 1.2
Thank you both!

"Gerry Hickman" <gerry666uk@yahoo.co.uk> wrote in message
news:OfWKWVCGEHA.4044@TK2MSFTNGP10.phx.gbl...
> 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.[color=blue]
>
> 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:
>
user-installed[color=blue]
is[color=blue]
installed[color=blue]
be[color=blue]
installed in[color=blue]
setup[color=blue]
being[color=blue]
the[color=blue]
issue[color=blue]
issue[color=blue]
applied[color=blue]
the[color=blue]
the[color=blue]
the[color=blue]
problem[color=blue]
somewhere[color=blue]
is[color=blue]
above[color=blue]
of[color=blue]
method.
>
>
> --
> Gerry Hickman (London UK)



  #7  
Old 04-02-04, 07:07 PM
Luca
Re: Office 2000 Service Pack 3 not being detected by MBSA 1.2
Doug

I went out to the Office Update and loaded SP3 for Office 2000. That took
care of the issue. Thanks again for the procedure and I wanted to let you
know that I didn't need to perform the step you outlined. Maybe Microsoft
fixed this issue at the Update site.

Thanks
Luca





"Doug Neal [MSFT]" <dugn@online.microsoft.com> wrote in message
news:eKAj1QBGEHA.3880@TK2MSFTNGP09.phx.gbl...
> 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[color=blue]
> 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.
>
>
> --
>
>
> Doug Neal [MSFT]
> dugn@online.microsoft.com
>
> If newsgroup discussion with experts and MVPs is unable to solve a problem
> to your satisfaction, feel free to contact PSS for the Microsoft Baseline
> Security Analyzer (MBSA) at the following link:
> http://support.microsoft.com/default...s;Prodoffer20a
>
> This e-mail address does not receive e-mail, but is used for newsgroup
> postings only.
>
>
> "Luca" <louis.luca@newline.com> wrote in message
> news:OPIm1JAGEHA.624@TK2MSFTNGP10.phx.gbl...
report.[color=blue]
report
> problem
> Baseline
> 2000
> Pack
>
>



  #8  
Old 04-02-04, 07:07 PM
Gerry Hickman
Re: Office 2000 Service Pack 3 not being detected by MBSA 1.2
Luca wrote:

> know that I didn't need to perform the step you outlined. Maybe Microsoft
> fixed this issue at the Update site.


Yes, but how much use is that if you've got 100 workstations that need
updated? The whole point of using an Administrative Installation Point
is that everything is automated.

Unless you give your users Admin rights I don't think the update site
would work, and even if it did, it's an extremely inefficient way of
updating 100 machines - plus the users are wasting time waiting for it
to install and clicking "I Agree" to text they don't even understnad,
instead of doing their work.

I do the udpates overnight.

--
Gerry Hickman (London UK)
 


Popular forums
A+ (A Plus) Windows 2000 Active directory Exchange 2000 information store
Network+ Windows XP Security Exchange 2000 server administration
MCSE .NET Web services SQL Server
Cisco certification ASP .NET SQL 2000 Programming
Windows 2000 Registry .NET XML Viruses


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 12:06 PM.


Powered by vBulletin Version 3.6.2
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
Copyright MCSE braindumps 2003-2006