Software Update Policies- One Per Bulletin or Consolidate?
Created: 17 Mar 2010 | 3 comments
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?
discussion Filed Under:
Comments
I typically enable an entire month
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).
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
YEAR - MONTH - RELEASE
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!
Screenbert
Either one
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.
Would you like to reply?
Login or Register to post your comment.