<div>
Thanks jcrust and monorail1 !<br />
<br />
There will be three 2010 servers. 1 HT/CAS server and 2 MB servers.<br />
<br />
In this case the &quot;forwarder&quot; is the legacy.domain.com piece correct? &nbsp;I'll report back as I get to that point. We also have BES users so I'm thinking after the routing changes they might need to reactivate their devices?
</div>


<div>
Thanks guys. I have inbound and outbound mail routing through the 2010 server now and also moved over a few test accounts without issues.
</div>


<div>
<div class="content wysiwyg-content">
Experts,<br />
<br />
We have a migration project. Exchange 2003 to 2010. The 2003 setup is funky (at least to me it is).<br />
<br />
&nbsp;2003 side<br />
* OWA is published via ISA 2006<br />
* The Mailbox servers are clustered (windows clustering) and have a smart host configured that routes through an ASA firewall then to an external Barracuda device.<br />
<br />
As I bring up 2010 servers I'm not sure what routing considerations I need to address in order to have them coexist until all mailboxes are moved over. I know once the 2010 ht / cas server comes up it will create a send connector but beyond that i'm stuck.<br />
<br />
Thanks in advance for any help on this one.
</div>
</div>


Experts,

We have a migration project. Exchange 2003 to 2010. The 2003 setup is funky (at least to me it is).

 2003 side
* OWA is published via ISA 2006
* The Mailbox servers are clustered (windows clustering) and have a smart host configured that routes through an ASA firewall then to an external Barracuda device.

As I bring up 2010 servers I'm not sure what routing considerations I need to address in order to have them coexist until all mailboxes are moved over. I know once the 2010 ht / cas server comes up it will create a send connector but beyond that i'm stuck.

Thanks in advance for any help on this one.

Thanks jcrust and monorail1 !

There will be three 2010 servers. 1 HT/CAS server and 2 MB servers.

In this case the &quot;forwarder&quot; is the legacy.domain.com piece correct?  I&#39;ll report back as I get to that point. We also have BES users so I&#39;m thinking after the routing changes they might need to reactivate their devices?

Thanks guys. I have inbound and outbound mail routing through the 2010 server now and also moved over a few test accounts without issues.

Exchange 2003 to 2010 migration routing questions

Experts,

We have a migration project. Exchange 2003 to 2010. The 2003 setup is funky (at least to me it is).

 2003 side
* OWA is published via ISA 2006
* The Mailbox servers are clustered (windows clustering) and have a smart host configured that routes through an ASA firewall then to an external Barracuda device.

As I bring up 2010 servers I&#39;m not sure what routing considerations I need to address in order to have them coexist until all mailboxes are moved over. I know once the 2010 ht / cas server comes up it will create a send connector but beyond that i&#39;m stuck.

Thanks in advance for any help on this one.

Microsoft server applications are those applications developed specifically, but not necessarily exclusively, on the Windows Server platform. In addition to well-known products like SQL Server, Exchange, Internet Information Services (IIS), Microsoft Dynamics, Forefront, Lync and Sharepoint, they include applications like Skype, BizTalk, Hyper-V, Groove and Commerce Server. Server applications are managed with the Microsoft System Center.

Microsoft Server Apps

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.