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

Exchange 2010 configuration quesation

My question is this.  I am beginning my upgrade from Exchange 2003 to Exchange 2010.  Currently our 2003 configuration is a front-end/back-end setup with the the front-end server hosting OWA access.  I know that Microsoft does not support the CAS server being in the DMZ and they want you to use a proxy such as ISA or TMG.  My boss, however, is pushing me to put the CAs server in the DMZ anyway.  Our firewall can open ports by application and we won't have to open a bunch of random ports just tell it to let active directory access from the CAS server to the inside.  I don't want to do this so I need some data to support not putting the CAS server in the DMZ.  Besides the fact that it's unsupported and Microsoft won't help if we ever need to call them.
0
UMPH_User
Asked:
UMPH_User
  • 3
  • 2
  • 2
  • +1
2 Solutions
 
NenadicCommented:
Is your DMZ "on the side" (i.e. a single firewall) or a full DMZ between two firewalls.  The latter would make it slightly more complicated, but the bottom line is that you don't need to have CAS in DMZ to make it work.  As long as you open up correct ports and set up appropriate NAT rules (twice if you have two firewalls), you can access your Exchange externally.

Which services are you planning to use: OWA (and ECP), ActiveSync (mobile devices), Outlook Anywhere (connectivity from MS Outlook, rather than purely from web browsers?
0
 
AmitIT ArchitectCommented:
CAS is same in 2010 and 2007 so you can take this back to ur boss and tell the story.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
AmitIT ArchitectCommented:
0
 
UMPH_UserAuthor Commented:
Nenadic,
I know that CAS server does not NEED to be in the DMZ but my boss is worried about security and  us being PCI compliant.  I'm only planning on having OWA and activesync.  Again, I know what I CAN do I'm more worried about what I SHOULD do.
0
 
NenadicCommented:
Hi UMPH_User: I didn't mean to lecture. It was merely a request for some extra information, in order to provide the best possible suggestion for the way forward.

Putting CAS in DMZ is not recommended and serves no particular purpose, as you are forcing the firewall to pass RPC traffic, which is neither secure nor easy.

For OWA and EAS, all you only need to open is port TCP:443 and ensure you have proper address mappings. You can use Forms Based Authentication for OWA as you are going directly to the CAS (no server publishing).
0
 
Keith AlabasterEnterprise ArchitectCommented:
To be honest, there aren't any major additional reasons over and above those already given and discussed. The fact that your internal firewall can act dynamically is fine from a functional point-of-view but it is not secure. Having to open ANY port over and above those actually needed for the process to work obviously increases the attack surface but you already know this.
0
 
UMPH_UserAuthor Commented:
OK guys thanks for all the input.  I have convinced my boss to let me put the CAS server on the inside and get TMG 2010 as a proxy.  One last question.....Where does my new OWA Certificate go?  On the new CAS server or on the proxy?
0
 
Keith AlabasterEnterprise ArchitectCommented:
Installed on the IIS server - then re-export it with the private key and then immport it into the FTMG server - local machine account personal store. If you have a separate intermediate cert then import that into FTMG as well in the intermediate store.
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now