asked on

Need clarification of Exchange 2003 Front-end/Back-end setup

We have two existing Exchange 2003 servers (two sites, one domain) and are looking to setup a front-end server for OWA access. What I got from previous posts is: install exchange, move your certificate to the new server(if you're using SSL), flip the front-end switch, make sure you're forwarding SSL, etc. through your router/firewall to the new server, done. Is it that simple? What else needs to be done so OWA access will route properly for the users? Any other services need to moved or configured or is all of that taken care of with the front-end switch?

Thank you

Sembee

There is very little that needs to be done. You can simply enable the option and that is it.
There are refinements to the server that can be carried out, but at a basic level nothing more needs to be done. Just make sure that the frontend server can see both backends correctly.

http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/febetop.mspx

Simon.

jforville

ASKER

Thank you for your post Simon. As far as the certificate goes for SSL, the 'first' exchange server was the OWA server running with SSL. Is there anything special we need to do with that other than move it to the front-end server?

Sembee

Depends if the certificate was on a generic name or the server's real name.
If it was the server's real name then you are going to have problems as you would have to remove the original server before the SSL certificate will work correctly.
If the certificate is on a generic name that is simply mapped to the server in DNS then just move the certificate and update DNS.

Simon.

jforville

ASKER

>you would have to remove the original server

I'm not sure if I follow, do you mean I would have to remove the original server certificate?

jforville

ASKER

If I understand correclty, in IIS the certificate is issued to mail.mydomain.com, the name of the server is myserver.mydomain.local. So, the generic certificate name will be unchanged to the outside world despite being put on mynewserver.mydomain.local.

ASKER CERTIFIED SOLUTION

Sembee

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jforville

ASKER

Great, thanks for all of the help!