This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

King for a Day - What would you change?

For the past few weeks I've had some really good discussions around patch management.  The reasons why some people don't patch, the reasoning behind why people do patch, where it fits into an organization and who's role it typically falls under.  All of the conversations have been great and it is clear to me that patching is not just clicking update and walking away.  Patch management should be part of a robust, important and thought out procedure in almost every organization.  Big and small alike, the processes and challenges are pretty similar for all of us.


As a last brainstorming event on the topic, I thought it would be interesting to play King (or Queen) for a Day.  Looking back at the Patch Management process, if you had supreme powers, what would you change?  How different would/could the processes look?  No need to even ground it in reality if you feel strongly enough about it! emoticons_happy.png

Let's start with reboots becoming a thing of the past.  Patch an application or OS and NOT have to restart or incur downtime penalties?!?  Revolutionary!

Expulsion from my computerized Kingdom for any vendor requiring manual patching.  If you've packaged it up in a way that requires me to manually copy files or change registry entries, you haven't put enough time into your patch.  This would be considered a capital offense in my fiefdom.

What would you do if you could just summon your subjects, wave your hand and make it so?

*Reply to this post to earn 50 points and 1 entry to win an iPod Nano

Parents
  • First, I would declare that Microsoft must put in the update window what the update/patch does for each patch.  Not just some of them (although sometimes I think they are trying to do this more often). 

    My next decree is that no vendor should issue a patch that re-installs the entire program!  Fix only what's broken.

    I know you said it, but it's worth repeating.  No reboots!

    During the patching process, it would be required to preserve a copy of all old files and all old registry entries.  It's been said, but here it becomes law...easy painless rollback!

  • My next decree is that no vendor should issue a patch that re-installs the entire program!  Fix only what's broken.

    That's an excellent one!  I completely forgot about that.  It drives me CRAZY to download a 300MB Patch!  At that point, just call it a Release and toss some new features in it!

Reply
  • My next decree is that no vendor should issue a patch that re-installs the entire program!  Fix only what's broken.

    That's an excellent one!  I completely forgot about that.  It drives me CRAZY to download a 300MB Patch!  At that point, just call it a Release and toss some new features in it!

Children
No Data