That the FE/BE must be in the same domain is well-documented and makes sense from a single-domain email namespace design concept.
But what about the situation where we want ONE OWA interface to be the FE for, say, ten BE machines in different domains (and different email namespaces). Where we can tell users, jut go to https://owa.usf.edu/exchange/joebob and they will be routed to their appropriate BE server. MS docs state that the FE does an AD lookup of the user to find their home server and route the user to it. In that case I fail to see why that couldn't be done for a user in ANY domain in the forest. That info is all in the GC. But my question is, what approaches has anyone taken in this case to provide a single OWA entry point? Terry Beavers USF -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Cornetet Sent: Wednesday, January 28, 2004 10:30 AM To: Exchange Discussions Subject: RE: Front End Server Chaos FE/BE servers must be in the same domain (see page 16 of the MS whitepaper Echange 2000 Front-end and Back-end Topology"). _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
