Re: MBSA 1.2 documentation
From: Adam Welker [MSFT] (adamwel_at_online.microsoft.com)
Date: 06/29/04
- Next message: SCHC-Steve: "Clients will not install. I get an Admin$ share issue. Logs past"
- Previous message: Adam Welker [MSFT]: "Re: SMS2003 - Confusion about MSXML"
- In reply to: stevejenk: "Re: MBSA 1.2 documentation"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 29 Jun 2004 09:08:11 -0700
Uninstalled means the last status message regarding this update was that the
update was "removed". This means that the scan tool detected, at least once
that the update was installed. At some later time the scan tool detected
the update was missing.
Advertisement success means that the ad ran successfully, but is not an
indication in any way the update was installed or even attempted or what the
status was.
I'm not sure what the complete scenario is here and there are several
different possibilites. Generally speaking though if the update is
attempted you should have patch status which should over write the
"uninstalled" status. If the package is running, but the update is not
being attempted then the last status could legitimitely be uninstalled.
Check the patchinstall.log to verify the update is truly running.
-- Adam Welker This posting is provided "AS IS" with no warranties, and confers no rights. "stevejenk" <stevejenk@discussions.microsoft.com> wrote in message news:7AA0EAA5-3400-4866-813B-0F297313BF02@microsoft.com... > OK you touched upon the most common of the Distribution State messages now how about UNINSTALLED. Why would I get that status. The package has reported success in the console, but it continues to run the MDAC update and the status has been uninstalled for the last two attempts. > > > "Adam Welker [MSFT]" wrote: > > > These are not MBSA messages. The aren't even scan tool messages for the > > most part. > > > > No status means exactly that, no distribution status messages have been > > received from the client for that update. > > Preliminary Success means an update was installed and reported success with > > no reboot required, however another update in the package was installed > > which does require a restart. > > Pending Reboot usually means an update was installed but needs a reboot to > > be considered successful. > > Retrying is basically any state where we didn't install an update and expect > > to retry the installation on the next advertisement schedule assignment > > time. This excludes failures which is another state. > > -- > > Adam Welker > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > > > >
- Next message: SCHC-Steve: "Clients will not install. I get an Admin$ share issue. Logs past"
- Previous message: Adam Welker [MSFT]: "Re: SMS2003 - Confusion about MSXML"
- In reply to: stevejenk: "Re: MBSA 1.2 documentation"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
