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

Exchange 2007 Migration to 2010 Question (Mx Record)

Hello experts,

I have a question and hopefully it's an easy one.

I have completed (almost) the migration from our 2007 Exchange server to 2010.  Both servers are currently co-existing.

Mail is still being routed through our 2007 server because the check mark telling it to look at the mx record for mail delivery is checked and I have not changed over the mx record.

I have followed to the best of my knowledge every other step from the Microsoft check list and the finalize documentation.  All firewall changes everything else has been done.

Is it just as simple as changing the mx record and everything should work?  If I missed something and it doesn't work, can I change the mx record back and review and do what is needed?  Is there significant downtime in this?

I have never done this and really want to get this done but I'm scared of taking everyone down, without a back up plan.

Thank you for your help.
2 Solutions
Patrick BogersDatacenter platform engineer LindowsCommented:
If transferred users log into OWA, are they redirected to the 2010 version? If Yes it is setup correctly and you can change the MX record.

Still have it run dual for couple of days before uninstalling old exchange.
klsphotosAuthor Commented:
All mailboxes have been moved to the new server and have been running off of it for several weeks, it's just the mail is still routing through the old server.
Patrick BogersDatacenter platform engineer LindowsCommented:
What about owa?
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

klsphotosAuthor Commented:
Yup they have been using the new 2010 owa for a few weeks now and love it.  2007 was outdated.  I got the nerve and made the change and my test to my internal account and also my gmail account were successful, does that mean its actually done?  That's it? :):)
Gareth GudgerCommented:
When you say you need to update the MX record, I assume then that your new 2010 server will be using a new public IP address? If so, some things to check:

1/. Point it to the new Public IP of the 2010 server.
2/. Make sure port 25 is being forwarded to your new Exchange 2010 server.
3/. Make sure your Send and Receive connectors on Exchange 2010 are ready to go.
4/. Do you currently using any cloud or appliance filtering for anti-spam and anti-virus? If so, you likely do NOT need to update the MX record, but more-so just need to update on that service or appliance where to redirect mail.
5/. Same deal for outbound - are you using a smarthost or going straight to DNS/MX for delivery.
6/. If you have an SPF record, you may need to update that with your new public IP of your Exchange server.
7/. IF you are sending directly to the internet (not using a smarthost) then you should create a PTR record with your ISP.
Please check out  this article http://tinyurl.com/qhb5bcq. May be it helps you.
Simon Butler (Sembee)ConsultantCommented:
Have you enabled Anonymous on the Default Receive Connector? If not then you need to do that and then email from the internet will flow. If you don't do that then email will bounce. Change the option, restart the MS Exchange Transport service, then adjust the MX record and or NAT on your firewall.

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

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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