Exchange Server - OWA - Front/Back End Srvr 2

[jny04]

I have Exchange Server installed for 750 Users, however we want to deploy a DMZ, with a front end svr.

Can you advise if i should use the forest prep/domain prep installation commands on the new Front End server?

Which server should OWA use IIS for the front end or back end? Or should i ocnfigure this all from exchange manager?

Also is there any advice when trying to configure the front/back end/IIS?

 

[PScottC]

You only have to run forest/domain prep when you install exchange for the first time.

What version of Exchange are you running?

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[jny04]

exchnage 2003!.

so should i just setup exchange with no switches??

 

[sab4you]

correct

 

[PScottC]

Yeah... I would setup your FE server on your inside network and test it there. Then move it to DMZ when you're ready to deploy. I strongly recommend that you acquire an SSL cert for your FE box so that users' passwords are not transmitted in clear text over the internet.

Go to Microsoft's Exchange library online. There are a number of white papers on deployment of Exchange and FE/BE solutions. There's a whole bunch of ports you will have to open up on your firewall from the DMZ to the inside network to get everything working. The white papers document it relatively well.

DMZ issues are the main reason for setting up inside first. At least you can prove it works. When you move it to the DMZ I can almost guarantee that you'll have to troubleshoot it for a few hours.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[PScottC]

BTW --- Most of the MS white papers reference ISA server. You can safely replace the word "ISA" with "Firewall", since you can get this to work with pretty much any firewall.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[jny04]

any white papers on this?

 

[PScottC]

Here's the library link: [URL unfurl="true"]http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/default.mspx[/url]

Here's the FE/BE white paper, it contains a list of ports that have to be open on firewall: [URL unfurl="true"]http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/febetop.mspx[/url]

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[foc]

I would also suggest that you encyrpt the traffic between the FE and the BE servers - easy to do.

 

[jny04]

HI thanks FOC - thats good but i have been told encrytion can cause problems ? is there any white papers on this??

thanks guys

 

[foc]

I'll have to look for white papers on this, but here is something you can you can reference. Again - change ISA to firewall.

This is just one of many ways to set things up.

http://www.tacteam.net/isaserverorg/exchangekit/2003/2003rpchttp/2003rpchttp.htm