Bharat
Wed May 16 18:41:42 CDT 2007
Response to the nagging question:
The Edge Transport server role is generally not a member of the AD domain
and sits in the perimeter network (DMZ). It cannot co-exist with any other
Exchange Server 2007 server roles. Therefore, it can't host OWA.
The Client Access Server (CAS) role is responsible for OWA. Unlike Front-End
servers in previous versions of Exchange (2003/2000) that could be located
in the perimeter (and Microsoft documented and supported the configuration,
though not a recommended one), Exchange Server 2007 CAS servers are not
supported in the perimeter.
Locating Exchange Server 2007 CAS role in the perimeter?
http://exchangepedia.com/blog/2007/03/locating-exchange-server-2007-cas-role.html
Solution: a) Publish your CAS servers to the internet directly b) Publish
using an application-layer or application-aware firewall/appliance like
Microsoft's ISA server or Whale appliances (acquired by Microsoft last year,
just learnt it's now part of ForeFront:
http://www.microsoft.com/forefront/edgesecurity/iag/default.mspx)
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
------------------------------
"Soda Ant" <SodaAnt@discussions.microsoft.com> wrote in message
news:1FBFB1CB-D467-4B19-A340-C0435C34CDAF@microsoft.com...
> I'm setting up Exchange 2007 from scratch in a new installation.
>
> The main part of Exchange will run on a Windows 2003 x64 server on the
> inside network. I plan to put an Edge Transport Server on a machine in the
> DMZ to isolate it from the inside network and not expose the main part of
> Exchange to the Internet.
>
> The only thing I can't figure out is how to get IIS 6 running on the
> server
> in the DMZ to serve up OWA instead of IIS on the main server on the inside
> network. I am not running ISA in this configuration. Is this possible to
> do?
> Can anyone point me to a link on the Microsoft site that describes how to
> do
> this?