<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [cisco-voip] Unity 5 upgrading from Unity 4</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText91204 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>This does not sound promising
as I'm about to embark on the win2k/4.0x to win2k3/4.2 to 5.0 myself. I
was going to upgrade to to 4.2 first (since 4.03sr1 isn't supported on win2k3),
dirt backup, install fresh win2k3 install, dirt restore, upgrade to 5.0.
This is going to be ugly...</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net on
behalf of Jonathan Charles<BR><B>Sent:</B> Thu 8/23/2007 6:34 PM<BR><B>To:</B>
Scott Voll<BR><B>Cc:</B> cisco voip list<BR><B>Subject:</B> Re: [cisco-voip]
Unity 5 upgrading from Unity 4<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>The Windows issue is the big one I am going to be running
into... most<BR>of the people who want to upgrade is because they want Windows
2000<BR>out of their network (that is why they went to CCM5.1, MPX,
etc...)<BR><BR>A few customers have Unity 4.2(1) on Win2k3, which means the
upgrade<BR>should be easy, but if they are running Win2K, that means a
complete<BR>blow away and start over...<BR><BR>I did one back in July, and it
was a nightmare, we ended up abandoning<BR>the old system and recreating
everything from scratch...<BR><BR><BR>Jonathan<BR><BR>On 8/23/07, Scott Voll
<svoll.voip@gmail.com> wrote:<BR>> I'm planning on this upgrade October
/ Novemberish but have not started the<BR>> research on it yet. If
anyone has any comments I would like to know also.<BR>><BR>> I don't have
the Windows issue as I'm already at windows 2k3 with Exchange<BR>> 2k3 and
Unity 4.0.5 UM. I'm hoping upgrading to 5.0 will be a little
easier<BR>> then Jonathan is talking about.<BR>><BR>>
Scott<BR>><BR>><BR>> On 8/23/07, Jonathan Charles
<jonvoip@gmail.com> wrote:<BR>> ><BR>> > Has anyone done it
successfully?<BR>> ><BR>> > I have a LOT of customers on Unity 4.X
running Windows 2000 who want<BR>> > to upgrade to Unity 5 and Windows
2003. However, my first attempt was<BR>> > a complete disaster (ended up
having to install from scratch).<BR>> ><BR>> > Here is the
problem:<BR>> ><BR>> > You CANNOT upgrade a Windows 2000 box to
Windows 2003 once Unity is<BR>> > installed (says so in the upgrade
documentation).<BR>> ><BR>> > So, you must do a DRT backup, install
Windows 2003 clean, install your<BR>> > old version of Unity 4.X and
restore it. Then you can upgrade to 5<BR>> ><BR>> > This is not even
slightly as simple as it sounds and has a remarkably<BR>> > high failure
rate.<BR>> ><BR>> > (we got an error that the hostname didn't match
and the upgrade to unity<BR>> failed)<BR>> ><BR>> > TAC refused
to support the upgrade (this was early July, it had come<BR>> > off of NPH
that day).<BR>> ><BR>> > If anyone has, I am curious as to what
tricks you did to make it work...<BR>> ><BR>> ><BR>> ><BR>>
> Jonathan<BR>> >
_______________________________________________<BR>> > cisco-voip mailing
list<BR>> > cisco-voip@puck.nether.net<BR>> > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
><BR>><BR>><BR>_______________________________________________<BR>cisco-voip
mailing list<BR>cisco-voip@puck.nether.net<BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></FONT></P></DIV>
</BODY>
</HTML>