Internal Outlook / OWA / ECP not working post Exchange migration
Posted on 2016-10-09
I've hit a minor road block with my exchange migration. Currently, mail flow is 100%, and external OWA/AS devices all work fine. Internally, OWA errors to 503 on https://mail.domain.com/owa and https://mail.domain.com/ecp (even when you enter in the ?v=15...).
When trying to configure a fresh outlook profile in testing, I get the error of 'The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.' The dialog then pops up with the GUID@domain.com, with the mailbox referenced of =SMTP:firstname.lastname@example.org. I also generate an error of 'The action cannot be completed. The Connection to microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.'
Migration was from Ex2010 to Ex2013. All is fully patched. Ex2010 is complete uninstalled. All the virtual directories have entries, all names resolve internally with NSLOOKUP. I don't think split DNS is configured, but resolving these URL's and services was working with the prior exchange set up.
SRV, PTR etc. records exist for autodiscover, mail.domain.com records exist.
One odd stumbling block that I hit during the migration: When I tried to apply the SAN cert to Ex2013 from Godaddy using the import method (not the generate CSR -> upload to godaddy ->download -> import method) from the ellipses - it would say it successfully imported...and not appear in the exchange page of available certs. If you looked at the locally installed certs on MMC, it listed it with the correct thumbprint. I couldn't get that to work at all, so I resorted to exporting the cert from Ex2010 and importing the CRX/PFX (sp?) to EX2013. That worked successfully (but doesn't listed the most current names on the SAN, which I don't understand why that is).
Any further testing and ideas?