The point of FE server is not to avoid creating separate namespaces. The real reason 
for using an FE server is to offload some of the processing from the mailbox (back-end 
server) - like initial authentications, SSL processing, etc. Plus FE is great for when 
you need to hide the back-end behind a firewall.

But as far as namespaces, whatever virtual server/virtual directory set you have on 
the FE, you have to make the same on the BE.

My configuration uses one virtual server with a bunch of vitual directories and it is 
all bound to the same IP (on a given server)

One could also make separate virtual servers for each domain, but then you would need 
to use additional IP addresses.

-----Original Message-----
From: Woodruff, Michael [mailto:mwoodruff@;inchord.com]
Sent: Friday, October 18, 2002 10:58 AM
To: Exchange Discussions
Subject: RE: Front-end/Back-end config


What good is the front-end server if you still need a separate namespace
for each domain?  You can do that without a FE server.  

-----Original Message-----
From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com] 
Sent: Friday, October 18, 2002 10:54 AM
To: Exchange Discussions
Subject: RE: Front-end/Back-end config


http://FDQN/customerabc

or http://IPAddress/customerabc

-----Original Message-----
From: Woodruff, Michael [mailto:mwoodruff@;inchord.com]
Sent: Friday, October 18, 2002 9:28 AM
To: Exchange Discussions
Subject: RE: Front-end/Back-end config


I can hit the directories with server/directory, but how do you use a
single url to hit all of them?

-----Original Message-----
From: Andrey Fyodorov [mailto:afyodorov@;innerhost.com] 
Sent: Wednesday, October 16, 2002 9:47 AM
To: Exchange Discussions
Subject: RE: Front-end/Back-end config


I have FE/BE config with the generic FE/BE virtual directories, plus I
have a few customers for whom I created their "dedicated" OWA virtual
directories.

I did the generic ones by following the whitepaper. I did the
"dedicated" using the method of scientific poking around :)

This is what I have on the BE:
PROTOCOLS
        HTTP
                Exchange Virtual Server
                        exchange
                        public
                        customerabc
                        customerxyz
                FE01
                        exchange
                        public
                FE02
                        exchange
                        public

In the properties of customerabc:
Mailboxes for: customerabc.com
Access -> Authentication
Basic Authentication
Default domain: \


In the properties of FE01
Advanced
IP                      TCP Port        SSL Port        Host name
All unassigned  80              443             FE01

Access -> Authentication
Basic Authentication
Default Domain: \


Similar stuff for the properties of FE02


NOW ON THE FRONT-END SERVER ITSELF:
PROTOCOLS
        HTTP
                Exchange Virtual Server
                        exchange
                        public
                        customerabc
                        customerxyz


In the properties of customerabc:
Mailboxes for: customerabc.com
Access -> Authentication
Basic Authentication
Default domain: \





-----Original Message-----
From: Woodruff, Michael [mailto:mwoodruff@;inchord.com]
Sent: Wednesday, October 16, 2002 9:25 AM
To: Exchange Discussions
Subject: Front-end/Back-end config


I am setting up our Front-end/Back-end config for our org.  I have
installed a FE server (Enterprise:-)).  I don't understand Microsofts
whitepaper on this.  I want to create virtual directories to avoid all
the SSL certificates.  When a virtual directory is created for a certain
domain, do I need to do anything else with that directory or leave it as
it is?  It says to create an identical one on the BE server also.  All I
get when I hit the directory is HTTP 404 - File not found...  Someone
with knowledge of the FE/BE config, please clue me in on what I am doing
wrong please.  Thanks.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to