How do I install OWA on DMZ as frontend server? 2

[Shadowfax1]

Hi, how do I install OWA on the DMZ as a frontend server? I have the main Exchange 2003 running, but I want to install OWA 2003 onto the DMZ, how do I install this?

Kind Regards

Andy

 

[xmsre]

You'll need a few ports open to the internal network; 80 445, 135, 53, 88, 123, 389, and 3268. The front end will need to be able to resolve the SRV recods for the GCs and the backend or you will also need to open 137 and 139. You will need to open 1024-1026 for directory access, or you can lock it down to a single port with a reg key.

From the DMZ to the internet, you only need to open 443.

After you install, check the box to make it a front end server. If your backend is a cluster, you'll need to add some host headers to the backend for external FQDN, Frontend FQDN, and Frontend netbios name. You can dismount the pub on the frontend, but it's best to wait until PF hierarchy finshes replicating to avoid replication messages queueing to the front end. If you have no MTA or connectors on the front end, you can dismount the priv, although you will see some error messages about it in the app log. You can ignore these.

The install itself is a standard install. I don't put the tools on a front end in the DMZ. The disaster recovery process is simply disasterrecovery install. This puts everthing back except security customizations and the certificate for SSL. After you install your certificate, you can export it for later use in disaster recovery. The only real security mods are setting basic, setting forms based authentication, and setting security on exweb/bin/spell if you want to use the speel chucker.

 

[Shadowfax1]

Wow thanks! Just a another newbie question, I wasn't involved in the initial build of Exchange 2003 (Enterprise Edition), which I guess was created as a backend server, so do I just put the Exchange 2003 disk in and get an option to install it as a frontend server? If so does this mean I have to treat it as a second Exchange 2003 server with all the costs of the licensing?

Kind Regards

Andy

 

[xmsre]

You just install it. After it's installed, in ESM, on the properties of the server object, check the box to make it a front end server.

 

[Shadowfax1]

Does this mean I have to treat it as a second Exchange 2003 server with all the costs of the licensing?

 

[xmsre]

Yup.

If you used per seat licensing, the only additional cost is the $800 or so for Exchange 2003 Standard. Unlike Exchange 2000 Standard, Exchange 2003 standard CAN BE a front end server.

 

[sibbir]

i have a similar situation. i already have a single exchange 2003 running, now i want to add a front end. my question is while i'm configuring/restarting front end will the backend keep working just fine? or will this affect users while i'm setting things up the front end. Thanks so much for your help.

 

[shadowfax1066]

None of your users will be effected while you build/restart an OWA 2003 server, just stick it on your DMZ and allow the correct ports to talk to your back-end Exchange server and DC's for DNS:

http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html