That's usually the best way to go.. But with reference to Remedy and its ITSM suite of products, you might want to reconsider that stance, and review the release notes to check the fix lists.. some of the bugs fixed as a result of some of those patches were problems that would have hit you somewhere down the road so these patches were worth installing rather than wait as most of them were workflow related so it was easy to see what was fixed.
It sometimes sucks though when patches are released barely weeks from each other.. What I usually do is if workflow is fixed as in ITSM sort of patches, I go ahead and apply them right away. You can't go too wrong doing that. However I prefer waiting and watching the release results of core patches like patches to the AR Server, Mid-Tier, E-Mail engine, as these patches are usually more software patches than application patches.. If I do have the luxury of working with development servers though I do tend to apply them on a weekend and see how it goes, and roll out if there seems to be a obvious problem.. Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Robert Molenda Sent: Monday, September 10, 2007 1:44 PM To: [email protected] Subject: Re: Request For Opinion/Knowledge: Patches ** We use the ole-adage “If It Ain’t broke-Don’t Fix it” With the multitude of patches coming out, it is next to impossible for us to be “current” because of our “release cycle” is 9 weeks (unless an emergency arises) We ALWAYS keep Admin-Tool & Server versions in synch. AND since we are mixed (6.3 and 7.0.1) we have TWO Admin tools installed. This simply is to avoid the “Shoot yourself in the foot” issue that can happen… Generally Mid Tier is also the same as the server, but we have been testing Higher to Lower versions for performance. And as with Micro$oft patches, WAIT until you know it will not destroy your system before applying… Thank-goodness for SandBox-Clones these days… Thanks-n-advance; HDT Platform Incident / Problem Manager & Architect Robert Molenda IT OS PA Tel: +1 408 503 2701 Fax: +1 408 503 2912 Mobile: +1 408 472 8097 [EMAIL PROTECTED] Quality begins with your actions. ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Monday, September 10, 2007 10:35 AM To: [email protected] Subject: Re: Request For Opinion/Knowledge: Patches ** Three words: Don't. Buy. Trouble. If what you have is working, and there's nothing in the patch worth risking a smoothly operating system, I'd hold off until there's a need to upgrade. At that, I would wait about 2 weeks after a patch is released - if it's still out there after then, it's probably going to stay there. Keep Admin and Server synced up as closely as is possible. Mid-Tier can be a version above AR Server if necessary - the last couple of versions have been helpful in that way. Rick On 9/10/07, Durrant, Michael M. - ITSD <[EMAIL PROTECTED]> wrote: ** Could I please get peoples' opinions/experiences related to patches? Do you always run the latest and greatest or do you only fix it if it's broken? Do you keep your Mid-Tier and AR at the same patch levels? Do you have a "wait" time for releases - BMC releases it and you wait 6 weeks for bugs? Any and all feedback is appreciated. Thank you for your time. Michael Durrant [EMAIL PROTECTED] No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.14/999 - Release Date: 9/10/2007 5:43 PM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
