Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,

I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange 2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.

  • The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
  • How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
  • How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
  • Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.

Kindly guide if any thing missing that need to address during start the migration activity.

Thanks in Advance

January 23rd, 2015 9:13am

Hi ,

1.For your information send connector is an organisation wise component .On the existing send connector please add the exchange 2013 server on the source server field.So that emails coming exchange 2010 and exchange 2013 will go to outside world by using that existing send connector.

2.Yes , In exchange 2010 and exchange 2013 we can able to have the same URL'S.Same time you can easily configure the owa virtual directories in exchange 2010 EMC and for exchange 2013 in EAC.

3.For exchange 2013 at minimum you need the following namespaces in the SAN certificate.

autodiscover.domain.com

mail.domain.com

If you have those names then you can make use of the same SAN certificate in exchange 2013.

4.We cannot directly move the exchange 2010 database to exchange 2013 server.So the best way is to move anyone of the user mailbox to exchange 2013 and check the results.If everything is working fine then we can start moving the bulk mailboxes from exchange 2010 to exchange 2013.

Reference Links : 

http://exchangeserverpro.com/exchange-2010-to-exchange-2013-migration/

http://www.petenetlive.com/KB/Article/0000788.htm

Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2015 11:16am

Hello Nithyanandham,

Thanks for your valuable response. On point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?

Started few mailboxes migration on Exchange 2013 and faced different issues on users computers i.e.

  • Outlook 2007 SP3 disconnected and unable to connect to Exchange 2013 mailbox server on some users.
  • Some users facing issue on outlook prompt user and password every time
  • Certificate error on an every computer when opens outlook

I have migrated users have outlook 2007 SP3 and do not have any idea about the same issue will rise on outlook 2010 and 2013.

Please guide to resolve these issues.

January 23rd, 2015 11:04pm

Hi,

Can someone please respond on the above queries.

Thanks,

Free Windows Admin Tool Kit Click here and download it now
January 26th, 2015 7:44am

Hi ,

Sorry for delay.

Question : Thanks for your valuable response. On point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?

Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange 2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.

For mailbox connectivity issue in exchange 2013 :

1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange 2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.

2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.

3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover service is not reaching the proxy server if you have on your network.

In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.

4.please share me the output for the below mentioned command.

get-ClientAccessServer -Identity server name  | fl AutodiscoverServiceInternalURI 

5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.

6.On which operating system version those outlook 2007 clients are installed?

Please reply me if anything is un

January 26th, 2015 10:44am

Hi Nithyanandham,

Thanks for your quick response. I will share you the CMDlet out put later and for the client issue, some are on Windows XP and some are on Windows 7 and 8. Yes the outlook 2007 computers are fully patched with latest updates.

Free Windows Admin Tool Kit Click here and download it now
January 26th, 2015 12:38pm

Hi ,

Have you checked the remaining suggestions provided by me ?

For windows xp to work with exchange 2013 additionally we need to follow the below mentioned steps in the given article.

http://clintboessen.blogspot.in/2014/10/windows-xp-clients-must-match.html

January 26th, 2015 2:04pm

Hello Nithyanandham,

Thanks for your reply, I want little more clarification on the internal/external URL configuration.

Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange 2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.

How can I proxy both OWA from exchange 2010 to Exchange 2013 and other thing that need to consider is that on Exchange 2010 I am using trial Wildcard SSL certificate and have plan to buy new SAN SSL Certificate. On that scenario can I use  SAN SSL with trial Wildcard in coexistence between OWA and ActiveSync. Please guide the process to accomplish this task.

Thanks,

Free Windows Admin Tool Kit Click here and download it now
January 27th, 2015 8:25am

Hi ,

1.First of all proxying can be done only from exchange 2013 to exchange 2010 and it can't be done through exchange 2010 to exchange 2013.

I mean proxying can be only be possible from higher exchange exchange version to lower exchange version or else between the same exchange versions.

2.Once you install and enable the services by using the purchased SAN certificate in exchange 2010 and it will the overwrite the existing trial wildcard certificate so there is no need to worry. 

Note :  Make sure you are going to have all the required names in the SAN certificate which is going to be used for exchange 2010 and exchange 2013.

January 27th, 2015 8:44am

Thanks for your prompt reply,

You mean if I proxy the exchange 2013 to 2010 the user will access OWA from both directions. Exchange 2010 user will login on 2010 OWA and Exchange 2013 user will login on 2013 OWA. Do I need to change any internal URL in Exchange 2013 or 2010?

Thanks,

Free Windows Admin Tool Kit Click here and download it now
January 27th, 2015 9:09am

Hi,

yes, just try to have the same name for the internal url's in exchange 2010 as well as for exchange 2013.

Please reply me if you have any queries.

January 27th, 2015 9:16am

You mean should use same name on external and internal on both exchange 2010 and 2013 ?
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2015 10:50am

Hi ,

Yes that would be good and easy to remember.

January 27th, 2015 10:53am

Hi,

I am in serious problem during Exchange migration. Windows XP Users that moved on Exchange 2013 unable to connect with outlook 2007 SP3 with updates and frequent password prompt. Some XP users received message that Exchange is not available.  If try these users login on Win 7/8 machine with outlook 2010 from there also unable to connect. I don't know what happened with these users are not able to connect. I googled a lot but didn't find any solution to get resolve the issue.

Please help to get the proper solution.

Thanks 

Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2015 6:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics