<div>If your running UM and you want Exchange 2007 you have to upgrade Unity first anyway.... so then you need two people skilled ;-)</div>
<div>&nbsp;</div>
<div>Scott<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 8/24/07, <b class="gmail_sendername">Jason Aarons (US)</b> &lt;<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">The Exchange 2007 upgrade has it&#39;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&#39;t want us going to Unity 5, instead they want to push us
<br>into using Exchange 2007 Unified Messaging...&nbsp;&nbsp;:)<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, &#39;this should work...&#39; and then refused to support it.
<br><br><br><br>Jonathan<br><br>On 8/23/07, Keith Klevenski &lt;<a href="mailto:keith.klevenski@rig.net">keith.klevenski@rig.net</a>&gt; wrote:<br>&gt;<br>&gt;<br>&gt;<br>&gt; This does not sound promising as I&#39;m about to embark on the win2k/4.0x
<br><br>&gt; to<br>&gt; win2k3/4.2 to 5.0 myself.&nbsp;&nbsp;I was going to upgrade to to 4.2 first<br>&gt; (since<br>&gt; 4.03sr1 isn&#39;t supported on win2k3), dirt backup, install fresh win2k3<br>&gt; install, dirt restore, upgrade to 
5.0.&nbsp;&nbsp;This is going to be ugly...<br>&gt;<br>&gt;&nbsp;&nbsp;________________________________<br>&gt;&nbsp;&nbsp;From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> on behalf of Jonathan<br>&gt; Charles
<br>&gt; Sent: Thu 8/23/2007 6:34 PM<br>&gt; To: Scott Voll<br>&gt; Cc: cisco voip list<br>&gt; Subject: Re: [cisco-voip] Unity 5 upgrading from Unity 4<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; The Windows issue is the big one I am going to be running into... most
<br><br>&gt; of the people who want to upgrade is because they want Windows 2000<br>&gt; out of their network (that is why they went to CCM5.1, MPX, etc...)<br>&gt;<br>&gt; A few customers have Unity 4.2(1) on Win2k3, which means the upgrade
<br>&gt; should be easy, but if they are running Win2K, that means a complete<br>&gt; blow away and start over...<br>&gt;<br>&gt; I did one back in July, and it was a nightmare, we ended up abandoning<br><br>&gt; the old system and recreating everything from scratch...
<br>&gt;<br>&gt;<br>&gt; Jonathan<br>&gt;<br>&gt; On 8/23/07, Scott Voll &lt;<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>&gt; wrote:<br>&gt; &gt; I&#39;m planning on this upgrade October / Novemberish but have not
<br>&gt; &gt; started<br>&gt; the<br>&gt; &gt; research on it yet.&nbsp;&nbsp;If anyone has any comments I would like to know<br>also.<br>&gt; &gt;<br>&gt; &gt; I don&#39;t have the Windows issue as I&#39;m already at windows 2k3 with
<br>&gt; &gt; Exchange<br>&gt; &gt; 2k3 and Unity 4.0.5 UM.&nbsp;&nbsp;I&#39;m hoping upgrading to 5.0 will be a<br>&gt; &gt; little<br>&gt; easier<br>&gt; &gt; then Jonathan is talking about.<br>&gt; &gt;<br>&gt; &gt; Scott<br>&gt; &gt;
<br>&gt; &gt;<br>&gt; &gt; On 8/23/07, Jonathan Charles &lt;<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>&gt; wrote:<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; Has anyone done it successfully?<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; I have a LOT of customers on Unity 
4.X running Windows 2000 who<br>&gt; &gt; &gt; want to upgrade to Unity 5 and Windows 2003. However, my first<br>&gt; &gt; &gt; attempt was a complete disaster (ended up having to install from<br>scratch).<br>&gt; &gt; &gt;
<br>&gt; &gt; &gt; Here is the problem:<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; You CANNOT upgrade a Windows 2000 box to Windows 2003 once Unity<br>&gt; &gt; &gt; is installed (says so in the upgrade documentation).<br>&gt; &gt; &gt;
<br>&gt; &gt; &gt; So, you must do a DRT backup, install Windows 2003 clean, install<br>&gt; &gt; &gt; your old version of Unity 4.X and restore it. Then you can upgrade<br><br>&gt; &gt; &gt; to 5<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; This is not even slightly as simple as it sounds and has a
<br>&gt; &gt; &gt; remarkably high failure rate.<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; (we got an error that the hostname didn&#39;t match and the upgrade to<br><br>&gt; &gt; &gt; unity<br>&gt; &gt; failed)<br>&gt; &gt; &gt;
<br>&gt; &gt; &gt; TAC refused to support the upgrade (this was early July, it had<br>&gt; &gt; &gt; come off of NPH that day).<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; If anyone has, I am curious as to what tricks you did to make it
<br>work...<br>&gt; &gt; &gt;<br>&gt; &gt; &gt;<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; Jonathan<br>&gt; &gt; &gt; _______________________________________________<br>&gt; &gt; &gt; cisco-voip mailing list<br>&gt; &gt; &gt; <a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a><br>&gt; &gt; &gt; <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>&gt; &gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt; _______________________________________________
<br>&gt; cisco-voip mailing list<br>&gt; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>&gt; <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>&gt;<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.&nbsp;&nbsp;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.&nbsp;&nbsp;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><br></blockquote></div><br>