Exchange Share SMTP Namesapce

Posted on 2009-04-16
Last Modified: 2012-05-06
I really need help grasping this concept.

I need to move users from one forest to another, and one exchange server to another, so CrossOrg. I want all users in each Org to send/receive email for the same external domain. They also need to be able to talk to each other internally and look up names in the GAL. I want to do 1 department at a time. I need the steps to achieve this.

I have already created the trusts and built the new Exchange 2007 server. The old Exchange server is 2003.

I also used ADMT 3.1 to copy users to the new forest.

I have figured out how to move the mailboxes with EMS.

Now, I want to be able to disable the old mailboxes (2003) and keep everyone communicating in each forest/org.
I have read numerous articles but I'm getting confused.

I need specifics of what to do on each server.

ForestA Exchange 2003 (Will be decommissioned)
ForestB Exchange 2007

Both need to send/receive same external domain. Internally, users need to be able to communicate with each other cross org until the transition is complete.

What connectors? What recipient policies?, etc...

Please Help.
Question by:LCNW
    LVL 7

    Accepted Solution

    Go thru this one:
    if u have already read this.let me know.
    LVL 1

    Author Comment

    I have already read that article. It helps but I'm still confused. I need to understand what type of connectors to build on each server 2003 and 2007. Then I need to understand the recipient policies. Finally, how do I sync the GALs or how do people find each other internally cross org?

    Once I tackle all of those items I need to move onto migrating some public folders.

    Please let me know if you can help. I would like to step through this piece by piece so I thouroughly understand everything.

    LVL 1

    Author Comment

    Okay I have the connectors and the Recipient policies done and they seem to be working. Is there a way to sync the GALs?

    LVL 1

    Author Comment

    Nevermind I'm having connector issues. Here is what I have done so far.

    On Exchange Server 2003
    1)I created and new recipient poilcy and put the shared namepace in it as non-authoritative.
    2)I added a new internal name to the default policy and removed the shared namespace.
    3)I created a SMTP connector with the address space of the shared smtp namespace and set it to forward to smart host ip of new 2007 server.

    Is that all correct and all that needs to be done for that server? If so, I will move on to the 2007 server.
    LVL 7

    Expert Comment

    if u can provide with the domain name,server names and ips,recipient policy...dat wud be more easier
    LVL 1

    Author Comment

    Ok. I will user some generic names.

    Public domain (

    Forest A
    Domain A (DomainA.local)
    Server A (Exchange 2003) []

    Forest B
    Domain B (DomainB.local)
    Server B (Exchange 2007)[]

    Here is what I've done so far on Server A:
    1)On Server A I added a new internal Domain to the the Default recipient policy (DomainA.local)
    2)Then, I created a new recipient policy for the public domain( I need to share. In this policy I added the public domain and set as non-authoritative and set it as primary.
    3)I removed the public domain( from the default recipient policy.
    4)I created an SMTP connector and did the Forward all mail through this connector to the following smart hosts setting with the Server B address []. I typed the for the Internet Address Space Properties and selected Allow messages to be relayed to these domains.

    Is this all that needs to be done on Server A?

    LVL 1

    Author Comment

    I think I have this all working. Due to the lack of documentation for Cross Org between 2003 and 2007 with just a hub transport server, no edge server, I will write up what I did soon. Now that I have it working, it's pretty simple, just confusing to get there.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Set OWA language and time zone in Exchange for individuals, all users or per database.
    "Migrate" an SMTP relay receive connector to a new server using info from an old server.
    The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
    This video discusses moving either the default database or any database to a new volume.

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    22 Experts available now in Live!

    Get 1:1 Help Now