<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>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……<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Ken Johnson<br>
Mgr. Network Services,<br>
Information Technology<br>
LeTourneau University<br>
_________________________________<br>
E-mail: kenjohnson@letu.edu<br>
Helpdesk: (903) 233-3500<br>
Phone: (903) 233-3520<br>
Web: </span><span style='color:#1F497D'><a
href="BLOCKED::http://www.letu.edu/infotech/"
title="http://www.letu.edu/infotech/"><span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'>http://www.letu.edu/infotech/</span></a></span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Scott Voll<br>
<b>Sent:</b> Friday, August 24, 2007 11:17 AM<br>
<b>To:</b> Jason Aarons (US)<br>
<b>Cc:</b> Rhodes, Geoff; cisco voip list<br>
<b>Subject:</b> Re: [cisco-voip] Unity 5 upgrading from Unity 4<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>If your running UM and you want Exchange 2007 you have to
upgrade Unity first anyway.... so then you need two people skilled ;-)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Scott<br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span class=gmailquote>On 8/24/07, <b>Jason Aarons (US)</b>
<<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>>
wrote:</span> <o:p></o:p></p>
<p class=MsoNormal>The Exchange 2007 upgrade has it's own caveats, 64-bit
hardware, 64-bit<br>
OS and migration of mailboxes....either way you need someone skilled! <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 Rhodes, Geoff<br>
Sent: Friday, August 24, 2007 11:01 AM<br>
To: cisco voip list<br>
Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4<br>
<br>
Maybe they don't want us going to Unity 5, instead they want to push us <br>
into using Exchange 2007 Unified Messaging... :)<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: Thursday, August 23, 2007 11:18 PM<br>
To: Keith Klevenski<br>
Cc: cisco voip list<br>
Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4 <br>
<br>
That is exactly what I did...<br>
<br>
Then when I went to run the Unity 5 install, it failed saying there was<br>
a hostname mismatch... I called TAC, they had no idea what to do and<br>
said, 'this should work...' and then refused to support it. <br>
<br>
<br>
<br>
Jonathan<br>
<br>
On 8/23/07, Keith Klevenski <<a href="mailto:keith.klevenski@rig.net">keith.klevenski@rig.net</a>>
wrote:<br>
><br>
><br>
><br>
> This does not sound promising as I'm about to embark on the win2k/4.0x <br>
<br>
> to<br>
> win2k3/4.2 to 5.0 myself. I was going to upgrade to to 4.2
first<br>
> (since<br>
> 4.03sr1 isn't supported on win2k3), dirt backup, install fresh win2k3<br>
> install, dirt restore, upgrade to 5.0. This is going to be
ugly...<br>
><br>
> ________________________________<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
on behalf of Jonathan<br>
> Charles <br>
> Sent: Thu 8/23/2007 6:34 PM<br>
> To: Scott Voll<br>
> Cc: cisco voip list<br>
> Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4<br>
><br>
><br>
><br>
><br>
> The Windows issue is the big one I am going to be running into... most <br>
<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>
<br>
> the old system and recreating everything from scratch... <br>
><br>
><br>
> Jonathan<br>
><br>
> On 8/23/07, Scott Voll <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>>
wrote:<br>
> > I'm planning on this upgrade October / Novemberish but have not <br>
> > started<br>
> the<br>
> > research on it yet. If anyone has any comments I would
like to know<br>
also.<br>
> ><br>
> > I don't have the Windows issue as I'm already at windows 2k3 with <br>
> > Exchange<br>
> > 2k3 and Unity 4.0.5 UM. I'm hoping upgrading to 5.0 will
be a<br>
> > little<br>
> easier<br>
> > then Jonathan is talking about.<br>
> ><br>
> > Scott<br>
> > <br>
> ><br>
> > On 8/23/07, Jonathan Charles <<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>>
wrote:<br>
> > ><br>
> > > Has anyone done it successfully?<br>
> > ><br>
> > > I have a LOT of customers on Unity 4.X running Windows 2000 who<br>
> > > want to upgrade to Unity 5 and Windows 2003. However, my first<br>
> > > attempt was a complete disaster (ended up having to install from<br>
scratch).<br>
> > > <br>
> > > Here is the problem:<br>
> > ><br>
> > > You CANNOT upgrade a Windows 2000 box to Windows 2003 once Unity<br>
> > > is installed (says so in the upgrade documentation).<br>
> > > <br>
> > > So, you must do a DRT backup, install Windows 2003 clean,
install<br>
> > > your old version of Unity 4.X and restore it. Then you can
upgrade<br>
<br>
> > > to 5<br>
> > ><br>
> > > This is not even slightly as simple as it sounds and has a <br>
> > > remarkably high failure rate.<br>
> > ><br>
> > > (we got an error that the hostname didn't match and the upgrade
to<br>
<br>
> > > unity<br>
> > failed)<br>
> > > <br>
> > > TAC refused to support the upgrade (this was early July, it had<br>
> > > come off of NPH that day).<br>
> > ><br>
> > > If anyone has, I am curious as to what tricks you did to make it
<br>
work...<br>
> > ><br>
> > ><br>
> > ><br>
> > > Jonathan<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">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">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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
-----------------------------------------<br>
Disclaimer:<br>
<br>
This e-mail communication and any attachments may contain<br>
confidential and privileged information and is for use by the <br>
designated addressee(s) named above only. If you are not the<br>
intended addressee, you are hereby notified that you have received<br>
this communication in error and that any use or reproduction of<br>
this email or its contents is strictly prohibited and may be <br>
unlawful. If you have received this communication in error, please<br>
notify us immediately by replying to this message and deleting it<br>
from your computer. Thank you.<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">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:13.5pt;color:black;background:white'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:13.5pt;color:black;background:white'><br>
<a href="http://antispam.letu.edu/canit/b.php?i=6286216&m=676f7f24d262&c=s">Spam</a><br>
<a href="http://antispam.letu.edu/canit/b.php?i=6286216&m=676f7f24d262&c=n">Not
spam</a><br>
<a href="http://antispam.letu.edu/canit/b.php?i=6286216&m=676f7f24d262&c=f">Forget
previous vote</a></span><o:p></o:p></p>
</div>
</div>
</body>
</html>