Several Exchange Front-End Server Questions
Posted on 2007-08-07
I currently have a Windows/Exchange 2003 setup going. At this point we have the configuration of one front-end server & one back-end server. The front-end server is currently being used for our OWA, RPC over HTTP & Exchange ActiveSync. It is working great, except the front-end server is old & dies a lot. With that information, here are my questions:
1) I am looking at adding a second front-end server to do the same functionality. What software licensing do I need to buy? I know I need Windows 2003 server. Do I need to buy Exchange 2003 server also? What version (our back-end is using Exchange Enterprise)?
2) What are the bottle-necks on a front-end server that I need to address? We have about 60-100 people using RPC over HTTPS (at certain times), about 50 phones doing Exchange ActiveSync & about 10-20 people on OWA.
3) Is there a way to set-up a public DNS record that points to multiple IP addresses for our Front-end server? (Round-robin) The purpose would be to enable some sort of clustering in the case that one of the front-ends went down, it would automatically switch to the other front-end without any user interaction. Does that make sense?
4) Does anyone have any good pointers for a front-end Exchange server that I should consider? (AV, Configuration quirks, Exchange Activesync settings etc)