I recently set up an Exchange 2013 server in order to migrate our Exchange 2007 mailboxes over. In DNS I have a 'mail' ecord that points to our new Exchange 2013 server. I also created a 'legacy' record that points to the 2007 server. We also have
a local CA and I generated an exchange certificate with this CA and installed in the 2013 Exchange server. Autodiscover SEEMS to be working. Errors I get:
On a migrated account - using Outlook to create a brand new profile-
"Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
On an account that only exists on the new Exchange 2013 box - new profile:
'The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
In OWA:
Trying to login with the Exchange 2013 only account it seems to try and login, sits and thinks about it for awhile and then the URL switches to the legacy URL. The login obviously fails with a "This page cannot be displayed" error.
Note from above the DNS alias 'mail' is the new server. So if I ping 'mail' I get replies from new server, nslookup shows new server also. But if I do :
nslookup mail.my.domain.name
it fires back :
Name: mail.my.domain.name.my.domain.name
Address: <address of OLD 2007 Exchange>
I would think this nslookup would show the NEW Exchange 2013 machine?
PLEASE HELP! If you need for information I will do my best!
Migration from Exchange 2007 to Exchange 2013 - Outlook cannot connect and OWA always redirects to legacy
June 4th, 2015 3:58pm
Put a period at the end of the nslookup command.
nslookup mail.my.domain.name.
Have you configured Autodiscover?
Enter this command and be sure the URL is correct:
Get-ClientAccessServer | FL Name,AutodiscoverServiceInternalUri
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2015 4:46pm
Hello Alan,
DNS Records
Legacy.domain.com point to exchange 2007
Mail.domain.com Point to Exchange 2013
Autodiscover.domain.com point to Exchange 2013
========================================
Exchange Virtual Directories
----------------Exchange Web services--------------------
******2007 (internally and Externally)******
https://legacy.domain.com/EWS/Exchange.asmx
******2013 (Internally and Externally)******
https://Mail.domain.com/EWS/Exchange.asmx
----------------Outlook Anywhere--------------------
2007 and 2013 (same values) outlook anywhere must be point to 2013
******Internal and External URLs******
mail.domain.com
******IISAuthenticationMethods:******
Basic,NTML
******ExternalClientAuthenticationMethods: ******Basic
----------------Autodiscover URI--------------------
******Exchange 2007 and 2013 (Internally and Externally)******
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
----------------Activsync--------------------
******Exchange 2007******
******Internal ******
https://legacy.domain.com/Microsoft-Server-ActiveSync
******External******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/Microsoft-Server-ActiveSync
----------------ECP--------------------
******Exchange 2007 (Internally and Externally)******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/ecp
----------------OWA--------------------
******Exchange 2007 (Internally and Externally)******
https://legacy.domain.com/owa
******Exchange 2013 (Internally and Externally)******
https://Mail.domain.com/owa
===================================================
******Certificate must be contains ******
Legacy.domain.com
Domain.domain.com
Autodiscovry.domain.com
Thanks
Reference
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Edited by Abdelrahman M-Attia 17 hours 53 minutes ago format
June 5th, 2015 9:35am
Hello Alan,
DNS Records
Legacy.domain.com point to exchange 2007
Mail.domain.com Point to Exchange 2013
Autodiscover.domain.com point to Exchange 2013
========================================
Exchange Virtual Directories
----------------Exchange Web services--------------------
******2007 (internally and Externally)******
https://legacy.domain.com/EWS/Exchange.asmx
******2013 (Internally and Externally)******
https://Mail.domain.com/EWS/Exchange.asmx
----------------Outlook Anywhere--------------------
2007 and 2013 (same values) outlook anywhere must be point to 2013
******Internal and External URLs******
mail.domain.com
******IISAuthenticationMethods:******
Basic,NTML
******ExternalClientAuthenticationMethods: ******Basic
----------------Autodiscover URI--------------------
******Exchange 2007 and 2013 (Internally and Externally)******
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
----------------Activsync--------------------
******Exchange 2007******
******Internal ******
https://legacy.domain.com/Microsoft-Server-ActiveSync
******External******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/Microsoft-Server-ActiveSync
----------------ECP--------------------
******Exchange 2007 (Internally and Externally)******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/ecp
----------------OWA--------------------
******Exchange 2007 (Internally and Externally)******
https://legacy.domain.com/owa
******Exchange 2013 (Internally and Externally)******
https://Mail.domain.com/owa
===================================================
******Certificate must be contains ******
Legacy.domain.com
Domain.domain.com
Autodiscovry.domain.com
Thanks
Reference
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Edited by Abdelrahman M-Attia Friday, June 05, 2015 1:35 PM format
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2015 1:33pm
Hello Alan,
DNS Records
Legacy.domain.com point to exchange 2007
Mail.domain.com Point to Exchange 2013
Autodiscover.domain.com point to Exchange 2013
========================================
Exchange Virtual Directories
----------------Exchange Web services--------------------
******2007 (internally and Externally)******
https://legacy.domain.com/EWS/Exchange.asmx
******2013 (Internally and Externally)******
https://Mail.domain.com/EWS/Exchange.asmx
----------------Outlook Anywhere--------------------
2007 and 2013 (same values) outlook anywhere must be point to 2013
******Internal and External URLs******
mail.domain.com
******IISAuthenticationMethods:******
Basic,NTML
******ExternalClientAuthenticationMethods: ******Basic
----------------Autodiscover URI--------------------
******Exchange 2007 and 2013 (Internally and Externally)******
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
----------------Activsync--------------------
******Exchange 2007******
******Internal ******
https://legacy.domain.com/Microsoft-Server-ActiveSync
******External******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/Microsoft-Server-ActiveSync
----------------ECP--------------------
******Exchange 2007 (Internally and Externally)******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/ecp
----------------OWA--------------------
******Exchange 2007 (Internally and Externally)******
https://legacy.domain.com/owa
******Exchange 2013 (Internally and Externally)******
https://Mail.domain.com/owa
===================================================
******Certificate must be contains ******
Legacy.domain.com
Domain.domain.com
Autodiscovry.domain.com
Thanks
Reference
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Edited by Abdelrahman M-Attia Friday, June 05, 2015 1:35 PM format
June 5th, 2015 1:33pm
Hello Alan,
DNS Records
Legacy.domain.com point to exchange 2007
Mail.domain.com Point to Exchange 2013
Autodiscover.domain.com point to Exchange 2013
========================================
Exchange Virtual Directories
----------------Exchange Web services--------------------
******2007 (internally and Externally)******
https://legacy.domain.com/EWS/Exchange.asmx
******2013 (Internally and Externally)******
https://Mail.domain.com/EWS/Exchange.asmx
----------------Outlook Anywhere--------------------
2007 and 2013 (same values) outlook anywhere must be point to 2013
******Internal and External URLs******
mail.domain.com
******IISAuthenticationMethods:******
Basic,NTML
******ExternalClientAuthenticationMethods: ******Basic
----------------Autodiscover URI--------------------
******Exchange 2007 and 2013 (Internally and Externally)******
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
----------------Activsync--------------------
******Exchange 2007******
******Internal ******
https://legacy.domain.com/Microsoft-Server-ActiveSync
******External******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/Microsoft-Server-ActiveSync
----------------ECP--------------------
******Exchange 2007 (Internally and Externally)******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/ecp
----------------OWA--------------------
******Exchange 2007 (Internally and Externally)******
https://legacy.domain.com/owa
******Exchange 2013 (Internally and Externally)******
https://Mail.domain.com/owa
===================================================
******Certificate must be contains ******
Legacy.domain.com
Domain.domain.com
Autodiscovry.domain.com
Thanks
Reference
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Edited by Abdelrahman M-Attia Friday, June 05, 2015 1:35 PM format
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2015 1:33pm
Hello Alan,
DNS Records
Legacy.domain.com point to exchange 2007
Mail.domain.com Point to Exchange 2013
Autodiscover.domain.com point to Exchange 2013
========================================
Exchange Virtual Directories
----------------Exchange Web services--------------------
******2007 (internally and Externally)******
https://legacy.domain.com/EWS/Exchange.asmx
******2013 (Internally and Externally)******
https://Mail.domain.com/EWS/Exchange.asmx
----------------Outlook Anywhere--------------------
2007 and 2013 (same values) outlook anywhere must be point to 2013
******Internal and External URLs******
mail.domain.com
******IISAuthenticationMethods:******
Basic,NTML
******ExternalClientAuthenticationMethods: ******Basic
----------------Autodiscover URI--------------------
******Exchange 2007 and 2013 (Internally and Externally)******
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
----------------Activsync--------------------
******Exchange 2007******
******Internal ******
https://legacy.domain.com/Microsoft-Server-ActiveSync
******External******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/Microsoft-Server-ActiveSync
----------------ECP--------------------
******Exchange 2007 (Internally and Externally)******
Null
******Exchange 2013 (Internally and Externally)******
https://mail.domain.com/ecp
----------------OWA--------------------
******Exchange 2007 (Internally and Externally)******
https://legacy.domain.com/owa
******Exchange 2013 (Internally and Externally)******
https://Mail.domain.com/owa
===================================================
******Certificate must be contains ******
Legacy.domain.com
Domain.domain.com
Autodiscovry.domain.com
Thanks
Reference
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Edited by Abdelrahman M-Attia Friday, June 05, 2015 1:35 PM format
June 5th, 2015 1:33pm
Hi,
Hope this blog will be helpful for you.
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2015 9:36pm
Okay I have an update. If I generate a brand new account in AD and create a brand new mailbox in Exchange 2013 OWA will open the mailbox without redirecting to the legacy URL.
But my question is why is OWA redirecting to legacy on the migrated account? What is the actual mechanism that is doing the redirection? Do I have URL's wrong??
Please explain to me a little, driving me crazy. Thanks in advance. Also thank you for the suggestions.
...AR
June 22nd, 2015 3:41pm
If it's redirecting to legacy, then Exchange 2013 thinks the mailbox is still on the legacy server. Look in ADSI Edit for the msExchHomeMDB property.
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 3:46pm
May be in Router setup, public IP is pointing to the old server...
Regards,
Joby
June 22nd, 2015 3:53pm
If it's redirecting to legacy, then Exchange 2013 thinks the mailbox is still on the legacy server. Look in ADSI Edit for the msExchHomeMDB
Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2015 2:30pm
Sorry, I was posting from memory. The property is "homeMDB".
June 23rd, 2015 3:36pm
No, account is on the 2013 server/database. Verified this 2 ways.
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 1:57pm
Have you run Outlook's Test E-mail Autoconfiguration? What are the connection settings showing there?
June 25th, 2015 2:07pm
Also, does the user's profile try to open other mailboxes that haven't been moved to Exchange 2013?
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 2:08pm
SIr,
I can't even create a profile for my new test user whose mailbox was created on Exchange 2013. Outlook 2013 gives me:
On an account that only exists on the new Exchange 2013 box - new profile:
'The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
Don't see how I can test connectivity. Autodiscover fills in the profile fine but it then fails when trying to search for/log in the user. I tried adding the DS Server value to HKCU Exchange Provider using FQDN but no luck.
If a new account doesn't work then a migrated account is not my biggest problem.
Thank you again.
June 26th, 2015 9:03am
ALSO - more information
Autodiscover fills in the information correctly, here is the sequence on the "searching your mail server settings" page in outlook:
OK Establishing network connection
OK Searching for Benny.Hill@mail.mydomain.com
FAIL Logging on to the mail server
then a popup
'The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
'mail' in DNS points to the new mail server, hence Exchange 2013.
--AR
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2015 9:16am
Sorry to bother you with all this.
On certificates. Our network is a closed network with no Internet connection. We have a local CA server on which I processed the certificate request for the Exchange server. So my question is does this certificate need to be on the workstations? OR, do I need a certificate on the workstations and if so which one?
I am not well versed in certs yet.
...AR
June 26th, 2015 9:36am
The workstations need to trust that certificate. If they trust your CA's root, then that should be enough. You can tell whether it's trusted easily enough by opening OWA and seeing whether you get the certificate warning.
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2015 4:13pm
Exchange 2013 requires Outlook Anywhere.
Again, have you run Outlook's Test E-mail Autoconfiguration?
June 26th, 2015 4:15pm
Exchange 2013 requires Outlook Anywhere.
Again, have you run Outlook's Test E-mail Autoconfigur
Free Windows Admin Tool Kit Click here and download it now
June 30th, 2015 8:55am
I can't say. You posted your URLs above and if mail.domain.com points to the Exchange 2013 server, that server has a certificate trusted by the client that matches that name, and Outlook is a supported version, it should just work.
June 30th, 2015 1:23pm
Ed,
I used OWA and got no certificate error. In doing more searching I tried using the certificates mmc and noted the Exchange certificate is not under Certificates\Personal\Certificates. In fact there is no certificates folder under Personal, if that's relevant at all.
Never mind. Didn't take the info I had far enough. The CA looks to be trusted. So I am still at a loss. No idea where to go right now.
- Edited by AlanRaczek 11 hours 26 minutes ago
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2015 3:57pm
This topic is archived. No further replies will be accepted.
Other recent topics
