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

Exchange 2010 migration to Exchange 2013 on Premise

I have our current Exchange 2010 on SBS2011 Co-existing with the new Exchange 2013 On Premise Installed and followed the Configuration steps but I cannot get our OWA Externally go to the New Exchange 2013 OWA, any guidance and troubleshooting information would be greatly appreciated.
0
dtssupport
Asked:
dtssupport
  • 7
  • 6
1 Solution
 
Will SzymkowskiSenior Solution ArchitectCommented:
Have you got the correct cert in place and verified that you have updated your URL of your OWA virtual directories for both Exchnage 2010 and Exchange 2013?

Your Exchange Cert should have the following SAN names
- autodiscover.domain.com
- mail.domain.com
- legacy.domain.com

Using legacy.domian.com for all of the virtual directories on Exchange 2010 and using mail.domain.com for all virtual directories on Exchange 2013.

Once this is in place you will only have to use mail.domain.com to access OWA and if the mailbox resides on Exchange 2010 it will redirect you automatically to the legacy.domain.com and log you into your mailbox (exchange 2010). For mailboxes that are already on Exchange 2013 it will go directly into the mailbox.

Will.
0
 
dtssupportAuthor Commented:
Thx Will,

I have multiple Certs listed and there are all valid and I have one that has all of the ones you listed.
Autodiscover. domain.com
mail.domain.com
legacy.domain.com

I also created a send and receive connector on the New Exchange 2013 server and now I am getting an internal pop up with the Outlook 2013 about the Security Cert and it's the one we imported from the SBS2011 Exchange 2010 Server.
0
 
dtssupportAuthor Commented:
From externally if I type in https://legacy.domain.com/owa or https://mail.domain.con/owa still pulls up the 2010 OWA
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Will SzymkowskiSenior Solution ArchitectCommented:
You can import a cert on an Exchange server with no issues. You need need to assign the Cert on the Exchange server with the appropriate services.

Go to the Exchange server where the cert is installed
- open the EMS
- Type Get-ExchangeCertificate (you should see your exchange cert listed there)
- Type Enable-ExchangeCertificate -Thumbprint "thumbprint of your cert" -services "smtp,iis,pop,imap"
- This cert now becomes the default cert that will be used

Also when you are getting that popup what cert is it mapped to?

Will.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
If you type legacy.domain.com it should go directly to your OWA login page for 2010. If you type mail.domain.com it should go to 2013 OWA.

I would start by making sure your cert assignment is correct and then going through and checking all of your URL for all of your virtual directories. Also for External Access.

Will.
0
 
dtssupportAuthor Commented:
it was mapped to the imported Certificate from the SBS2011 Exchange 2010 Server, I just enabled the one that I had created on the New Exchange Server and includes all of the Services and this one has all of the Autodiscover.domain.com, Mail.domain.com, legacy.domain.com
smtp, iis, pop, imap........ rebooted Exchange Server and https: 443 is showing the new cert, but OWA External still going to 2010 OWA....I sure there has to be some other steps, any ideas>?
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Have you created External DNS pointers to point to the new Exchange server? I am assuming that is what the issue is. Do you have split DNS (Internal AD Domain and External Domain Zones access internally?) If you do does it work internally and just not when you are on the internal domain network?

Will.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Your OWA externally needs to be accessible on the new server and it is pointing to the old 2010 Exchange still. Which is why it is going directly to your old 2010 server when you are using mail.domain.com

WIll.
0
 
dtssupportAuthor Commented:
I have all the Virtual Directories pointed correctly unless there is a firewall setting that has to change?
0
 
dtssupportAuthor Commented:
OWA is accessible on the new Server internally, just not externally!
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Have you configured your firewall rules to point to your new Exchange 2013 server? You should have your external IP which for mail.domain.com NAT'ed through your firewall to the new server. It is still pointing to your old 2010 server.

This is what needs to be changed.

Will.
0
 
dtssupportAuthor Commented:
I don't believe I will have time currently to keep this ticket open and will have to work on it later, as will work to resolve the issue thank you
0
 
dtssupportAuthor Commented:
Could not come up with a solution and ran out of time to leave this question up with no activity
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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