Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
   

The problem with co-existence is the mail routing

Page 1 | Page 2 | Page 3

Directory Synchronization

Here is where things get tricky. If you use the connectors to synchronize the directories, SMTP will not be the transport used for message routing. Because the addresses will be created with the connector, the systems will try to use the connector as the transport. To correct this we have two options:

      1)      Use a third-party tool to keep the directories in place

 2)      Force the directory to delete the references to the legacy system while keeping the entries synchronized between the systems.

Again, the focus here is long-term connectivity so whatever option we choose should be stable and supported be either a third-party or within the scope of Microsoft or legacy vendor support. A secondary goal is to make the solution cheap. The connectors are free, so coming up with a costly alternative may not sit will with the executives with the check-books.  

There are many possible solutions including Microsoft Metadirectory Services and similar products from other vendors. Instead of posting my directory synchronization answers, I want to see if someone out there has created a better sync solution. I will post a summary in the next week or so with the ideas I have collected. I will also try to lab up these ideas so we will all know how well they work.

Send your responses to sbryant@outlookexchange.com

 

Blueprint for an Exchange Service Level Agreement

Columnist's Index
Page 1 | Page 2 | Page 3

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008