Patch Management Solution

 View Only

  • 1.  Poor compliance for APSB16-10

    Posted Apr 26, 2016 01:23 AM

    Just wondering if anyone else is seeing very poor compliance for the Adobe patch APSB16-10? I am seeing extremely low compliance on this specific patch this month, with every other patch being fine.

    The odd thing is that the NS sees the systems as non-compliant, but if I go to the system and check in the agent Software Updates it is not listed, and reviewing the InstallLog.csv it never even attempted to install.



  • 2.  RE: Poor compliance for APSB16-10

    Posted May 02, 2016 01:24 PM

    Where are you seeing that APSB16-10 has poor compliance? 

    Please verify that you have the debuggers checked on your vendor list in the PMImport and that you have 11 updates for APSB16-10. 

    AdobeAIRInstaller2100198.exe flashplayer_18_ax_debug1800343.exe flashplayer_18_plugin_debug1800343.exe
    flashplayer_21_ax_debug2100213.exe flashplayer_21_plugin_debug2100213.exe flashplayer_21_ppapi_debug2100213.exe
    install_flash_player_18_active_x1800343.exe install_flash_player_18_plugin1800343.exe install_flash_player_21_active_x2100213.exe
    install_flash_player_21_plugin2100213.exe install_flash_player_21_ppapi2100213.exe  

    Also,  do you have "Delete " and "checked in your metadata import? 

    APSB16-10 superseded APSB16-08, please verify the compliance of APSB16-08 also.



  • 3.  RE: Poor compliance for APSB16-10

    Posted May 02, 2016 03:21 PM

    I'm running the Windows Compliance by Bulletin report.

     

    I don't have delete previously downloaded data or automatically revise checked, but I did manually re-download this patch as it did get updated at least once. That didn't change anything, my compliance is still sitting at 16% for my workstations, showing as applicable to 1677, only installed on 275. 



  • 4.  RE: Poor compliance for APSB16-10
    Best Answer

    Posted May 02, 2016 04:44 PM

    I created a new policy, applied to the same target as the original policy, and now the update is showing up on the agent so that appeared to resolve it. Not sure why the new policy was needed, but at least it appears to be working.

     

    Thanks for the reply though Christina.