Server Management Group

 View Only
  • 1.  Automatically deleting disabled patches from the server

    Trusted Advisor
    Posted Feb 22, 2012 11:53 AM
      |   view attached

    I thought after reaching out to support we had this working, but it appears to not be working now.

    Here's the previous thread with the settings I had (have) set when it was working

    https://www-secure.symantec.com/connect/forums/patch-software-best-practice

     

    I rechecked my settings against what I posted in that thread (when I had it working prevoiusly) and support seems stumped.

    Can anyone confirm their settings and confirm patches disabled are actually being removed from the server?

    In log viewer (attached) it seems to show 2 orphaned linux packages getting deleted (we don't use linux) and nothing for windows.



  • 2.  RE: Automatically deleting disabled patches from the server

    Posted Feb 23, 2012 05:11 PM

    Hi Sally.

    Could you please edit the post marked as solution in the linked thread?

    You mention a 'How do I delete ...' article. Do you have the URL for that and could you update the solution please?

    PS Is that article by any chance this one: Remove Patch Packages for Disabled Bulletins ?



  • 3.  RE: Automatically deleting disabled patches from the server

    Trusted Advisor
    Posted Feb 24, 2012 04:25 PM

    I'll update the post in the linked thread when I have a solution.  Support is working on it.  They said all the settings I mention in that thread are correct.

    I'm not sure where I "mention a 'How do I delete ...' article"   ??



  • 4.  RE: Automatically deleting disabled patches from the server

    Posted Feb 25, 2012 04:40 PM

    In the screenshot above, you refer to a "how do I delete ..." process. Is that available online somewhere?



  • 5.  RE: Automatically deleting disabled patches from the server

    Trusted Advisor
    Posted Feb 25, 2012 08:04 PM

    The steps / process support told me to follow is what I outlined in the post in the prior thread marked as solution.  It's still correct according to support.