Exchange 2007 Deployment - Help Needed
Posted on 2007-11-19
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?