Dear all;We are migrating Server2003 dc/exc2007 to server2008/exc2010 with new forest infrastructure.But smtp namespace will be the same.legacy forest new forestdomain : a.com domain: b.comsmtp namespace of mail address : domain.com(mail:user@domain.com) smtp name space of mail address: domain.comI have migrated pilot users with admt(sid history)And move mailboxes to exchange 2010.Everything fine.But i'm confused about coexistence during exchange migration.1-What will happen when a user from legacy exchange send mail to a user from new forest.There is no send connector between exchange,only forest trust.2.When a mail recevied from internet by the new exchange server,it will look at the smtp name space(domain.com)and it is authoritive about this domain.it will look for user in the new forest.But if this user is in old forest yet,will this new exchange route this message to old exchange over forest trust.Or should i configure receive/send connector ?3.or what will happen when old exchange receive a message from internet for a user in b.com forest.?Thanks.

1 - Unless you can make this transition very quickly, you should consider implementing a directory synchronization between the two forests so that users in one can see the other. You will need a send connector unless you have some special external mail routing technique that will handle mail routing for you. 2 & 3 - The first organizaiton where mail enters cannot be authoritative for the domain, and your send connector must point to the other server. An alternative approach is to assign the old forest's users an alternate SMTP address of something like user@old.company.com and create contacts in the new forest that directs their mail accordingly. I think this approach is often much less confusing because it clearly defines how the mail is to be routed.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "biblo45" wrote in message news:6f5b7cd6-e2e5-4688-87cb-c178488fedf1...Dear all;We are migrating Server2003 dc/exc2007 to server2008/exc2010 with new forest infrastructure.But smtp namespace will be the same.legacy forest new forestdomain : a.com domain: b.comsmtp namespace of mail address : domain.com(mail:user@domain.com) smtp name space of mail address: domain.comI have migrated pilot users with admt(sid history)And move mailboxes to exchange 2010.Everything fine.But i'm confused about coexistence during exchange migration.1-What will happen when a user from legacy exchange send mail to a user from new forest.There is no send connector between exchange,only forest trust.2.When a mail recevied from internet by the new exchange server,it will look at the smtp name space(domain.com)and it is authoritive about this domain.it will look for user in the new forest.But if this user is in old forest yet,will this new exchange route this message to old exchange over forest trust.Or should i configure receive/send connector ?3.or what will happen when old exchange receive a message from internet for a user in b.com forest.?Thanks. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi,Please understand that if the domain is configured as authoritative and a recipient is not found in the Active Directory directory, a NDR is returned to the sender. If the domain is configured as an non-authoritative or internal relay domain, it first tries to deliver to a recipient in the Exchange organization. If the recipient is not found, the message is routed to the Sender Connector that has the closest address space match.Thus, you need first uncheck "This Exchange Organization is responsible for all mail delivery to this address" option on the recipient policy, then create the Send Connector with the domain.com address space.For Exchange 2010, you need configure the domain as internal relay domain, and create a send connector with the domain.com address space.For more information, you can refer to the article about mechanism of sharing the address space:Exchange 2003:http://support.microsoft.com/kb/321721Exchange 2010:http://technet.microsoft.com/en-us/library/bb676395.aspxThanksAllen

Thanks.Another question;Should i create contacts for internal relay domain configurations?Because when i configure internal relay domain and create a send connector, exchange first tries to deliver message on same organization.After that "if a contact exist" exchange send this message over send connector.Is it true? Because if i don't create contact on source domain for a migrated user, although i configure internal relay domain, source exchange doesn't send message to migrated user.It returns RESOLVER.ADR.Exrecipnotfound error.If i create a contact on source domain,mail was dellivered to the target exchange.If this is the situation, i have to create contacts for all users on target domain before migration.So When i migrate a user to the target domain ,he can send message because of contact list.?

Hi,No, you don't need to create the contacts. For the send connector, you need to set the target Exchange as the Smart host. No matter whether the conacts are created or not, the Send Connector must be used.ThanksAllen

Yes i tried yesterday this confgiruation and without creating contacts it worked.The only problem is GAL.When i migrate a user to another forest,this user must see legacy domain users in GAL.I dont want to use IIFP so i export all users and import as contact to exchange 2010 with group memberships.Is this a true step?

Hi,To export and import the users simply, the group memberships will be lost. To keep the membership, I suggest you use the ADMT tool to do this migration.http://www.microsoft.com/downloads/details.aspx?FamilyID=ae279d01-7dca-413c-a9d2-b42dfb746059&displaylang=enThanksAllen

I'm already migrating users and groups with admt.But when i migrate a user with his group to the new domain and exchange infrastructure,that user cannot see on GAL any user from legacy domain.So there must be contacts on new domain for legacy users.I can sync GAL with IIFP but i dont want to buy another license for this product.

interesting post - http://community.priasoft.com/blogs/exchange_migration_team_blog/archive/2010/05/20/issues-to-be-considered-while-thinking-about-moving-mailboxes-to-exchange-2010-using-the-microsoft-native-tools.aspxCJ