<div dir="ltr"><div>It depends.</div>
<div> </div>
<div>CM patch when needed. SR as needed for problems you have.</div>
<div> </div>
<div>Test all Major Upgrades! Always weather tested or not have a back out plan! CM 4.x I always had a Mirrored drive to back up to if necassary.</div>
<div> </div>
<div>SR I kind of just sounded off on the list to see if others were having issues.</div>
<div> </div>
<div>OS Patches regularly. Specially on Windows OS.</div>
<div> </div>
<div>UCCx. Only if I have too and same goes for CER.</div>
<div> </div>
<div>Just my two cents.</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Mon, Sep 22, 2008 at 12: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="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<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></div>