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

Exchange Server 5.5 to Exchange Server 2k3 migration mail flow issues

I'm in the process of migrating from Exchange 5.5 to Exchange 2003.  I've used the Exchange 2k3 deployment guide and have completed the process from beginning to the deployment of my first Exchange 2k3 server.  This includes successfully setting up the ADC and getting 1999 out of 2010 object to sync with AD.  

After the installation of the Exchange 2k3 server I ran some "move mailbox" tests that appeared to have worked just fine.  However, when I send an email to the moved mailbox from an email account that still resides on any of the Exch5.5 servers it is returned undeliverable with message:

The following recipient(s) could not be reached:

      mailtest2 on 4/10/2007 11:42 AM
            A required directory operation was unsuccessful
      The MTS-ID of the original message is: c=US;a= ;p=Shared Technolog;l=DFWEX02-070410164223Z-12023

It appears that the Exchange 2k3 Server has installed itself as a Front End Server instead of pointing to the existing Exchange 5.5 IMC.  I used the Microsoft Exchange Troubleshooting assistant to confirm the Exchange 2k3 server's status as a front end server.  When I open the Microsoft Exchange Administrator for Exchange 5.5, the new Exchange 2k3 server is not listed but I know it's part of the site because in Exchange System Manager all the servers in the site show up, both Exch5.5 and Exch2k3.

How can I correct this?  I need to be able to start moving mailboxes to the new server without interupting internal and external mail flow production.
  • 2
1 Solution
Exchange does not install itself as a frontend server. You must have selected the option at some point - whether in error or on purpose.
If EXBPA is stating the server is a frontend then you need to change the option. ESM, Servers. Right click on your server and choose Properties. The option to enable Frontend is on the first tab. Change it and then restart the machine.

BradburyLLCAuthor Commented:
Thanks for for the feedback.  I already checked that before reading your response and it was not checked.  The problem ended up being connection agreements in the ADC. I had 2 different connection agreements that just appeared after the install of the Exc2k3 server.  The agreements pointed to the exc2k3 server and not a 5.5 server.  Aslo, the configuration connection aggreement wasn't pointing to the correct server.  I used the ADSIEdit util to make corrections to the configuration connection agreement, deleted to 2 agreements that were auto created and everything worked correct at that point.  
BradburyLLCAuthor Commented:
I'm going to award the points to you Sembee because you did clear up a question I had about Front End servers and the ability of it getting installed automatically.  Thanks.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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