Yeah I skimmed that quicker than I should have. I saw that he had a single server before so I should have been specific. Good catch...
The link I posted is probably some of the first ms docs written that I have actually been impressed with, they are very complete. Hopefully MS is turning over a new stone wrt to docs. There was a while where stuff was written by community folk and was just terrible. I would just reco a quick read through the technet site, its super good for exchange. We both instinctively agree though:) -----Original Message----- From: Paul Gordon [mailto:[email protected]] Sent: Monday, October 19, 2009 3:02 PM To: NT System Admin Issues Subject: RE: Exch2003 to 2007 experiences? Our survey said.... UH OH! The Edge Transport role is a "specialised" variety of the hub transport role, - it does pretty much the same functions. You do NOT *have* to have an edge server, it is entirely optional depending on your needs/network topology etc. You can just use hub transport server(s) alone if this more closely matches your requirements. However, if you believe that you *DO* want to utilise an edge transport, then you need to be aware of the following: - The Edge transport role CANNOT co-exist with any other Exchange server role, it must be the only Exchange role on a dedicated box. - The Sever hosting the Edge transport role MUST NOT be a domain member - it should be installed as a standalone server in its own workgroup in your DMZ. It will utilise AD-LDS (AKA ADAM), and you will configure an "edge subscription" with one of the Hub transport servers on the internal network in order to replicate the necessary AD information out to it. My instinct would be that if you are in a position where you were/are considering a one-box solution in the first place, that you very likely don't really need to bother with a edge server. £0.02 Paul G. -----Original Message----- From: Joseph L. Casale [mailto:[email protected]] Sent: 19 October 2009 20:22 To: NT System Admin Issues Subject: RE: Exch2003 to 2007 experiences? >4. Do I "require" a seperate Edge Server? Or can that be on the same box >as our hub transport, client mailboxes, etc.? (it seems doing a "typical" >installation of Exchange 2007 puts it all on all box even though the >"typical" installation doesnt say anything at all about Edge Transport?) It can all be on one box, sure. Different needs require splitting it up, but it is designed to coexist. >5. In a small sized Exchange organization (a single Exchange 2003 server), >would you "recommend" a seperate Edge Server? Or just lump it in with the >main Exchange 2007 box. Put it on one, keep it simple. If you have specific needs like HA or sec for edge servers, you would know:) If you have a single 2003 box now, a single 2007 box will do. BTW, 2010 is peeking its head through the door, and it plain rocks. >I've read a number of Exchange 2007 technotes, articles, etc, but I am >looking for real world answers from people that have done this. Thanks! HTH, jlc ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.422 / Virus Database: 270.14.20/2441 - Release Date: 10/18/09 09:04:00 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
