Solved

questions about migrating from 2003 exchange to 2010

Posted on 2014-02-19
11
273 Views
Last Modified: 2014-02-20
So I have another server with exchange 2010 configure and working properly.
I move my inbox over there to test. Able to send email internally and external, also to users still on 2003 fine. It is going through the 2003 send connector, not 2010 yet. I have the routing groups setup between 2003 and 2010.

1. After moving the rest of mailbox over, I need to switch smtp feed over to new server.
Currently, firewall has smtp incoming pointed to old server, will switch to new server ip.
SMTP Outgoing will be also allow on port 25 via new server ip.
Also will change internal dns to point mail cname to new server.

2. The old server is pointed to .227 on public side. MX record on outside shows old server name, does that need to be update to new server? Also the cname will be to be update to new server name? I don't think any of these needs to be updated right since incoming will be pointed to new server via internal dns and firewall.
@                               IN      MX      10 oldexchange.test.com
@                               IN      A       69.89.15.39
mail                            IN      CNAME   oldexchange.test.com
oldexchange                     IN      A       61.197.210.227 (Need to update old to new?)

3. Email on my phone isn't working, I'm assuming because the public name is still routed to old server and my mailbox is not on old server anymore correct?

4. OWA isn't working externally because email server publicly is still pointed to old server which doesn't have my mailbox?
5. Any other changes I might be missing?
0
Comment
Question by:uscost
  • 6
  • 5
11 Comments
 
LVL 37

Expert Comment

by:Jamie McKillop
ID: 39870782
Hello,

I suggest you read this article on transition your client access role. You need to create a legacy FQDN for your Exchange 2003 environment. You will need a new certificate for this.

http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx

-JJ
0
 
LVL 1

Author Comment

by:uscost
ID: 39870793
why do I need to do a legacy? I'm transitioning all of them over to exchange 2010. Everyone will use outlook 2007.

I was following this:
http://www.petenetlive.com/KB/Article/0000234.htm

They never mention anything about that.
0
 
LVL 37

Expert Comment

by:Jamie McKillop
ID: 39870813
Those instructions are for a swing migration. That means you plan on having an outage window and moving all your mailboxes at once. If that is your plan, as opposed to doing a transition over a period of time, then you will not need to use a legacy name.

-JJ
0
 
LVL 1

Author Comment

by:uscost
ID: 39870961
yeah, I'll be doing it over an outage window.
0
 
LVL 1

Author Comment

by:uscost
ID: 39873184
Anyone?
0
Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

 
LVL 37

Expert Comment

by:Jamie McKillop
ID: 39873239
With the exception of the legacy stuff, you just need to follow the instructions in the article I linked. Let me know if you have any specific questions.

-JJ
0
 
LVL 1

Author Comment

by:uscost
ID: 39873252
My questions were posted above. 1-5
0
 
LVL 37

Accepted Solution

by:
Jamie McKillop earned 500 total points
ID: 39873282
1. Yes, you need to switch inbound SMTP to point to your 2013 Hub transport server.
2. You don't need to change your DNS records as long as your firewall now points those IPs to the 2013 server.
3. Correct. For Activesync to work, your DNS record needs to be pointed at the 2013 server.
4. Correct. Same as above.
5. You seem to be missing an autodiscover record. Does your SSL cert include autodiscover.test.com or will you be using an SRV record?

-JJ
0
 
LVL 1

Author Comment

by:uscost
ID: 39873294
Not understanding #5.
Where is that located? On the T1 provider side?
0
 
LVL 37

Expert Comment

by:Jamie McKillop
ID: 39873307
With Exchange 2010, Outlook and Activesync use autodiscover to automatically configure the client. You need a DNS A record with the FQDN autodiscover.yourdomain.com that points to your Exchange server. You need a SAN SSL cert that includes both mail.yourdomain.com and autodiscover.yourdomain.com installed on your Exchange server. If you only have a cert that has mail.yourdomain.com, you can create an SRV record in DNS that points Outlook autodiscover to mail.yourdomain.com.

-JJ
0
 
LVL 1

Author Comment

by:uscost
ID: 39873312
oh ok, I already have the srv record for the dns already from the old exchange 2003.

Thank you.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

"Migrate" an SMTP relay receive connector to a new server using info from an old server.
Easy CSR creation in Exchange 2007,2010 and 2013
In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
To show how to generate a certificate request 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 Servers >> Certificates…

746 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

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now