Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2007-04-10
3
Medium Priority
?
207 Views
Last Modified: 2010-03-06
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
            MSEXCH:MSExchangeMTA:ICI:DFWEX02

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.
0
Comment
Question by:BradburyLLC
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 1500 total points
ID: 18885832
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.

Simon.
0
 

Author Comment

by:BradburyLLC
ID: 18912088
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.  
0
 

Author Comment

by:BradburyLLC
ID: 18912191
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.
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
how to add IIS SMTP to handle application/Scanner relays into office 365.
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

670 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