I am hoping to get some feedback about a proposed solution we ahve for integrating 3 mail domains.One domain 2000 or so users, the other 2 are about 150 or so.We plan on migrating the 2 smaller domains into the larger domain, but there is a lot of work to execute before we can do that. In the meantime, I am hoping to make avaialbe the GALs of all 3 domains to each of the other domains. My plan is this:Export the GAL from each mail domain to a csv fileCreate a new public folder and import the csv file for each domain into the public folderMake the Public folder availabe as an Outlook Address Book.I plan on creating a script that would execute this Export/Import on a weekly basis to account for new user additions to any of the domains.Can anyone give me some feedback about whether this is a sound plan or should I be thinking about this in a totally different way?

If they are all E2k/E2K3 servers then why not to use IIFP?It's free, simple and supported documents are available... this will provide you with an automated way of syncing the 3 GALs together.If you don't want to go with this approach then you can periodicly impport the CSVs directly in the GAL as contacts, this will be easier for the users to locate rather than the PF OAB and you can script the contact creation also. If it's E2K7 then this will be much more easier with powershell.Mohamed Baher | MSFT | MCA:Exchange 2007 | http://blogs.technet.com/mbaher/

Hello,As Mohamed suggest for IIFP which is quite costly...Interorg Replication Tool (IOREPL) free free/busy and IIFP for GALsync. The following blog has a lot of tutorials on setting up IIFP and IOREPL for cross-forest environments: http://exchangeserverinfo.com/Or you can use Quest's Collaboration Services Tool that takes care of both things without needing a trust, create accounts, etc.. Making the Exchange Server GAL Portablehttp://www.slipstick.com/exs/portagal.aspGALsync 3.0.0.9http://www.softpedia.com/get/Internet/E-mail/Mail-Utilities/GALsync.shtml Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3