|
Home > Archive > Voice over IP Cisco > August 2007 > Unity 5 upgrading from Unity 4
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Unity 5 upgrading from Unity 4
|
|
| Jonathan Charles 2007-08-23, 7:11 pm |
| 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
| |
| Jason Aarons \(US\) 2007-08-23, 7:11 pm |
| 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-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.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-voip@puck.nether.net
https://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.
| |
| Scott Voll 2007-08-23, 7:11 pm |
| 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 <jonvoip@gmail.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-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Jonathan Charles 2007-08-23, 7:11 pm |
| 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.voip@gmail.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 <jonvoip@gmail.com> wrote:
> failed)
>
>
| |
| Keith Klevenski 2007-08-24, 1:11 am |
| 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-bounces@puck.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.voip@gmail.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 <jonvoip@gmail.com> wrote:
> failed)
>
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Jonathan Charles 2007-08-24, 1:11 am |
| 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.klevenski@rig.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-bounces@puck.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.voip@gmail.com> wrote:
> the
> easier
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Rhodes, Geoff 2007-08-24, 1:11 pm |
| < 5d093f9a0708232018o57d506f0ie2438467c66c
ab7f@mail.gmail.com>
NNTP-Posting-Host: lo.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Trace: sea.gmane.org 1187967752 23548 80.91.229.12 (24 Aug 2007 15:02:32 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Fri, 24 Aug 2007 15:02:32 +0000 (UTC)
To: "cisco voip list" <cisco-voip@puck.nether.net>
Original-X-From: cisco-voip-bounces@puck.nether.net Fri Aug 24 17:02:29 2007
Return-path: <cisco-voip-bounces@puck.nether.net>
Envelope-to: gcvc-cisco-voip@gmane.org
Original-Received: from puck.nether.net ([204.42.254.5])
by lo.gmane.org with esmtp (Exim 4.50)
id 1IOag6-0002pI-UR
for gcvc-cisco-voip@gmane.org; Fri, 24 Aug 2007 17:02:27 +0200
Original-Received: from puck.nether.net (puck.nether.net [204.42.254.5])
by puck.nether.net (8.14.1/8.12.9) with ESMTP id l7OF0hCi016122;
Fri, 24 Aug 2007 11:01:08 -0400 (EDT)
(envelope-from cisco-voip-bounces@puck.nether.net)
Original-Received: from mta2.rbh.com (mta2.rbh.com [64.132.107.15])
by puck.nether.net (8.14.1/8.12.9) with ESMTP id l7OF0eU2016106
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <cisco-voip@puck.nether.net>; Fri, 24 Aug 2007 11:00:41 -0400 (EDT)
(envelope-from GRhodes@rbh.com)
X-Envelope-From: GRhodes@rbh.com
Original-Received: from apollo.rbh.local (apollo.rbh.local [10.1.19.64])
by mta2.rbh.com (Postfix) with ESMTP id 3F02D559D6
for <cisco-voip@puck.nether.net>; Fri, 24 Aug 2007 11:00:35 -0400 (EDT)
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5
In-Reply-To: < 5d093f9a0708232018o57d506f0ie2438467c66c
ab7f@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [cisco-voip] Unity 5 upgrading from Unity 4
Thread-Index: Acfl/aQ/sZl1MljeQWSYrzzR8G5CBQAYausQ
X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-4.0a6 (puck.nether.net [204.42.254.5]); Fri, 24 Aug 2007 11:01:10 -0400 (EDT)
X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-4.0a6
(puck.nether.net [204.42.254.5]);
Fri, 24 Aug 2007 11:00:41 -0400 (EDT)
X-BeenThere: cisco-voip@puck.nether.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: cisco VoIP list <cisco-voip.puck.nether.net>
List-Unsubscribe: <https://puck.nether.net/mailman/listinfo/cisco-voip>,
<mailto:cisco-voip-request@puck.nether.net?subject=unsubscribe>
List-Archive: <https://puck.nether.net/pipermail/cisco-voip>
List-Post: <mailto:cisco-voip@puck.nether.net>
List-Help: <mailto:cisco-voip-request@puck.nether.net?subject=help>
List-Subscribe: <https://puck.nether.net/mailman/listinfo/cisco-voip>,
<mailto:cisco-voip-request@puck.nether.net?subject=subscribe>
Original-Sender: cisco-voip-bounces@puck.nether.net
Errors-To: cisco-voip-bounces@puck.nether.net
Xref: news.gmane.org gmane.comp.voip.cisco:20459
Archived-At: <http://permalink.gmane.org/gmane.comp.voip.cisco/20459>
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-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.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.klevenski@rig.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-bounces@puck.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.voip@gmail.com> wrote:
> the
also.[vbcol=seagreen]
> easier
scratch).[vbcol=seagreen]
[vbcol=seagreen]
[vbcol=seagreen]
work...[vbcol=seagreen]
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Keith Klevenski 2007-08-24, 1:11 pm |
| Nice. :c|
Keith Klevenski
IP Telephony Engineer
RigNet Inc.
1880 S. Dairy Ashford
Suite 300
Houston, TX 77077=A0=A0=A0=A0=A0=A0=A0=A0 =
Office: =A0 +1 281.674.0702
Mobile:=A0 +1 713.677.3925
http://www.rig.net
"Extending the power of your knowledge"
-----Original Message-----
From: Jonathan Charles [mailto:jonvoip@gmail.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.klevenski@rig.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-bounces@puck.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.voip@gmail.com> wrote:
> the
so.[vbcol=seagreen]
nge[vbcol=seagreen]
> easier
ity[vbcol=seagreen]
....[vbcol=seagreen]
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Jason Aarons \(US\) 2007-08-24, 1:11 pm |
| 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-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.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-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.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.klevenski@rig.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-bounces@puck.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.voip@gmail.com> wrote:
> the
also.[vbcol=seagreen]
> easier
scratch).[vbcol=seagreen]
[vbcol=seagreen]
[vbcol=seagreen]
work...[vbcol=seagreen]
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://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.
| |
| Scott Voll 2007-08-24, 7:12 pm |
| If your running UM and you want Exchange 2007 you have to upgrade Unity
first anyway.... so then you need two people skilled ;-)
Scott
On 8/24/07, Jason Aarons (US) <jason.aarons@us.didata.com> wrote:
>
> 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-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.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-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.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.klevenski@rig.net> wrote:
>
>
>
> also.
> scratch).
>
>
> work...
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://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-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Johnson, Ken 2007-08-29, 1:11 pm |
| I sadly am stuck on 2k for our 5.x move unless support for the Dialogic
cards has materialized on 2003 and I'm just out of the loop - I'm
assuming that things haven't changed since the last time I looked at the
docs unless 5.x includes some proprietary 2k3 drivers but since my
understanding was those were largely OS-level drivers from Intel I'm
assuming if they were available they'd be available to all versions of
Unity......
Ken Johnson
Mgr. Network Services,
Information Technology
LeTourneau University
_________________________________
E-mail: kenjohnson@letu.edu
Helpdesk: (903) 233-3500
Phone: (903) 233-3520
Web: http://www.letu.edu/infotech/
<BLOCKED::http://www.letu.edu/infotech/>
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Scott Voll
Sent: Friday, August 24, 2007 11:17 AM
To: Jason Aarons (US)
Cc: Rhodes, Geoff; cisco voip list
Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4
If your running UM and you want Exchange 2007 you have to upgrade Unity
first anyway.... so then you need two people skilled ;-)
Scott
On 8/24/07, Jason Aarons (US) <jason.aarons@us.didata.com> wrote:
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-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.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-bounces@puck.nether.net
[mailto: cisco-voip-bounces@puck.nether.net
<mailto:cisco-voip-bounces@puck.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.klevenski@rig.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-bounces@puck.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.voip@gmail.com> wrote:
> the
also.[vbcol=seagreen]
> easier
scratch).[vbcol=seagreen]
[vbcol=seagreen]
[vbcol=seagreen]
work...[vbcol=seagreen]
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://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-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________
Spam <http://antispam.letu.edu/canit/b.ph...76f7f24d262&c=s>
Not spam
<http://antispam.letu.edu/canit/b.ph...76f7f24d262&c=n>
Forget previous vote
<http://antispam.letu.edu/canit/b.ph...76f7f24d262&c=f>
| |
| Robert Kulagowski 2007-08-29, 1:11 pm |
| Johnson, Ken wrote:
> I sadly am stuck on 2k for our 5.x move unless support for the Dialogic =
> cards has materialized on 2003 and I=92m just out of the loop =96 I=92m =
> assuming that things haven=92t changed since the last time I looked at th=
e =
> docs unless 5.x includes some proprietary 2k3 drivers but since my =
> understanding was those were largely OS-level drivers from Intel I=92m =
> assuming if they were available they=92d be available to all versions of =
> Unity=85=85
I'm assuming that you're talking about the dialogic terminating PRIs; =
can you use an external gateway (2821 / 2851) to terminate the PRIs and =
convert to IP / RTP at that point?
| |
| Johnson, Ken 2007-08-29, 7:11 pm |
| No - I wish it was a PRI but they stopped support for purchasing the PRI
cards (as far as I could tell) before we upgraded our hardware last year
- it's still on pots lines into a Dialogic D/120JCT-LS.
(This is a split system with unity serving the administrative
callmanager cluster and our legacy NEAX serving our residence halls.
I don't know that I'd ever considered converting those lines in an
external gateway - admittedly we haven't revisited the preferred method
for connecting legacy systems to Unity since we originally deployed in
2001 :-/ I might need to read up more on non-Dialogic options for
pulling that off it sounds like and move to something a little more
standard :-)
Ken Johnson
Mgr. Network Services,
Information Technology
LeTourneau University
_________________________________
E-mail: kenjohnson@letu.edu
Helpdesk: (903) 233-3500
Phone: (903) 233-3520
Web: http://www.letu.edu/infotech/
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Robert
Kulagowski
Sent: Wednesday, August 29, 2007 10:08 AM
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4
Johnson, Ken wrote:
> I sadly am stuck on 2k for our 5.x move unless support for the
Dialogic
> cards has materialized on 2003 and I'm just out of the loop - I'm
> assuming that things haven't changed since the last time I looked at
the
> docs unless 5.x includes some proprietary 2k3 drivers but since my
> understanding was those were largely OS-level drivers from Intel I'm
> assuming if they were available they'd be available to all versions of
> Unity......
I'm assuming that you're talking about the dialogic terminating PRIs;
can you use an external gateway (2821 / 2851) to terminate the PRIs and
convert to IP / RTP at that point?
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach CanIt if this mail (ID 6458245) is spam:
Spam:
http://antispam.letu.edu/canit/b.ph...1fe11bb1b6a&c=s
Not spam:
http://antispam.letu.edu/canit/b.ph...1fe11bb1b6a&c=n
Forget vote:
http://antispam.letu.edu/canit/b.ph...1fe11bb1b6a&c=f
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS
|
|
|
|
|