Exchange 2013 Deployment Question

We are upgrading from Exchange 2007 to 2013.  On the new DDeployment, we want to have Outlook Clients connect to an Internal Client Access server but have mobile devices and OWA clients connect through an External Client Access Server.  The reason for this is that we would like to keep the internal outlook traffic from unnecessarily going through our firewall.  Below is the configuration that we are planning:

Server 1:
Client Access and Mailbox Roles - Physical Server
This server will process traffic from Outlook Clients internally.  

Server 2:
Client Access Role - Virtual Server
We want this server to process traffic from OWA and Mobile Devices.  

Is this possible?  If so, what will we need to do to make this work.
netmaster3620Asked:
Who is Participating?
 
Simon Butler (Sembee)ConsultantCommented:
It will work, although I would probably use two different name spaces.
However the external name space will need to resolve internally as well via split dns.

Thus:

mail.example.com
internal.example.com

etc

Although your reason for doing so is flawed - with split DNS you can have internal traffic going straight to an internal server, not going through the firewall at all. Split DNS is pretty much mandatory with Exchange 2013 because you cannot put internal names on the public SSL certificate.

Simon.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.