Unable to create outlook profile manually

Hello,

I have two Exchange 2013 Servers with combined roles with DAG configured. I am not using any cas server load balancer. I created manual entries of AutoDiscover pointing to one of the Exchange server. Now I am able to create Outlook 2013 profile automatically through AutoDiscover and there is no problem (Even with automatically configuration it is giving strange server name like 81038b66-57d8-44d1-abd6-f243e85fe7db@abc.com)

BUT when I try to create any user profile manually by giving one of the Exchange Server name, It gives me an error message

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

Kindly anyone please guide me where is the problem?

Thanks in advance.


  • Edited by Sawag 16 hours 56 minutes ago
March 31st, 2015 9:41am

Hello

are you set exch proxy in outlook?

like msstd: and https:// ?

Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 9:47am

Hi

Please check outlook connectivity test using below url and update me the status. make sure you are testing both outlook connectivity and outlook autodiscover.

https://testconnectivity.microsoft.com

Thanks and regards

Bobson

March 31st, 2015 10:32am

yes I set the proxy but in my Outlook connection setting it is showing strange server name

see the snapshot

Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 10:52am

yes I set the proxy but in my Outlook connection setting it is showing strange server name

see the snapshot

That's by design.  Exchange 2013 no longer uses a common name (like a CASArray or common namespace) to connect directly to the mailbox.  It now uses the MailboxGUID@domain.com to have Outlook connect to the Exchange Server.  It will still use the Outlook Anywhere address to connect to the CAS Server, but the server name will always be that GUID. 

The best way to configure the Outlook Profile is to let Autodiscover handle the profile creation.  if for what ever reason you can not (really there isn't a compelling reason why), then you need to obtain the ExchangeGUID from Powershell.  You can use:

Get-Mailbox -Identity <username> | fl identity, ExchangeGUID
to get that information.  Again, Autodiscover is the easiest and painless way to go.

March 31st, 2015 12:57pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics