Its late to post reply on issue face by Luke, but in my case similar issue in which Outlook Profile does not get configured and shows =SMTP:user@domain.com.
I had to set “Default offline address book” to the Exchange 2013 Address Book on the database where users mailbox is.

Thanks for great helping articles all the time.

we need one help we are in process of migrating users from EX2k7 to EX2K13 everything seems to be working fine except IMAP and POP.

we have exchange server roles installed on different host not multi role servers. when we are trying to set imap setting and change internal and external URLs its showing error ” The ExternalConnectionSettings property is read-only when the Mailbox role: Mailbox service server role is installed.”

Please help as when we are trying to configure outlook with IMAP its getting error “Log on to incoming mail server failed (IMAP). The connection to server was interrupted.

Regards
Vikas Bhadauria

As far as I’ve seen, wildcards will generally work just fine without doing those steps.

With Wildcard, Did I should apply the following two commands, or it is optional:

Set-OutlookProvider EXPR -CertPrincipalName ” msstd : * demain.com . ”

Set-OutlookProvider EXCH -CertPrincipalName msstd ” msstd : * demain.com . “

Hi Paul,
I have a WildCard Certificate
When I recycle AppPool of Autodiscover & OAB & RpcProxy the prompt for Credential disappear
I hope that the problem will not happen again
Many Thank’s Paul

That often means one of the URLs or namespaces being used is not included on the SSL certificate on the server.

Below my Server Configuration

# Outlook Anywhere Configuration

InternalHostname : mail.domain.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Basic, Ntlm}
SSLOffloading : False

# AutoDiscover Configuration

Identity : E15Node1
AutoDiscoverServiceInternalUri : https://mail.domain.com/Autodiscover/Autodiscover.xml

# WebServices Configuration

InternalUrl : https://mail.domain.com/EWS/Exchange.asmx
ExternalUrl : https://webmail.domain.com/EWS/Exchange.asmx
CertificateAuthentication :
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
OAuthAuthentication : True
AdfsAuthentication : False

I am in Coexistance phase, and when I applying instruction guide page 37, Launching Outlook 2013 Prompting password appear each time
Is there a mismatch Configuration ?

Many Thank’s Paul.

The Autodiscover SCP URL is only for the Autodiscover service that clients connect to and query so they can discover the settings they should be using for things like Outlook Anywhere, Exchange Web Services, ActiveSync, the Offline Address Book and so on.

As a HTTPS service, as long as the Autodiscover SCP URL you’ve configured is included on the SSL certificate on any Client Access server that the Autodiscover SCP URL resolves to in DNS then there should be no problems or surprises.

The CAS Array name is not changed at any point during the migration.

I am just wondering if the provisioned Outlook clients will detect this change and update their server name automatically or will I need to do this manually.

Currently they are still using the old URL. Does the CAS Array URL need to be changed also to have the Outlook clients on EX2010 update their server URL?