I usually would love to do that, but they already gave me a personnel notice last time I suggested that exchange could be handled better and more efficiently by following best practices (perhaps those weren't the exact words I used, eh, Karen?) because I "was not being customer service oriented". Now I am not permitted to suggest improvements without getting prior approval. But since half of our administrators are on this list, I'll probably be sitting on the hot seat once again.
Terry -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fyodorov, Andrey FTL Sent: Wednesday, January 28, 2004 5:11 PM To: Exchange Discussions Subject: RE: Front End Server Chaos doubled Would you be my messenger? -----Original Message----- From: Beavers, Terry [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 3:55 PM To: Exchange Discussions Subject: RE: Front End Server Chaos doubled I know you can do that. Unfortunatelym nultiple domains with namespaces and servers is the political reality here and at many other large universities. We actually host 10 or 15 smtp domains on our exchange boxes in our dept. But the reality is that there are about 15 other smtp domains out there in our enterprise, each in their own windows domain with their own exchange servers. Don't tell me about best practices. Tell the people who run this place. Terry Beavers -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fyodorov, Andrey FTL Sent: Wednesday, January 28, 2004 2:48 PM To: Exchange Discussions Subject: RE: Front End Server Chaos doubled You don't need to have different domains to be able to support multiple SMTP namespaces. You can do it all with one AD domain and many recipient policies in Exchange, each recipient policy defining a different SMTP domain name. You need to find some Exchange hosting whitepapers. -----Original Message----- From: Beavers, Terry [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 2:26 PM To: Exchange Discussions Subject: RE: Front End Server Chaos doubled 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 _________________________________________________________________ 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.
