• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 352
  • Last Modified:

Exchange Share SMTP Namesapce

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.
0
LCNW
Asked:
LCNW
  • 5
  • 2
1 Solution
 
RammesteinCommented:
Go thru this one:
http://support.microsoft.com/kb/321721
if u have already read this.let me know.
0
 
LCNWAuthor Commented:
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.

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

Thanks.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
LCNWAuthor Commented:
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.
0
 
RammesteinCommented:
if u can provide with the domain name,server names and ips,recipient policy...dat wud be more easier
0
 
LCNWAuthor Commented:
Ok. I will user some generic names.

Public domain (Domain.org)

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

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

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(Domain.org) 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(Domain.org) 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 [10.1.2.20]. I typed the Domain.org 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?

Thanks.
0
 
LCNWAuthor Commented:
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.

Thanks.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now