Agree 100%.. even if you can swing just replacing the pub on ccm it cuts out a good bit of time and gives you a nice backout option.<br><br><div class="gmail_quote">On Jan 28, 2008 4:41 PM, Jonathan Charles <<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">New servers... then just drop em in....<br><font color="#888888"><br><br>Jonathan<br></font><div>
<div></div><div class="Wj3C7c"><br>On Jan 28, 2008 3:12 PM, Scott Voll <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>> wrote:<br>> yes, you have to do the two(CM and IPCC) at the same time. This is a big<br>
> killer (time wise). especially on large clusters. I'm up against the same<br>> issue.<br>><br>> Scott<br>><br>><br>><br>> On Jan 28, 2008 9:31 AM, Miller, Steve <<a href="mailto:MillerS@dicksteinshapiro.com">MillerS@dicksteinshapiro.com</a>> wrote:<br>
><br>> > To clarify:<br>> ><br>> > It is necessary to upgrade to IPCC 5.0 when upgrading the CCM to 6.X ?<br>> > Is it possible to upgrade the IPCC in advance - while still operating on<br>> > 4.1 ? Would that make the transition/upgrade to 6.1 easier since it<br>
> > would be too separate processes?<br>> ><br>> ><br>> > Steve Miller<br>> > Telecom Engineer<br>> > Dickstein Shapiro LLP<br>> > 1825 Eye Street NW | Washington, DC 20006<br>> > Tel (202) 420-3370| Fax (202) 330-5607<br>
> > <a href="mailto:MillerS@dicksteinshapiro.com">MillerS@dicksteinshapiro.com</a><br>> ><br>> ><br>> ><br>> ><br>> ><br>> > -----Original Message-----<br>> > From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> > [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Jonathan<br>> > Charles<br>> > Sent: Wednesday, December 19, 2007 11:58 AM<br>> > To: <a href="mailto:Peterson_Erik@aac.com">Peterson_Erik@aac.com</a><br>
> > Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> > Subject: Re: [cisco-voip] Call Manager 6 upgrade and IPCC-X<br>> ><br>> > I have done this 'upgrade' (notice the quotes...)<br>
> ><br>> > It isn't really an upgrade, I just back up everything (prompts,<br>> > scripts, docs, etc..) and then recreate everything from scratch on the<br>> > new server... it isn't quick, but it works...<br>
> ><br>> ><br>> ><br>> > Jonathan<br>> ><br>> > On Dec 18, 2007 4:49 PM, <<a href="mailto:Peterson_Erik@aac.com">Peterson_Erik@aac.com</a>> wrote:<br>> > > Keep in mind there is no actual upgrade path from UCCX 4.0 to 5.0,<br>
> > only<br>> > > from 4.5 to 5.0.<br>> > ><br>> > > >So when I upgrade from CM 4.1 to 6.1 I also have to upgrade UCCx 4.0<br>> > to<br>> > > 5.0,<br>> > > >Xmedius, Berbee informaCast, Arc Console, School Messenger, etc. So<br>
> > I<br>> > > feel<br>> > > >your indigestion.<br>> > ><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>> > _______________________________________________<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>> ><br>> > --------------------------------------------------------<br>> > This e-mail message and any attached files are confidential<br>> > and are intended solely for the use of the addressee(s)<br>
> > named above. This communication may contain material<br>> > protected by attorney-client, work product, or other<br>> > privileges. If you are not the intended recipient or person<br>> > responsible for delivering this confidential communication<br>
> > to the intended recipient, you have received this<br>> > communication in error, and any review, use, dissemination,<br>> > forwarding, printing, copying, or other distribution of<br>> > this e-mail message and any attached files is strictly<br>
> > prohibited. Dickstein Shapiro reserves the right to monitor<br>> > any communication that is created, received, or sent on its<br>> > network. If you have received this confidential<br>> > communication in error, please notify the sender<br>
> > immediately by reply e-mail message and permanently delete<br>> > the original message.<br>> ><br>> > To reply to our email administrator directly, send an email<br>> > to <a href="mailto:postmaster@dicksteinshapiro.com">postmaster@dicksteinshapiro.com</a><br>
> ><br>> > Dickstein Shapiro LLP<br>> > <a href="http://www.DicksteinShapiro.com" target="_blank">http://www.DicksteinShapiro.com</a><br>> ><br>> ><br>> ==============================================================================<br>
> ><br>> ><br>> ><br>> ><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>><br>><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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations