Solved

Exchange 2007 Deployment  - Help Needed

Posted on 2007-11-19
2
193 Views
Last Modified: 2010-03-06
In the past I deployed and managed an Exchange 2003 server for a small company with no front end smtp.  I am in the process of developing a deployment for Exchange 2007 for a 200 user organization and I have a few questions for the experienced experts.

This deployment is not a migration from an earlier server but a new installation of Exchange 2007 for a new domain. I understand what the EdgeT role is for but have you found that it is really worth the extra money for the spam and security that it provides?  Originally I was planning for a 3rd party spam appliance which seems to be a better spam solution.  Also, I am not quite sure how this configuration would work from the public standpoint. I would have an EdgeT in the DMZ (Firewall DMZ Public IP 999.999.9.1  and Internal IP 192.168.1.5) and then the client access role on the internal server ( Firewall Public IP 999.999.9.2 and Internal IP 192.168.3.6).  I am assuming that my public DNS would point SMTP to the EdgeT server to allow public (SMTP) emails in and then setup the public DNS mail record to 999.999.9.2 public address to access the OWA?  Would this be the correct setup?

Has anyone installed the EdgeT as well as implemented a 3rd party spam filter for layered filtering? Pros/Cons?
0
Comment
Question by:preshomes
2 Comments
 
LVL 18

Accepted Solution

by:
Don S. earned 500 total points
ID: 20314988
Because you cannot put the client access roll on an Edge server in the DMZ, it's maybe less usefull than MS would like you to think - UNLESS you are using it in an ISA configuration which is the officially blessed MS configuration.  An Edge server, however, will off load your main Exchange server from having to handle things like spam and AV filtering from the outside world and is an asset if you ever come under a severe DOS attack.  I've put in an installation with an Edge server, main email server, 3rd party firewall proxying the Client access connections, and external spam filtering service.  It seems to work well enaough - only time will tell if it proves to be more resilient than a single server setup.  BTW, You do not need an edge server to run MS spam filtering - you can run it on the Hub transport role - there is a setting that will allow you to do that.

IMO you do not need an edge server for 200 mailboxes for performance reasons, but if you want an extra layer seperating the evil doers from your core mail server then its fine.
0
 
LVL 1

Author Comment

by:preshomes
ID: 20315232
Thank you for your comments...I did understand that I can run spam filtering from the Hub.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now