Re: Advanced Client-will not install security updates

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: phoenix (phoenix_at_discussions.microsoft.com)
Date: 08/09/04

  • Next message: TJ: "require winxpsp2 installation guidelines" 
    Date: Mon, 9 Aug 2004 10:53:03 -0700

    I am also having this problem, I have checked the scanning tool and it seems
    to be ok, is there anything else you can suggest?

    "Bippen Bisht [MSFT]" wrote:

    > This error means that the patchinstall agent couldn't find the scan tools.
    > Has the scantools already run on the failing machines? The scantools should
    > have run at least once on the client machines before you attempt to
    > distribute patches to them.
    >
    > -Bippen Bisht [MSFT]
    > This posting is provided "AS IS" with no warranties, and confers no rights.
    >
    > ====================================
    > "krijack" <krijack@discussions.microsoft.com> wrote in message
    > news:FF89D88B-EFDA-4C8C-B441-68E2DD3C3906@microsoft.com...
    > >I am frustrated overan issue with some SMS clients. We run SMS2003
    > >security update distribution tool (latest version)which is functioning well
    > >to a population machines. I am trying to deliver Windows 2000 and Windows
    > >XP MBSA security updates through the distribute software updates function.
    > >
    > > Source: SMS CLient Message ID: 10007
    > > The advertisement status of this package reports back the following
    > > error...
    > >
    > > The program for advertisement "P0120065" failed ("P0100033" - "MBSA -
    > > Win2k Pro Security Updates - TEST"). The failure description was "11203".
    > > User context: NT AUTHORITY\SYSTEM
    > >
    > > Possible cause: The program generated an installation status Management
    > > Information Format (MIF) file with a status value of Failed.
    > > Solution: For more information about the failure, refer to the
    > > documentation for the program you are distributing.
    > >
    > > A Hardware Scan was successfully initiated before the package was
    > > distributed and the same admin accounts are in the workstations that are
    > > having success.
    > >
    > > This package has been delivered successfully to other machines.
    > >
    > > I did a ccm clean and re-installed the client on one machine after many
    > > failures to no avial.
    > >
    > > All else appears ok....Help!
    > >
    > >
    >
    >
    >

  • Next message: TJ: "require winxpsp2 installation guidelines"

    Relevant Pages

    • Re: Advanced Client-will not install security updates
      ... If the patchinstall log is there and has no issues then compare the scan ... >> have run at least once on the client machines before you attempt to ... >>> The advertisement status of this package reports back the following ... >>> having success. ...
      (microsoft.public.sms.misc)
    • Advanced Client-will not install security updates
      ... Source: SMS CLient Message ID: 10007 ... A Hardware Scan was successfully initiated before the package was distributed and the same admin accounts are in the workstations that are having success. ... This package has been delivered successfully to other machines. ...
      (microsoft.public.sms.misc)
    • Re: Advanced Client-will not install security updates
      ... Has the scantools already run on the failing machines? ... > The advertisement status of this package reports back the following ... > having success. ...
      (microsoft.public.sms.misc)
    • LSASS.exe terminated unexpectedly with status code 1073741819
      ... to Ghost are not supported by Microsoft. ... It is precisely for these types of issues that Microsoft ... After running the package the machines started ...
      (microsoft.public.win2000.security)
    • Re: Remote desktop: Problems reconnecting to an existing session.
      ... We are having a persistent issue with Remote Desktop at our company. ... Success Audit 576 immediately afterword)  The next event is a ... All machines are running Windows XP SP3 with updates applied monthly. ... I killed the screensaver remotely, ...
      (microsoft.public.windows.terminal_services)