• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 589
  • Last Modified:

Exchange 2010 - Non Internet Facing CAS in Exchange 2003/2007 Environment

Hi All

I have a bit of a non-standard environment for Exchange 2010 Setup.

Details as follows.

1 x Site with 3 x Exchange 2003 Servers all SP2 (2 Hosting User mail, 1 Hosting business mailboxes/Shared)
1 x DMZ with Exchange 2007 SP3 running CAS (Used for ActiveSync & OWA for user mailboxes only).

We will be migrating the user mailboxes to Office 365 later in the year but I need to replace one of the Exchange 2003 servers (Business mailboxes) with Exchange 2010. However no mailboxes on the Exchange 2010 will ever need to be accessed via OWA or Active Sync..

I have prepared AD and meet all the prerequisites for Exchange 2010.

I have installed 1 x  Exchange 2010 CAS server as non internet facing.

I need to know the following.

1.      Will the Outlook 2003-2010 clients will connect to 2 x Exchange 2003 servers hosting user mailboxes without issue (none so far) ?
2.      Can I leave the Exchange 2007 SP3 CAS in the DMZ until all user mail is moved to the cloud ?
3.      If I can leave the 2007 CAS Server in the DMZ till clients are on the cloud can I hold off on buying a certificate and just use a self signed one?

I will then run up 2 x Exchange 2010 in DAG for business mailboxes and move the certain mailboxes over.

Thanks
0
MediaMon
Asked:
MediaMon
1 Solution
 
CWCertus1Commented:
Are you aware that it is not a supported configuration to have a CAS server in a DMZ? MS only support an Edge server in DMZ. To get CAS functionality in DMZ, they recommend putting ISA (Forefront) into the DMZ and publish OWA (or just puch 443 through to your CAS server on the LAN).

To answer your questions though:-
1. The outlook clients will not move to the new CAS until their mailboxes are on a 2010 server. You may be able to redirect the outlook clients manually or via a new outlook profile but would be difficult setup.
0
 
MediaMonAuthor Commented:
Hi CWC thanks for your reply.

Yes I know its an unsupported DMZ config but it will see us through till we go office 365.

Thanks again

MM
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.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now