Client Management Suite

 View Only
  • 1.  Software Update Policies- One Per Bulletin or Consolidate?

    Posted Mar 17, 2010 08:16 AM
    Historically, we have created one software update policy per bulletin, the reason being it was easier to disable a specific patch if needed.  I have been thinking about creating one policy per month of patches to consolidate them.  I know in the advanced tab you can actually disable specific updates so I am thinking I would not be missing out on the flexibility of simply disabling an individual patch policy.

    How does everyone else do it?  Are there any best practices I should be aware of?


  • 2.  RE: Software Update Policies- One Per Bulletin or Consolidate?

    Posted Mar 17, 2010 09:53 AM

    and either remove superseeded or disabled unneeded updates. I was the happiest guy in the world when the update came out that allowed multiple bulletins\updates per policy. (I know, I'm too easy to please).


  • 3.  RE: Software Update Policies- One Per Bulletin or Consolidate?

    Posted Mar 17, 2010 02:08 PM
    I do the entire month together following this format:

    YEAR - MONTH - RELEASE
    2010 - 01 - A

    This way when you open them in the console tree you can view them in a logical order and quickly find the patches you need.  Also regarding the release letter, if I have a patch that I apply any different it might get it's own release letter, so that I can enable, disable or apply to a different collection.

    Hope that helps!


  • 4.  RE: Software Update Policies- One Per Bulletin or Consolidate?

    Posted Jun 17, 2010 03:46 PM
    I usually try to put all bulletins for a month into one task, but some have up to 60 patch executables in one bulletin.  I try not to have more than about 50-60 in one task, so I'll break a month into multiple tasks.

    By the way, I'm not sure if "task" is the correct word, but it works for me.