<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You raise a good point and it is something we are trying to do more of. We held a call with a large number of partners earlier this year that covered many of the popular topics (upgrades, P2V migrations, SBD) and it seemed to go over very well. I expect we'll do more in the future and hopefully I can manage to get to the Partner Summit this year. <div><br></div><div>How "major" an upgrade is depends heavily on the specific deployment. It also depends on your (or the partner's) confidence and ability to plan, test, and verify an upgrade such that at the end of the maintenance window both the partner and customer has a satisfactory level of confidence that everything is working just as well as it was before the upgrade. Note that there may be many reasons why that confidence and ability aren't present. Lack of resources, a customer that doesn't want to take the extra time to generate and implement a test plan, etc. There are many factors that can keep folks from doing things the way they'd like to do them. <br><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:47 AM, Jason Gurtz wrote:</div><br class="Apple-interchange-newline"><div>Hopefully, resources like this list would be passed on by Cisco (with<br>participation highly encouraged) to the channel at large at your special<br>meetings and events.<br><br>Most times, people I talk to are like, "mailing list, huh?" It is easy to<br>see the participants in this list are the cream of the crop in cisco-voip<br>land. The people we work with are technically OK, but seem unplugged.<br>Meanwhile I come from the networking and server infrastructure side with<br>little voip experience (just trying to catch up. :)<br><br>I hear ya WRT major version releases and being careful. Unfortunately, our<br>reseller regards even the smallest point release as a major upgrade. :( My<br>expectation is something like quarterly or semi-annual upgrades to latest<br>point release or SU; is that a reasonable expectation?<br><br>Cheers,<br><br>~JasonG<br><br><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite">From: Buchanan, James [mailto:jbuchanan@presidio.com]<br></blockquote><blockquote type="cite">Sent: Tuesday, July 10, 2012 11:34<br></blockquote><blockquote type="cite">To: Jason Gurtz; Ryan Ratliff<br></blockquote><blockquote type="cite">Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br></blockquote><blockquote type="cite">Subject: RE: [cisco-voip] CUCM 8.6 licenses disappear on reboot<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Speaking from the channel side, I certainly don't take that position.<br></blockquote><blockquote type="cite">That said, when a new major release comes out (like 9.0), I exercise<br></blockquote><blockquote type="cite">caution and make sure to read the release notes closely as well as the<br></blockquote><blockquote type="cite">SRND. With a minor release and a service release, there generally is a<br></blockquote><blockquote type="cite">reason for it, such as SU1, so in a situation like this one that's been<br></blockquote><blockquote type="cite">described, I would go straight to SU1, still having read the release<br></blockquote><blockquote type="cite">notes. A lot of this comes back to experience, and lists like this help<br></blockquote><blockquote type="cite">all of us share our experiences and go forth better informed.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">James Buchanan| UC Technology Manager | Presidio South |<br></blockquote><blockquote type="cite">Presidio Networked Solutions<br></blockquote><blockquote type="cite">12 Cadillac Dr Ste 130 Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><br></blockquote><blockquote type="cite">D: 615-866-5729 | F:615-866-5781 <a href="http://www.presidio.com">www.presidio.com</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite">From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto:cisco-voip-<br></blockquote><blockquote type="cite"><a href="mailto:bounces@puck.nether.net">bounces@puck.nether.net</a>] On Behalf Of Jason Gurtz<br></blockquote><blockquote type="cite">Sent: Tuesday, July 10, 2012 10:26 AM<br></blockquote><blockquote type="cite">To: Ryan Ratliff<br></blockquote><blockquote type="cite">Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br></blockquote><blockquote type="cite">Subject: Re: [cisco-voip] CUCM 8.6 licenses disappear on reboot<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">I'm curious why each of you would do an upgrade to 8.6(2) base when<br></blockquote></blockquote><blockquote type="cite"><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><blockquote type="cite"><blockquote type="cite">upgrade via PUT to get the license but there's no reason to do the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2-step<br></blockquote></blockquote><blockquote type="cite">upgrade<br></blockquote><blockquote type="cite"><blockquote type="cite">when SU1 is the desired destination (or should be).<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I can't speak for any others of course but I can say that our reseller<br></blockquote>is<br><blockquote type="cite">staunchly against upgrading...period. The only time they will recommend<br></blockquote><blockquote type="cite">an upgrade is when we are actively experiencing a known bug and there is<br></blockquote><blockquote type="cite">no workaround. This goes for Cisco VOIP as well as more traditional<br></blockquote><blockquote type="cite">IOS/ASAOS devices. There seems to be a perception and intense fear of<br></blockquote><blockquote type="cite">"spaghetti code" type issues. e.g. fix this; break that, general<br></blockquote><blockquote type="cite">likelihood of regressions, etc... With all the bugs and warts<br></blockquote>experienced<br><blockquote type="cite">I'm not sure I would say the fear is unfounded! With no Linux CLI access<br></blockquote><blockquote type="cite">to actually fix anything, the fear increases.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Internally, we are not allowed to do anything unless<br></blockquote>recommended/approved<br><blockquote type="cite">by our reseller.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">It would be great if Cisco could (broadly) inform the channel<br></blockquote><blockquote type="cite">(VARs/Resellers/Etc...) about the benefits of keeping software<br></blockquote>up-to-date<br><blockquote type="cite">vs. the "Mainframe Mentality." Also, best practices WRT testing/QA for<br></blockquote><blockquote type="cite">bugs before roll-out...<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Again, that's our situation, hoping it's not a widespread one.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">~JasonG<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">cisco-voip mailing list<br></blockquote><blockquote type="cite"><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br></blockquote><blockquote type="cite"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote><blockquote type="cite">This message w/attachments (message) is intended solely for the use of<br></blockquote><blockquote type="cite">the intended recipient and may contain information that is privileged,<br></blockquote><blockquote type="cite">confidential or proprietary. If you are not an intended recipient,<br></blockquote>please<br><blockquote type="cite">notify the sender, and then please delete and destroy all copies and<br></blockquote><blockquote type="cite">attachments. Please be advised that any review or dissemination of, or<br></blockquote><blockquote type="cite">the taking of any action in reliance on, the information contained in or<br></blockquote><blockquote type="cite">attached to this message is prohibited.<br></blockquote><br><br></div></div><br></div></div></body></html>