<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>This would be my exact recommendation. Slow-roll the new major releases but once you commit to the upgrade go straight to the latest available in that version. </div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-Ryan</div></span>
</div>
<br><div><div>On Jul 10, 2012, at 11:34 AM, Buchanan, James wrote:</div><br class="Apple-interchange-newline"><div>Speaking from the channel side, I certainly don't take that position. That said, when a new major release comes out (like 9.0), I exercise caution and make sure to read the release notes closely as well as the SRND. With a minor release and a service release, there generally is a reason for it, such as SU1, so in a situation like this one that's been described, I would go straight to SU1, still having read the release notes. A lot of this comes back to experience, and lists like this help all of us share our experiences and go forth better informed. <br><br>James Buchanan| UC Technology Manager | Presidio South | Presidio Networked Solutions <br>12 Cadillac Dr Ste 130 Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><br>D: 615-866-5729 | F:615-866-5781 <a href="http://www.presidio.com">www.presidio.com</a><br><br><br>-----Original Message-----<br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Jason Gurtz<br>Sent: Tuesday, July 10, 2012 10:26 AM<br>To: Ryan Ratliff<br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] CUCM 8.6 licenses disappear on reboot<br><br><blockquote type="cite">I'm curious why each of you would do an upgrade to 8.6(2) base when <br></blockquote><blockquote type="cite">SU1 is out there on <a href="http://cisco.com">cisco.com</a>? You still have to order the 8.6(2) <br></blockquote><blockquote type="cite">upgrade via PUT to get the license but there's no reason to do the <br></blockquote><blockquote type="cite">2-step<br></blockquote>upgrade<br><blockquote type="cite">when SU1 is the desired destination (or should be).<br></blockquote><br>I can't speak for any others of course but I can say that our reseller is staunchly against upgrading...period. The only time they will recommend an upgrade is when we are actively experiencing a known bug and there is no workaround. This goes for Cisco VOIP as well as more traditional IOS/ASAOS devices. There seems to be a perception and intense fear of "spaghetti code" type issues. e.g. fix this; break that, general likelihood of regressions, etc... With all the bugs and warts experienced I'm not sure I would say the fear is unfounded! With no Linux CLI access to actually fix anything, the fear increases.<br><br>Internally, we are not allowed to do anything unless recommended/approved by our reseller.<br><br>It would be great if Cisco could (broadly) inform the channel<br>(VARs/Resellers/Etc...) about the benefits of keeping software up-to-date vs. the "Mainframe Mentality." Also, best practices WRT testing/QA for bugs before roll-out...<br><br>Again, that's our situation, hoping it's not a widespread one.<br><br>~JasonG<br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>https://puck.nether.net/mailman/listinfo/cisco-voip<br>This message w/attachments (message) is intended solely for the use of the intended recipient and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.<br><br><br></div></div><br></div></body></html>