I currently have a production bare metal Windows 2008 Std SP2 running Exchange 2007 (with the proper update for migration to 2013). I have two Exchange 2013 Std CU9 servers up and running on Windows 2012 DC. DAG is configured and working.
At one point, I created a couple of new test mailboxes on the new servers and their respective databases and connect to them without issue. I was also able to create a couple of test mailboxes on my Exchange 2007 server, migrate and then connect to them successfully as well. I am planning a full migration this coming weekend.
In doing some lead work, I have managed to now create an issue with, (I believe), my virtual directories on my Exchange 2013 servers, namely Autodiscover. (NOTE: Exchange 2007 server is still working fine).
When I now try and launch Outlook, (v.2010), for a mailbox that connects to a database on the new 2013 servers, Autodiscover does not complete. It detects the e-mail account, I get a prompt about my local certificate and I reply "Yes" to continue. However, at the last step to "Log on to the server" I receive the error:
"The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I can log on to this account's OWA just fine. With that, I suspect that I messed something up with regards to the Autodiscover virtual directory. I tried putting it back to the default and resetting IIS, but I receive the same errors within Outlook.
I was reading this article that references Autodiscover using the oldest Exchange Server within the domain.
https://social.technet.microsoft.com/Forums/office/en-US/484604a9-d2e3-4a1b-8ac2-8d8c700e8957/outlook-does-not-connect-to-exchange-2013-after-name-change-due-to-marriage?forum=exchangesvrclients
However, this was working fine for me previously, so I'm stumped.
Any help would be greatly appreciated, and let me know any additional info needed. Thanks.