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.

I should also note that when I receive the error listed above, after I click OK, I then get the window showing the Exchange Server and Mailbox Account settings.  The Exchange server is a long SID followed by mydomain.com

Could be a DNS issue- If you make the wrong changes to DNS, it can screw up authentication with certificates- I'm not familiar with the migration path from 2007 to 2013, but I would start with looking at the SAN's available on your certificate and compare those with your internal and external DNS- the fact that you are resolving to a SID seems odd to me. Just a suggestion: I'm not sure how you are testing, but you could save some time by making DNS changes for A, AAAA, and CNAME records to your local HOSTS file instead of waiting for DNS replication. I'll be watching this thread- Let us know what you find!

Back when I was testing OWA on my new servers, I made one temp change to DNS, which was just a CNAME record change to allow for internal OWA access via a different name.  I had already changed it back and was still having the issue.

Based on what you suggested though, I flushed the DNS cache on my workstation and tried again.  I now get an additional message error message, so I'm now getting....

....followed by......

"The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."

.....followed by......

I do see where it seems like it could be DNS.  However, my client workstations can all ping the servers by name.  I just don't get it.  I'm going to keep testing and investigating.  Thanks.

Okay, so a new discovery now.  I launch Outlook and I tell I want to manually configure my server settings.  I select "Microsoft Exchange Server or compatible service", It recognizes the mailbox account but leaves the "Server" box empty.  If I put my Exchange 2013 Server name in there and click the "Check Name" box, I still receive:

"The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."

However, if I put in my Exchange 2007 server name in and click the "Check Name" box, it then automatically changes and resolves to my 2013 Exchange server name, and I can then finish set up.

Again, I agree that it seems DNS related, but I still don't know where my problem lies.

You are getting certificate errors- is the CA that issued your Exchange certificate in the trusted root certification authorities store? Also double check your mx and srv records- I would double-check all things related to your DNS and CA configuration. You might also try with a fresh computer that has not been part of your test lab yet. Also, try the steps in this link and see if it helps: https://social.technet.microsoft.com/Forums/en-US/1cefdd59-c236-4723-be46-2bf2ebdb3907/outlook-no-resolving-exchange-server-name-resolving-another-name-like-sid-object?forum=exchangesvrclients

Have a look on below given earlier discussed thread that might helps you:

https://social.technet.microsoft.com/Forums/en-US/01d1e2bc-8eb4-4adb-96b2-7e21b7226e43/exchange-2007-to-exchange-2013?forum=exchangesvrdeploy

https://social.technet.microsoft.com/Forums/en-US/ebd0a1ab-19da-4379-897c-14cb32aa78f0/move-exchange-2010-mailbox-to-office-365-autodiscover-error?forum=onlineservicesexchange

Back when I was testing OWA on my new servers, I made one temp change to DNS, which was just a CNAME record change to allow for internal OWA access via a different name.  I had already changed it back and was still having the issue.

Based on what you suggested though, I flushed the DNS cache on my workstation and tried again.  I now get an additional message error message, so I'm now getting....

....followed by......

"The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."

.....followed by......

I do see where it seems like it could be DNS.  However, my client workstations can all ping the servers by name.  I just don't get it.  I'm going to keep testing and investigating.  Thanks.

Hi,

Please try to delete "=SMTP:" in Check Name box to have a try. If it doesn't work, please try to do the following changes in Exchange server:

1. Open ADSIEdit.
2. Connect to the Configuration container.
3. Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.
4. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
5. In the right hand pane you will see a list of databases.
6. Right-click the listed database object -> Properties.
7. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database, please clear the value.
8. Click OK.
9. Check the rest of the databases to make sure that they are not populated in the same way.

Then setup Exchange account in Outlook and check whether the issue persists.

Regards,

Winnie Liang -

I attempted both of these items.  Removing the =SMTP: from the front of the Mailbox name did not work.  

The msExchHomePublicMDB was pointed to my Exchange 2007 Server on all my 2013 DB's.  I cleared these all out and tried reloading a fresh profile.  

I still have the same issue in that autodiscover fails at the "Log on to Server" step, and when I do it manually, it fails when I enter my 2013 server name, but if I put in my Exchange 2007 server name in and click the "Check Name" box, it then automatically changes and resolves to my 2013 Exchange server name, and I can then finish set up.

• Edited by timahh2 16 hours 31 minutes ago

DanielM65536 -

I looked at this thread and ran the command to check the mailbox GUID.  That GUID is actually what is in the "Microsoft Exchange Server" field, (in the screenshot above).

Like I said though, previously I was able to resolve the Exchange 2013 server name and complete Autodiscovery.

The auto generated, Self-Signed Certificate was something that I would just install and that would be the last time I received that prompt for that e-mail profile as well.

I'll keep troubleshooting.  Thanks.

• Edited by timahh2 16 hours 32 minutes ago

Patrickjohn -

This first article looks like it might be a good reference.  I have already looked a little into my autodiscovery settings.  When I execute: Get-ClientAccessServer | FL AutoDiscoverServiceInternalUri, I receive:

AutoDiscoverServiceInternalUri : https://EXCHANGE2007.MYDOMAIN.lcl/autodiscover/autodiscover.xml

AutoDiscoverServiceInternalUri : https://EXCHANGE2013_1.MYDOMAIN.lcl/autodiscover/autodiscover.xml

AutoDiscoverServiceInternalUri : https://EXCHANGE2013_2.MYDOMAIN.lcl/autodiscover/autodiscover.xml

When I browse to all three of these Url's, I get the page(s), with the expected results:

<?xml version="1.0" encoding="UTF-8"?>
-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">-<Response>-<Error Id="402454776" Time="09:06:12.4002000"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>

I looked some more at that first article and ran the OutlookWebServices credential test.  (I ran this off of the 1st node of my Exchange 2013 server):

When it looks at itself as the ServiceEndpoint, it is successful.  My Exchange 2013 Node 2 has the same result.

I'll keep looking.  Thanks.

• Edited by timahh2 15 hours 47 minutes ago Discovery

To give a little more info on this, I've added some more screen captures.  Also, just to clarify, (for the subject of the Certificate), all the testing I'm doing for now is strictly internal.  I will eventually generate and load the external Certificate later on.

I do have an internal MX record that points to my Exchange 2007 server, but I don't think that this has anything to do with Autodiscover, correct?  I also have A records in DNS for all Exchange servers.

During the Outlook Autodiscover process, I've always received the internal certificate message, (which, like I said, I've always just been able to install one time and I would never get prompted again after the profile successfully loaded).

As you can see in the background, this is the step where it is still searching for the mailbox. I selected "Yes" on this Security Alert Cert message.

The next screen shot demonstrates, (I think), that the certificate is accepted and it found the mailbox.  You can see where the search for the mailbox step completes, (via the green check mark).  Now, the Log on to server step is where I receive the error.

I click OK on the error, (above), and I receive the window below:

Now, via the command in the screen shot below, you can see that its' GUID and the GUID in the "Microsoft Exchange Server" box, above, match.

Not sure if this is info is helpful in moving this toward a solution, but I thought it might be helpful to share.  Thanks.

Winnie Liang -

I attempted both of these items.  Removing the =SMTP: from the front of the Mailbox name did not work.  

The msExchHomePublicMDB was pointed to my Exchange 2007 Server on all my 2013 DB's.  I cleared these all out and tried reloading a fresh profile.  

I still have the same issue in that autodiscover fails at the "Log on to Server" step, and when I do it manually, it fails when I enter my 2013 server name, but if I put in my Exchange 2007 server name in and click the "Check Name" box, it then automatically changes and resolves to my 2013 Exchange server name, and I can then finish set up.

• Edited by timahh2 Wednesday, August 26, 2015 2:54 PM

DanielM65536 -

I looked at this thread and ran the command to check the mailbox GUID.  That GUID is actually what is in the "Microsoft Exchange Server" field, (in the screenshot above).

Like I said though, previously I was able to resolve the Exchange 2013 server name and complete Autodiscovery.

The auto generated, Self-Signed Certificate was something that I would just install and that would be the last time I received that prompt for that e-mail profile as well.

I'll keep troubleshooting.  Thanks.

• Edited by timahh2 Wednesday, August 26, 2015 2:53 PM

Patrickjohn -

This first article looks like it might be a good reference.  I have already looked a little into my autodiscovery settings.  When I execute: Get-ClientAccessServer | FL AutoDiscoverServiceInternalUri, I receive:

AutoDiscoverServiceInternalUri : https://EXCHANGE2007.MYDOMAIN.lcl/autodiscover/autodiscover.xml

AutoDiscoverServiceInternalUri : https://EXCHANGE2013_1.MYDOMAIN.lcl/autodiscover/autodiscover.xml

AutoDiscoverServiceInternalUri : https://EXCHANGE2013_2.MYDOMAIN.lcl/autodiscover/autodiscover.xml

When I browse to all three of these Url's, I get the page(s), with the expected results:

<?xml version="1.0" encoding="UTF-8"?>
-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">-<Response>-<Error Id="402454776" Time="09:06:12.4002000"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>

I looked some more at that first article and ran the OutlookWebServices credential test.  (I ran this off of the 1st node of my Exchange 2013 server):

When it looks at itself as the ServiceEndpoint, it is successful.  My Exchange 2013 Node 2 has the same result.

I'll keep looking.  Thanks.

• Edited by timahh2 Wednesday, August 26, 2015 3:38 PM Discovery

Been working on this all day today, but still cannot figure it out.

I ran the Test E-Mail Autoconfiguration tool on two different Outlook Clients.  The first one was my account that connects to the Exchange 2007 production server.  The second was my test mailbox that connects (but doesn't), to the Exchange 2013 Server(s).  The xml output is below:

From Outlook 2010 to Exchange 2007 Server (My account)

<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
  <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <User>
      <DisplayName>My Name</DisplayName>
      <LegacyDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=myusername</LegacyDN>
      <DeploymentId>a40518c8-4950-4a30-982a-a8a78c0f4442</DeploymentId>
    </User>
    <Account>
      <AccountType>email</AccountType>
      <Action>settings</Action>
      <Protocol>
        <Type>EXCH</Type>
        <Server>Exchange2007server.mydomain.lcl</Server>
        <ServerDN>/o=mydomain/ou=Exchange Administrative Group 

(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange2007server</ServerDN>
        <ServerVersion>72038053</ServerVersion>
        <MdbDN>/o=mydomain/ou=Exchange Administrative Group 

(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange2007server/cn=Microsoft Private MDB</MdbDN>
        <PublicFolderServer>Exchange2007server.mydomain.lcl</PublicFolderServer>
        <AD>DC2.mydomain.lcl</AD>
        <ASUrl>https://Exchange2007server.mydomain.lcl/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://Exchange2007server.mydomain.lcl/ews/exchange.asmx</EwsUrl>
        <OOFUrl>https://Exchange2007server.mydomain.lcl/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://Exchange2007server.mydomain.lcl/unifiedmessaging/service.asmx</UMUrl>
        <OABUrl>https://Exchange2007server.mydomain.lcl/oab/075648c3-cae6-4485-aec0-2c470955f50b/</OABUrl>
      </Protocol>
      <Protocol>
        <Type>EXPR</Type>
        <Server>wm.mydomain.com</Server>
        <SSL>On</SSL>
      </Protocol>
      <Protocol>
        <Type>WEB</Type>
        <Internal>
          <OWAUrl AuthenticationMethod="Basic, Fba">https://Exchange2013Server01.mydomain.lcl/owa</OWAUrl>
          <OWAUrl AuthenticationMethod="Basic, Fba">https://Exchange2013Server02.mydomain.lcl/owa</OWAUrl>
          <Protocol>
            <Type>EXCH</Type>
            <ASUrl>https://Exchange2007server.mydomain.lcl/ews/exchange.asmx</ASUrl>
          </Protocol>
        </Internal>
      </Protocol>
    </Account>
  </Response>
</Autodiscover>

From Outlook 2010 to Exchange 2013 Server (Test account)

<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
  <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <User>
      <DisplayName>Migration Test2</DisplayName>
      <LegacyDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=a4058e869623453a952a83bc64c6eeae-Migration Test2</LegacyDN>
      <AutoDiscoverSMTPAddress>MTest2@mydomain.com</AutoDiscoverSMTPAddress>
      <DeploymentId>a40518c8-4950-4a30-982a-a8a78c0f4442</DeploymentId>
    </User>
    <Account>
      <AccountType>email</AccountType>
      <Action>settings</Action>
      <MicrosoftOnline>False</MicrosoftOnline>
      <Protocol>
        <Type>EXCH</Type>
        <Server>fb3c225f-c4ae-4eb1-b449-46d2eb9499c9@mydomain.com</Server>
        <ServerDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=fb3c225f-c4ae-4eb1-b449-46d2eb9499c9@mydomain.com</ServerDN>
        <ServerVersion>73C08450</ServerVersion>
        <MdbDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=fb3c225f-c4ae-4eb1-b449-46d2eb9499c9@mydomain.com/cn=Microsoft Private MDB</MdbDN>
        <PublicFolderServer>wm.mydomain.com</PublicFolderServer>
        <AD>DC2.mydomain.lcl</AD>
        <AuthPackage>Anonymous</AuthPackage>
        <ASUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</EwsUrl>
        <EmwsUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</EmwsUrl>
        <EcpUrl>https://Exchange2013server02.mydomain.lcl/Ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=mydomain.lcl</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-sms>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-photo>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-extinstall>
        <OOFUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://Exchange2013server02.mydomain.lcl/ews/UM2007Legacy.asmx</UMUrl>
        <ServerExclusiveConnect>off</ServerExclusiveConnect>
      </Protocol>
      <Protocol>
        <Type>EXPR</Type>
        <Server>wm.mydomain.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Negotiate</AuthPackage>
        <ServerExclusiveConnect>on</ServerExclusiveConnect>
        <GroupingInformation>Default-First-Site-Name</GroupingInformation>
      </Protocol>
      <Protocol>
        <Type>WEB</Type>
        <Internal>
          <OWAUrl AuthenticationMethod="Basic, Fba">https://Exchange2013server01.mydomain.lcl/owa/</OWAUrl>
          <OWAUrl AuthenticationMethod="Basic, Fba">https://Exchange2013server02.mydomain.lcl/owa/</OWAUrl>
          <Protocol>
            <Type>EXCH</Type>
            <ASUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</ASUrl>
          </Protocol>
        </Internal>
      </Protocol>
      <Protocol>
        <Type>EXHTTP</Type>
        <Server>wm.mydomain.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Ntlm</AuthPackage>
        <ASUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</EwsUrl>
        <EmwsUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</EmwsUrl>
        <EcpUrl>https://Exchange2013server02.mydomain.lcl/Ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=mydomain.lcl</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-sms>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-photo>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=mydomain.lcl</EcpUrl-extinstall>
        <OOFUrl>https://Exchange2013server02.mydomain.lcl/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://Exchange2013server02.mydomain.lcl/ews/UM2007Legacy.asmx</UMUrl>
        <ServerExclusiveConnect>On</ServerExclusiveConnect>
      </Protocol>
      <Protocol>
        <Type>EXHTTP</Type>
        <Server>wm.mydomain.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Negotiate</AuthPackage>
        <ServerExclusiveConnect>On</ServerExclusiveConnect>
      </Protocol>
    </Account>
  </Response>
</Autodiscover>

Hi,

Generally, the error code 600 when you access the Autodiscover service URL in IE indicates that your Autodiscover can be connected successfully with this URL. Moreover, the new created Exchange 2013 user can connect to Exchange server successfully in Outlook. It should be working with Autodiscover service in Exchange 2013.

Please check your Outlook Anywhere configuration in Exchange 2013:

Get-OutlookAnywhere | FL

In client machine, please check the following settings in IE:

Click Settings > Internet Options > Connections > LAN settings, please make sure there is no proxy server set there. Only Automatically detect settings option is checked.

Additionally, please restart related Exchange services in server side. And run the Microsoft Remote Connectivity tool to test connectivity steps by steps:

https://testconnectivity.microsoft.com/

Regards,

Proxy Settings have always been Automatic.  Output from Get-OutlookAnywhere | FL is below:

RunspaceId                         : 339a34fd-2612-4a8a-b42c-d1243b7cccc7
ServerName                         : exchange2013server01
SSLOffloading                      : True
ExternalHostname                   : wm.mydomain.com
InternalHostname                   : exchange2013server01.mydomain.lcl
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://exchange2013server01.mydomain.lcl/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 1104.5)
Server                             : exchange2013server01
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web
                                     Site),CN=HTTP,CN=Protocols,CN=exchange2013server01,CN=Servers,CN=Exchange Administrative
                                     Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=mydomain,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=lcl
Identity                           : exchange2013server01\Rpc (Default Web Site)
Guid                               : b146303b-a847-4bf1-9f43-273ef7e639ef
ObjectCategory                     : mydomain.lcl/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 8/27/2015 8:56:31 AM
WhenCreated                        : 7/31/2015 12:04:28 PM
WhenChangedUTC                     : 8/27/2015 1:56:31 PM
WhenCreatedUTC                     : 7/31/2015 5:04:28 PM
OrganizationId                     :
Id                                 : exchange2013server01\Rpc (Default Web Site)
OriginatingServer                  : DC1.mydomain.lcl
IsValid                            : True
ObjectState                        : Changed

RunspaceId                         : 339a34fd-2612-4a8a-b42c-d1243b7cccc7
ServerName                         : exchange2013server02
SSLOffloading                      : True
ExternalHostname                   : wm.mydomain.com
InternalHostname                   : exchange2013server02.mydomain.lcl
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://exchange2013server02.mydomain.lcl/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 1104.5)
Server                             : exchange2013server02
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web
                                     Site),CN=HTTP,CN=Protocols,CN=exchange2013server02,CN=Servers,CN=Exchange Administrative
                                     Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=mydomain,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=lcl
Identity                           : exchange2013server02\Rpc (Default Web Site)
Guid                               : 99df3a85-4f77-4ca9-9665-4e90da502366
ObjectCategory                     : mydomain.lcl/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 8/25/2015 12:17:39 PM
WhenCreated                        : 7/31/2015 1:24:28 PM
WhenChangedUTC                     : 8/25/2015 5:17:39 PM
WhenCreatedUTC                     : 7/31/2015 6:24:28 PM
OrganizationId                     :
Id                                 : exchange2013server02\Rpc (Default Web Site)
OriginatingServer                  : DC1.mydomain.lcl
IsValid                            : True
ObjectState                        : Changed



[PS] C:\Windows\system32>

I keep coming back to this being a DNS issue, (as DanielM65536 indicated as well).  The reason being is because of the auto-name change that happens when I put my Exchange 2007 server name in, and it is then automatically changed\resolved to my Exchange 2013 server name.

So, just to recap what's currently happening:

The first thing is that during autodiscover I receive:

Second, after clicking OK on the error above, I receive:

From there, I modify the Microsoft Exchange Server field and put my Exchange 2013 Server name in there and change the Mailbox field to the correct syntax:

I then receive, again, the error message:

"The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."

From there, I modify the Microsoft Exchange Server field and put my Exchange 2007 Server name in.  

When I click apply on the box above, it automatically changes the name to my Exchange 2013 server, but this time successfully resolves, and I can then load the the email profile:

As a side note, (and this has to be related to this problem, but I think when I fix one issue, the other will follow), mail flow between the two Exchange 2013 servers is working fine.  However, mail flow between the 2013 and 2007 servers fails.  

These commands were run from one of my Exchange 2013 nodes:

[PS] C:\Windows\system32>Test-Mailflow


RunspaceId         : 680d540c-1144-43c4-9780-caca68b20b82
TestMailflowResult : Success
MessageLatencyTime : 00:00:07.2357238
IsRemoteTest       : False
Identity           :
IsValid            : True
ObjectState        : New



[PS] C:\Windows\system32>Test-Mailflow exchange2013server02 -TargetMailboxServer exchange2013server01


RunspaceId         : 680d540c-1144-43c4-9780-caca68b20b82
TestMailflowResult : Success
MessageLatencyTime : 00:00:05.3064897
IsRemoteTest       : True
Identity           :
IsValid            : True
ObjectState        : New



[PS] C:\Windows\system32>Test-Mailflow exchange2013server02 -TargetMailboxServer exchange2007server


RunspaceId         : 680d540c-1144-43c4-9780-caca68b20b82
TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest       : True
Identity           :
IsValid            : True
ObjectState        : New

Also, I can set up this test Exchange 2013 account on an iPhone and email back and forth between it and another mailbox on the Exchange 2013 Server.

However, I cannot access the GAL from Outlook for either of these mailboxes that reside on the Exchange 2013 Servers.

Thoughts?

• Edited by timahh2 15 hours 53 minutes ago Info Update

I keep coming back to this being a DNS issue, (as DanielM65536 indicated as well).  The reason being is because of the auto-name change that happens when I put my Exchange 2007 server name in, and it is then automatically changed\resolved to my Exchange 2013 server name.

So, just to recap what's currently happening:

The first thing is that during autodiscover I receive:

Second, after clicking OK on the error above, I receive:

From there, I modify the Microsoft Exchange Server field and put my Exchange 2013 Server name in there and change the Mailbox field to the correct syntax:

I then receive, again, the error message:

"The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action."

From there, I modify the Microsoft Exchange Server field and put my Exchange 2007 Server name in.  

When I click apply on the box above, it automatically changes the name to my Exchange 2013 server, but this time successfully resolves, and I can then load the the email profile:

As a side note, (and this has to be related to this problem, but I think when I fix one issue, the other will follow), mail flow between the two Exchange 2013 servers is working fine.  However, mail flow between the 2013 and 2007 servers fails.  

These commands were run from one of my Exchange 2013 nodes:

[PS] C:\Windows\system32>Test-Mailflow


RunspaceId         : 680d540c-1144-43c4-9780-caca68b20b82
TestMailflowResult : Success
MessageLatencyTime : 00:00:07.2357238
IsRemoteTest       : False
Identity           :
IsValid            : True
ObjectState        : New



[PS] C:\Windows\system32>Test-Mailflow exchange2013server02 -TargetMailboxServer exchange2013server01


RunspaceId         : 680d540c-1144-43c4-9780-caca68b20b82
TestMailflowResult : Success
MessageLatencyTime : 00:00:05.3064897
IsRemoteTest       : True
Identity           :
IsValid            : True
ObjectState        : New



[PS] C:\Windows\system32>Test-Mailflow exchange2013server02 -TargetMailboxServer exchange2007server


RunspaceId         : 680d540c-1144-43c4-9780-caca68b20b82
TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest       : True
Identity           :
IsValid            : True
ObjectState        : New

Also, I can set up this test Exchange 2013 account on an iPhone and email back and forth between it and another mailbox on the Exchange 2013 Server.

However, I cannot access the GAL from Outlook for either of these mailboxes that reside on the Exchange 2013 Servers.

Thoughts?

• Edited by timahh2 Thursday, August 27, 2015 3:34 PM Info Update