<div dir="ltr">Hi Sean,<br><br>Major upgrades - build in test lab if possible. Only patch if needed for compatibility or new feature. I don't load .0 releases of callmanager, been burned before on them. Wait for the .1 version imo<br>
<br>CM, CER<br>Service releases - only if needed for a bug fix, but if i'm doing a major upgrade I'll usually load any subsequent SR/ES's as well to get as many bugfixes as possible for the downtime i'm already incurring. I try to let new ES's stew in the wild for a few weeks before I load on our production servers, unless its something super urgent. They seem pretty well tested nowadays though.<br>
<br>Unity, IPCCX<br>Windows OS - We try to do these on a regular basis, if something particularly nasty comes out we evaluate risk and if needed patch ASAP.<br><br>IPCC Express - Only when I absolutely have to do I patch the CRS application itself. I avoid patching it like the plague. Bad luck with introducing bugs.<br>
Unity - Only as needed for compatibility or bug fix.<br><br>Always have a good backup available and a back-out plan. The second partition on the appliance servers is good enhancement for your back-out plan. I also have a standard test plan I run through after any updates to test out major features/dial patterns.<br>
<br>Also.. Hope, pray :)<br><br><div class="gmail_quote">On Mon, Sep 22, 2008 at 3:17 PM, Sean Walberg <span dir="ltr"><<a href="mailto:sean@ertw.com">sean@ertw.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">What do people here do when planning for an upgrade (major? minor?) to CUCM and other components (Unity, IPCCx, CER, etc)? Do you stage something in a test environment? P2V machines and test on those? Hope, pray, and rely on the failback mechanisms?<br>
<br>Also, do you apply every patch? Only when you think it's relevent? Never patch?<br><br>We're about 70 phones in to our deployment of a few thousand, and I'm starting to get asked to put a policy together to answer these questions. I'm curious what has worked for people.<br>
<br>Thanks<br><br>Sean<br clear="all"><br>-- <br>Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> <a href="http://ertw.com/" target="_blank">http://ertw.com/</a><br>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>Assistant Director, Voice Services<br>West Virginia University<br>Telecommunications and Network Operations<br>
</div>