Skip navigation
1463 Views 9 Replies Latest reply: Feb 23, 2012 4:00 AM by Frank Wils RSS
RWilk Rookie 14 posts since
Mar 31, 2010

Has received 1 of 9 achievements.
Currently Being Moderated

Feb 20, 2012 11:59 AM

How To Troubleshoot Patches That Fail

I'm going to post a discussion I have a feeling has been asked before.  Its common for me to push out a patch (in this case Adobe Flash, but it happens with Microsoft updates) and a relatively small subet of computers (~5%) show up as failed.  I look at the logs in the Management console and it gives no detail on why it failed.

 

Here is a screenshot of a list of machine that failed (either all patches or some).

 

And here is the logs from the Management console from one of the machines.  I'm stuck on how to troubleshoot this.  Of course I replaced my server name with (core server).  In this case I'm patching the latest Adobe Flash updates: FLASHPLAYERPLUGINv11.1.102.62 and FLASHPLAYERv11.1.102.62.

 

Verifying device ID with core (core server)
     Done
Updating settings
     Done
Sending current settings information to core
     Done
Getting list of patches
     Done.  2 patches were found
Downloading http://(core server)/LDLogon/patch/install_flash_player_32bit_11.1.102.62.exe
Downloading file from source http://(core server)/LDLogon/patch/install_flash_player_32bit_11.1.102.62.exe.
Downloading file from source http://(core server)/LDLogon/patch/install_flash_player_32bit_11.1.102.62.exe.
Downloading file from source http://(core server)/LDLogon/patch/install_flash_player_32bit_11.1.102.62.exe.
Downloading file from peer http://(core server)/LDLogon/patch/install_flash_player_32bit_11.1.102.62.exe (10.170.7.34).
     Done
Downloading http://(core server)/LDLogon/patch/install_flash_player_ax_32bit_11.1.102.62.exe
Downloading file from source http://(core server)/LDLogon/patch/install_flash_player_ax_32bit_11.1.102.62.exe.
Downloading file from source http://(core server)/LDLogon/patch/install_flash_player_ax_32bit_11.1.102.62.exe.
Downloading file from source http://(core server)/LDLogon/patch/install_flash_player_ax_32bit_11.1.102.62.exe.
Downloading file from peer http://(core server)/LDLogon/patch/install_flash_player_ax_32bit_11.1.102.62.exe (10.170.7.34).
     Done
Running patch install_flash_player_32bit_11.1.102.62.exe
Installing patch 1 out of 2 patches
     Failed
     Done
Running patch install_flash_player_ax_32bit_11.1.102.62.exe
Installing patch 2 out of 2 patches
     Done
     Done
Getting definition data from core (core server)
     Done
Current Definition ID: FLASHPLAYERPLUGINv11.1.102.62
FLASHPLAYERPLUGINv11.1.102.62 detected
Current Definition ID: FLASHPLAYERPLUGINv10.3.183.11
Current Definition ID: FLASHPLAYERPLUGINv11.1.102.55
Current Definition ID: FLASHPLAYERv11.1.102.62
Current Definition ID: FLASHPLAYERv10.3.183.11
Current Definition ID: FLASHPLAYERv11.1.102.55
     Done
Sending scan results to core (core server)
     Done

  • Bradley_M Apprentice 52 posts since
    Apr 29, 2010

    Has received 1 of 9 achievements.
    Currently Being Moderated
    2. Feb 21, 2012 2:46 PM (in response to RWilk)
    Re: How To Troubleshoot Patches That Fail

    Since your failure rate is less than %5 my initial guess is that these people might be actively using the flashplayer at the time.  Therefore it can't update Flash Player because it is active.  Similarly I have a lot of trouble using LANDesk to natively repair Java from what I guess is that Java really likes IE closed when this is done.

     

    If you try the patches against your failures again do you pick additional successful ones or are they continually failed over and over?

  • Frank Wils SSMMVPGroup 1,214 posts since
    Feb 25, 2008

    Has received 8 of 9 achievements.
    Currently Being Moderated
    4. Feb 22, 2012 8:46 AM (in response to RWilk)
    Re: How To Troubleshoot Patches That Fail

    Look at the vulscan logfiles on the client in %ALLUSERSPROFILE%\ Application Data\Vulscan

     

    Frank

    Axle-IT

  • Rookie 8 posts since
    Sep 28, 2011

    Has received 1 of 9 achievements.
    Currently Being Moderated
    6. Feb 22, 2012 9:14 AM (in response to RWilk)
    Re: How To Troubleshoot Patches That Fail

    RWilk,

     

     

    you can use the Xtrace on client if you want to go in details also you can go to Run  and type vulscan e  it will directly take you to the vulscan log file.

     

     

     

     

    Regards

  • Bradley_M Apprentice 52 posts since
    Apr 29, 2010

    Has received 1 of 9 achievements.
    Currently Being Moderated
    7. Feb 22, 2012 3:16 PM (in response to ahsan)
    Re: How To Troubleshoot Patches That Fail

    I didn't know this option was in there but supposedly you can have the patch force Firefox, IE, and other things closed if you change the force mode on the patch.  I have never tried this on a patch before.  Has anybody tried?

  • mrspike SSMMVPGroup 1,321 posts since
    Dec 19, 2007

    Has received 9 of 9 achievements.
    Currently Being Moderated
    8. Feb 22, 2012 3:21 PM (in response to ahsan)
    Re: How To Troubleshoot Patches That Fail

    If you are willing to force close the browsers without any warning, you can go into the patch and there is a "custom variables" tab at the top and you can set this to "yes", thsi will force the browsers to close.

     

    You could clone the original patch and have one that will force close, and leave the orignal as is.... I do this, and advise our patching flks that they should only use the force close version at night and only after a few attempts have been made the other way

  • Frank Wils SSMMVPGroup 1,214 posts since
    Feb 25, 2008

    Has received 8 of 9 achievements.
    Currently Being Moderated
    9. Feb 23, 2012 4:00 AM (in response to RWilk)
    Re: How To Troubleshoot Patches That Fail

    Glad you found it! Can you please mark it as answered to be helpful to others and give Bradley his credit for his correct answer?

     

    Franj

More Like This

  • Retrieving data ...

Bookmarked By (2)

LANDESK Community powered by Jive SBS® 4.5.7.1  |  Legal Notices  |  Privacy Policy  |  Icon 

TweeterOn Twitter  |  Icon FacebookOn Facebook © 2007 LANDESK Software