Re: Exchange 2007 / OWA / RPC over HTTP
- From: "Scott Schnoll [MSFT]" <scschnol@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Nov 2006 11:58:54 -0800
Answers inline...
--
Scott Schnoll
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.
"Ian Davies" <IanDavies@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:516F9CAD-36FA-487E-8C6C-45F209F53D28@xxxxxxxxxxxxxxxx
I have a couple of questions that so far I havn't been able to find a clear
enough answer for me in the documentation:
1) OWA - from what it looks like, I can no longer have an OWA server in
my
DMZ. Is this really true? I don't like having to give a direct
connection
from the outside to my inside network.
[SS] It's true. The Client Access Server (CAS), which among other things
includes the OWA feature, is not supported in a perimeter network (aka a
DMZ). Instead you'll deploy one or more CASs inside your organization and
put a robust firewall such as ISA 2006 in front of it.
2) RPC over HTTP. It also appears that there are no longer Front-End
servers. The Edge transport role looks like it only handles
relay/anti-virus/spam issues. So for Outlook Anyware I'm assuming I have
the
same issue as OWA. I need to have a direct connection from the outside to
inside?
[SS] You use the same CASs to serve RPC over HTTP (now called Outlook
Anywhere). The CAS sits in the internal network and is published via ISA.
Very secure and reliable!
This means in both cases, there is no "direct" connection. Connections are
made by clients to the ISA Server, and not directly to the CAS.
.
- Prev by Date: Re: change smtp header
- Next by Date: Re: Exchange 2007 / OWA / RPC over HTTP
- Previous by thread: Re: FE Exchange deployment
- Next by thread: Re: Exchange 2007 / OWA / RPC over HTTP
- Index(es):
Relevant Pages
|
Loading