Unity 5 upgrading from Unity 4

Has anyone done it successfully?

I have a LOT of customers on Unity 4.X running Windows 2000
who want
to upgrade to Unity 5 and Windows 2003. However, my first
attempt was
a complete disaster (ended up having to install from
scratch).

Here is the problem:

You CANNOT upgrade a Windows 2000 box to Windows 2003 once
Unity is
installed (says so in the upgrade documentation).

So, you must do a DRT backup, install Windows 2003 clean,
install your
old version of Unity 4.X and restore it. Then you can
upgrade to 5

This is not even slightly as simple as it sounds and has a
remarkably
high failure rate.

(we got an error that the hostname didn't match and the
upgrade to unity failed)

TAC refused to support the upgrade (this was early July, it
had come
off of NPH that day).

If anyone has, I am curious as to what tricks you did to
make it work...



Jonathan
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

Most of my Unity 4.2 are running 2003 Server they provided,
I wonder if
that will present any issues -jason

-----Original Message-----
From: cisco-voip-bouncespuck.nether.net
[mailto:cisco-voip-bouncespuck.nether.net] On Behalf
Of Jonathan
Charles
Sent: Thursday, August 23, 2007 6:10 PM
To: cisco voip list
Subject: [cisco-voip] Unity 5 upgrading from Unity 4

Has anyone done it successfully?

I have a LOT of customers on Unity 4.X running Windows 2000
who want
to upgrade to Unity 5 and Windows 2003. However, my first
attempt was
a complete disaster (ended up having to install from
scratch).

Here is the problem:

You CANNOT upgrade a Windows 2000 box to Windows 2003 once
Unity is
installed (says so in the upgrade documentation).

So, you must do a DRT backup, install Windows 2003 clean,
install your
old version of Unity 4.X and restore it. Then you can
upgrade to 5

This is not even slightly as simple as it sounds and has a
remarkably
high failure rate.

(we got an error that the hostname didn't match and the
upgrade to unity
failed)

TAC refused to support the upgrade (this was early July, it
had come
off of NPH that day).

If anyone has, I am curious as to what tricks you did to
make it work...



Jonathan
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by
the
designated addressee(s) named above only.  If you are not
the
intended addressee, you are hereby notified that you have
received
this communication in error and that any use or reproduction
of
this email or its contents is strictly prohibited and may
be
unlawful.  If you have received this communication in error,
please
notify us immediately by replying to this message and
deleting it
from your computer. Thank you.
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

The Windows issue is the big one I am going to be running
into... most
of the people who want to upgrade is because they want
Windows 2000
out of their network (that is why they went to CCM5.1, MPX,
etc...)

A few customers have Unity 4.2(1) on Win2k3, which means the
upgrade
should be easy, but if they are running Win2K, that means a
complete
blow away and start over...

I did one back in July, and it was a nightmare, we ended up
abandoning
the old system and recreating everything from scratch...


Jonathan

On 8/23/07, Scott Voll <svoll.voipgmail.com> wrote:
> I'm planning on this upgrade October / Novemberish but
have not started the
> research on it yet.  If anyone has any comments I would
like to know also.
>
> I don't have the Windows issue as I'm already at
windows 2k3 with Exchange
> 2k3 and Unity 4.0.5 UM.  I'm hoping upgrading to 5.0
will be a little easier
> then Jonathan is talking about.
>
> Scott
>
>
> On 8/23/07, Jonathan Charles <jonvoipgmail.com> wrote:
> >
> > Has anyone done it successfully?
> >
> > I have a LOT of customers on Unity 4.X running
Windows 2000 who want
> > to upgrade to Unity 5 and Windows 2003. However,
my first attempt was
> > a complete disaster (ended up having to install
from scratch).
> >
> > Here is the problem:
> >
> > You CANNOT upgrade a Windows 2000 box to Windows
2003 once Unity is
> > installed (says so in the upgrade documentation).
> >
> > So, you must do a DRT backup, install Windows 2003
clean, install your
> > old version of Unity 4.X and restore it. Then you
can upgrade to 5
> >
> > This is not even slightly as simple as it sounds
and has a remarkably
> > high failure rate.
> >
> > (we got an error that the hostname didn't match
and the upgrade to unity
> failed)
> >
> > TAC refused to support the upgrade (this was early
July, it had come
> > off of NPH that day).
> >
> > If anyone has, I am curious as to what tricks you
did to make it work...
> >
> >
> >
> > Jonathan
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voippuck.nether.net
> > h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

That is exactly what I did...

Then when I went to run the Unity 5 install, it failed
saying there
was a hostname mismatch... I called TAC, they had no idea
what to do
and said, 'this should work...' and then refused to support
it.



Jonathan

On 8/23/07, Keith Klevenski <keith.klevenskirig.net> wrote:
>
>
>
> 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...
>
>  ________________________________
>  From: cisco-voip-bouncespuck.nether.net on behalf
of
> Jonathan Charles
> Sent: Thu 8/23/2007 6:34 PM
> To: Scott Voll
> Cc: cisco voip list
> Subject: Re: [cisco-voip] Unity 5 upgrading from Unity
4
>
>
>
>
> The Windows issue is the big one I am going to be
running into... most
> of the people who want to upgrade is because they want
Windows 2000
> out of their network (that is why they went to CCM5.1,
MPX, etc...)
>
> A few customers have Unity 4.2(1) on Win2k3, which
means the upgrade
> should be easy, but if they are running Win2K, that
means a complete
> blow away and start over...
>
> I did one back in July, and it was a nightmare, we
ended up abandoning
> the old system and recreating everything from
scratch...
>
>
> Jonathan
>
> On 8/23/07, Scott Voll <svoll.voipgmail.com> wrote:
> > I'm planning on this upgrade October / Novemberish
but have not started
> the
> > research on it yet.  If anyone has any comments I
would like to know also.
> >
> > I don't have the Windows issue as I'm already at
windows 2k3 with Exchange
> > 2k3 and Unity 4.0.5 UM.  I'm hoping upgrading to
5.0 will be a little
> easier
> > then Jonathan is talking about.
> >
> > Scott
> >
> >
> > On 8/23/07, Jonathan Charles <jonvoipgmail.com> wrote:
> > >
> > > Has anyone done it successfully?
> > >
> > > I have a LOT of customers on Unity 4.X
running Windows 2000 who want
> > > to upgrade to Unity 5 and Windows 2003.
However, my first attempt was
> > > a complete disaster (ended up having to
install from scratch).
> > >
> > > Here is the problem:
> > >
> > > You CANNOT upgrade a Windows 2000 box to
Windows 2003 once Unity is
> > > installed (says so in the upgrade
documentation).
> > >
> > > So, you must do a DRT backup, install Windows
2003 clean, install your
> > > old version of Unity 4.X and restore it. Then
you can upgrade to 5
> > >
> > > This is not even slightly as simple as it
sounds and has a remarkably
> > > high failure rate.
> > >
> > > (we got an error that the hostname didn't
match and the upgrade to unity
> > failed)
> > >
> > > TAC refused to support the upgrade (this was
early July, it had come
> > > off of NPH that day).
> > >
> > > If anyone has, I am curious as to what tricks
you did to make it work...
> > >
> > >
> > >
> > > Jonathan
> > >
_______________________________________________
> > > cisco-voip mailing list
> > > cisco-voippuck.nether.net
> > > h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> >
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

Maybe they don't want us going to Unity 5, instead they want
to push us
into using Exchange 2007 Unified Messaging...  


-----Original Message-----
From: cisco-voip-bouncespuck.nether.net
[mailto:cisco-voip-bouncespuck.nether.net] On Behalf
Of Jonathan
Charles
Sent: Thursday, August 23, 2007 11:18 PM
To: Keith Klevenski
Cc: cisco voip list
Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4

That is exactly what I did...

Then when I went to run the Unity 5 install, it failed
saying there was
a hostname mismatch... I called TAC, they had no idea what
to do and
said, 'this should work...' and then refused to support it.



Jonathan

On 8/23/07, Keith Klevenski <keith.klevenskirig.net> wrote:
>
>
>
> 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...
>
>  ________________________________
>  From: cisco-voip-bouncespuck.nether.net on behalf
of Jonathan 
> Charles
> Sent: Thu 8/23/2007 6:34 PM
> To: Scott Voll
> Cc: cisco voip list
> Subject: Re: [cisco-voip] Unity 5 upgrading from Unity
4
>
>
>
>
> The Windows issue is the big one I am going to be
running into... most

> of the people who want to upgrade is because they want
Windows 2000 
> out of their network (that is why they went to CCM5.1,
MPX, etc...)
>
> A few customers have Unity 4.2(1) on Win2k3, which
means the upgrade 
> should be easy, but if they are running Win2K, that
means a complete 
> blow away and start over...
>
> I did one back in July, and it was a nightmare, we
ended up abandoning

> the old system and recreating everything from
scratch...
>
>
> Jonathan
>
> On 8/23/07, Scott Voll <svoll.voipgmail.com> wrote:
> > I'm planning on this upgrade October / Novemberish
but have not 
> > started
> the
> > research on it yet.  If anyone has any comments I
would like to know
also.
> >
> > I don't have the Windows issue as I'm already at
windows 2k3 with 
> > Exchange
> > 2k3 and Unity 4.0.5 UM.  I'm hoping upgrading to
5.0 will be a 
> > little
> easier
> > then Jonathan is talking about.
> >
> > Scott
> >
> >
> > On 8/23/07, Jonathan Charles <jonvoipgmail.com> wrote:
> > >
> > > Has anyone done it successfully?
> > >
> > > I have a LOT of customers on Unity 4.X
running Windows 2000 who 
> > > want to upgrade to Unity 5 and Windows 2003.
However, my first 
> > > attempt was a complete disaster (ended up
having to install from
scratch).
> > >
> > > Here is the problem:
> > >
> > > You CANNOT upgrade a Windows 2000 box to
Windows 2003 once Unity 
> > > is installed (says so in the upgrade
documentation).
> > >
> > > So, you must do a DRT backup, install Windows
2003 clean, install 
> > > your old version of Unity 4.X and restore it.
Then you can upgrade

> > > to 5
> > >
> > > This is not even slightly as simple as it
sounds and has a 
> > > remarkably high failure rate.
> > >
> > > (we got an error that the hostname didn't
match and the upgrade to

> > > unity
> > failed)
> > >
> > > TAC refused to support the upgrade (this was
early July, it had 
> > > come off of NPH that day).
> > >
> > > If anyone has, I am curious as to what tricks
you did to make it
work...
> > >
> > >
> > >
> > > Jonathan
> > >
_______________________________________________
> > > cisco-voip mailing list
> > > cisco-voippuck.nether.net
> > > h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> >
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

Nice.  :c|

Keith Klevenski
IP Telephony Engineer
RigNet Inc.
1880 S. Dairy Ashford
Suite 300
Houston, TX 77077         
Office:   +1 281.674.0702
Mobile:  +1 713.677.3925
http://www.rig.net

"Extending the power of your knowledge"


-----Original Message-----
From: Jonathan Charles [mailto:jonvoipgmail.com] 
Sent: Thursday, August 23, 2007 10:18 PM
To: Keith Klevenski
Cc: Scott Voll; cisco voip list
Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4

That is exactly what I did...

Then when I went to run the Unity 5 install, it failed
saying there
was a hostname mismatch... I called TAC, they had no idea
what to do
and said, 'this should work...' and then refused to support
it.



Jonathan

On 8/23/07, Keith Klevenski <keith.klevenskirig.net> wrote:
>
>
>
> 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...
>
>  ________________________________
>  From: cisco-voip-bouncespuck.nether.net on behalf
of
> Jonathan Charles
> Sent: Thu 8/23/2007 6:34 PM
> To: Scott Voll
> Cc: cisco voip list
> Subject: Re: [cisco-voip] Unity 5 upgrading from Unity
4
>
>
>
>
> The Windows issue is the big one I am going to be
running into... most
> of the people who want to upgrade is because they want
Windows 2000
> out of their network (that is why they went to CCM5.1,
MPX, etc...)
>
> A few customers have Unity 4.2(1) on Win2k3, which
means the upgrade
> should be easy, but if they are running Win2K, that
means a complete
> blow away and start over...
>
> I did one back in July, and it was a nightmare, we
ended up abandoning
> the old system and recreating everything from
scratch...
>
>
> Jonathan
>
> On 8/23/07, Scott Voll <svoll.voipgmail.com> wrote:
> > I'm planning on this upgrade October / Novemberish
but have not started
> the
> > research on it yet.  If anyone has any comments I
would like to know also.
> >
> > I don't have the Windows issue as I'm already at
windows 2k3 with Exchange
> > 2k3 and Unity 4.0.5 UM.  I'm hoping upgrading to
5.0 will be a little
> easier
> > then Jonathan is talking about.
> >
> > Scott
> >
> >
> > On 8/23/07, Jonathan Charles <jonvoipgmail.com> wrote:
> > >
> > > Has anyone done it successfully?
> > >
> > > I have a LOT of customers on Unity 4.X
running Windows 2000 who want
> > > to upgrade to Unity 5 and Windows 2003.
However, my first attempt was
> > > a complete disaster (ended up having to
install from scratch).
> > >
> > > Here is the problem:
> > >
> > > You CANNOT upgrade a Windows 2000 box to
Windows 2003 once Unity is
> > > installed (says so in the upgrade
documentation).
> > >
> > > So, you must do a DRT backup, install Windows
2003 clean, install your
> > > old version of Unity 4.X and restore it. Then
you can upgrade to 5
> > >
> > > This is not even slightly as simple as it
sounds and has a remarkably
> > > high failure rate.
> > >
> > > (we got an error that the hostname didn't
match and the upgrade to unity
> > failed)
> > >
> > > TAC refused to support the upgrade (this was
early July, it had come
> > > off of NPH that day).
> > >
> > > If anyone has, I am curious as to what tricks
you did to make it work...
> > >
> > >
> > >
> > > Jonathan
> > >
_______________________________________________
> > > cisco-voip mailing list
> > > cisco-voippuck.nether.net
> > > h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> >
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

The Exchange 2007 upgrade has it's own caveats, 64-bit
hardware, 64-bit
OS and migration of mailboxes....either way you need someone
skilled!

-----Original Message-----
From: cisco-voip-bouncespuck.nether.net
[mailto:cisco-voip-bouncespuck.nether.net] On Behalf
Of Rhodes, Geoff
Sent: Friday, August 24, 2007 11:01 AM
To: cisco voip list
Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4

Maybe they don't want us going to Unity 5, instead they want
to push us
into using Exchange 2007 Unified Messaging...  


-----Original Message-----
From: cisco-voip-bouncespuck.nether.net
[mailto:cisco-voip-bouncespuck.nether.net] On Behalf
Of Jonathan
Charles
Sent: Thursday, August 23, 2007 11:18 PM
To: Keith Klevenski
Cc: cisco voip list
Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4

That is exactly what I did...

Then when I went to run the Unity 5 install, it failed
saying there was
a hostname mismatch... I called TAC, they had no idea what
to do and
said, 'this should work...' and then refused to support it.



Jonathan

On 8/23/07, Keith Klevenski <keith.klevenskirig.net> wrote:
>
>
>
> 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...
>
>  ________________________________
>  From: cisco-voip-bouncespuck.nether.net on behalf
of Jonathan 
> Charles
> Sent: Thu 8/23/2007 6:34 PM
> To: Scott Voll
> Cc: cisco voip list
> Subject: Re: [cisco-voip] Unity 5 upgrading from Unity
4
>
>
>
>
> The Windows issue is the big one I am going to be
running into... most

> of the people who want to upgrade is because they want
Windows 2000 
> out of their network (that is why they went to CCM5.1,
MPX, etc...)
>
> A few customers have Unity 4.2(1) on Win2k3, which
means the upgrade 
> should be easy, but if they are running Win2K, that
means a complete 
> blow away and start over...
>
> I did one back in July, and it was a nightmare, we
ended up abandoning

> the old system and recreating everything from
scratch...
>
>
> Jonathan
>
> On 8/23/07, Scott Voll <svoll.voipgmail.com> wrote:
> > I'm planning on this upgrade October / Novemberish
but have not 
> > started
> the
> > research on it yet.  If anyone has any comments I
would like to know
also.
> >
> > I don't have the Windows issue as I'm already at
windows 2k3 with 
> > Exchange
> > 2k3 and Unity 4.0.5 UM.  I'm hoping upgrading to
5.0 will be a 
> > little
> easier
> > then Jonathan is talking about.
> >
> > Scott
> >
> >
> > On 8/23/07, Jonathan Charles <jonvoipgmail.com> wrote:
> > >
> > > Has anyone done it successfully?
> > >
> > > I have a LOT of customers on Unity 4.X
running Windows 2000 who 
> > > want to upgrade to Unity 5 and Windows 2003.
However, my first 
> > > attempt was a complete disaster (ended up
having to install from
scratch).
> > >
> > > Here is the problem:
> > >
> > > You CANNOT upgrade a Windows 2000 box to
Windows 2003 once Unity 
> > > is installed (says so in the upgrade
documentation).
> > >
> > > So, you must do a DRT backup, install Windows
2003 clean, install 
> > > your old version of Unity 4.X and restore it.
Then you can upgrade

> > > to 5
> > >
> > > This is not even slightly as simple as it
sounds and has a 
> > > remarkably high failure rate.
> > >
> > > (we got an error that the hostname didn't
match and the upgrade to

> > > unity
> > failed)
> > >
> > > TAC refused to support the upgrade (this was
early July, it had 
> > > come off of NPH that day).
> > >
> > > If anyone has, I am curious as to what tricks
you did to make it
work...
> > >
> > >
> > >
> > > Jonathan
> > >
_______________________________________________
> > > cisco-voip mailing list
> > > cisco-voippuck.nether.net
> > > h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> >
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by
the
designated addressee(s) named above only.  If you are not
the
intended addressee, you are hereby notified that you have
received
this communication in error and that any use or reproduction
of
this email or its contents is strictly prohibited and may
be
unlawful.  If you have received this communication in error,
please
notify us immediately by replying to this message and
deleting it
from your computer. Thank you.
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip