Hi,

Please confirm whether the issue happens to all users or specific users to narrow the issue to client side or server side.

If the issue occurs on all users, we could run the following command to check the autodiscover service.

Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri

In Exchange server, please run the following command to check your new certificate settings:

Get-ExchangeCertificate | fl

Meanwhile, I suggest you can do an Outlook connectivity test with https://testconnectivity.microsoft.com/   and see what went wrong.

If the issue occurs on a specific user, I suggest you can create a new profile to test.

Best Regards,

David

Hi,

Please confirm whether the issue happens to all users or specific users to narrow the issue to client side or server side.

If the issue occurs on all users, we could run the following command to check the autodiscover service.

Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri

In Exchange server, please run the following command to check your new certificate settings:

Get-ExchangeCertificate | fl

Meanwhile, I suggest you can do an Outlook connectivity test with https://testconnectivity.microsoft.com/   and see what went wrong.

If the issue occurs on a specific user, I suggest you can create a new profile to test.

Best Regards,

David

Hello,

We are having problems getting Outlook 2013 to connect to Exchange 2013 internally.

We have already replaced the certificates and use a Certificate Authority to sign the certificates. Outlook can autodiscover fine but then throws an error saying: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

I then get a screen with address: fdcbfb4f-2b54-4a3d-aa6e-4d411d5ad8d6@domain.com as the Exchange server.

Mailbox: =SMTP:Administrator@domain.com

The mailbox exists and OWA just works fine. Any tips are very welcome

Thanks,

Jason

What you're seeing is the GUID of the mailbox server which is normal.  Use this TechNet article to help you troubleshoot the connection issues.  https://technet.microsoft.com/en-us/library/dd638082(v=exchg.150).aspx Let us know if you need further assistance.

What you're seeing is the GUID of the mailbox server which is normal.  Use this TechNet article to help you troubleshoot the connection issues.  https://technet.microsoft.com/en-us/library/dd638082(v=exchg.150).aspx Let us know if you need further assistance.

Hello

check new certificate included domain name. need same new cert  as old.

Hello

check new certificate included domain name. need same new cert  as old.

did you ever disable Outlook Anywhere on your users?  If so it has to be enabled for users to be able to connect to Exchange 2013.  Another thing to check is to make sure your OutlookAnywhere internal host name resolves to your 2013 server (or VIP).  

Get-outlookanywhere -Server <2013Server> | fl servername, *hostname*

did you ever disable Outlook Anywhere on your users?  If so it has to be enabled for users to be able to connect to Exchange 2013.  Another thing to check is to make sure your OutlookAnywhere internal host name resolves to your 2013 server (or VIP).  

Get-outlookanywhere -Server <2013Server> | fl servername, *hostname*

Make sure your Outlook 2013 clients are updated with the latest SP and Patches. There were a lot of updates released since Office 2013 was released that address authentication and connectivity issues with Exchange 2013.  You can also go to the testexchangeconnectivity.com website and download a client based testing tool to check client connectivity and configuration in your environment.

Make sure your Outlook 2013 clients are updated with the latest SP and Patches. There were a lot of updates released since Office 2013 was released that address authentication and connectivity issues with Exchange 2013.  You can also go to the testexchangeconnectivity.com website and download a client based testing tool to check client connectivity and configuration in your environment.