[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


exchange 2003 and 5.5 not synchronizing

Posted on 2006-06-01
Medium Priority
Last Modified: 2010-03-06
Here's the scenario:
I'm not an expert in Exchange. We had a consultant come in to migrate most of the users to a new 2003 box with exchange 2003. There was an OU (named Migration) that was setup to replicate with 5.5 directory. One of my colleaque was cleaning up the AD and renamed this Migration OU to something else, and also created a bunch of other OUs.

Here's the problem:
When creating a user on AD on the 2003 box, it is no longer replicating to the NT's 5.5 exchange. GAL is on the 2003 box, so user shows up on GAL, internal emails inbound and outbound is ok. But since the SMTP is on 5.5, external inbound email are bounced back with: The recipient name is not recognized error.

I went to the AD Connector Services and edited the Connection Agreement:
- From Windows tab: added all of the newly created OUs
- From Exchange tab: changed the default destination from Migration OU (initial & deleted OU) to Transition1 OU.

Tested by creating a new user on Transition1 OU, but still no luck in replicating it to 5.5.

Please help shed some light. Thanks!
Question by:dellon
LVL 12

Accepted Solution

aa230002 earned 600 total points
ID: 16808429
What if you create a new mailbox in Exchange 5.5? does that replicate to Active directory via Recipient Connection Agreement? Do you see any errors in the Application log on the server where you have your Active Directory Connector installed?
In which OU, you created this new user in AD? is this OU added to the "From Windows tab" on the Recipient connection Agreement. You might want to go to Connection tab on Recipient connection Agreement and re-enter the user name and password and say "Replicate Now" by right clicking on the Recipient Connection Agreement
and then check the application log if there is any error.

Amit Aggarwal.

Author Comment

ID: 16808813
Great tips on places to look. The application log shows that even after I point the destination to "Transition1", it was still looking for "Migration". I renamed Transition1 to Migration, reran the replication and works fine.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses
Course of the Month18 days, 19 hours left to enroll

834 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