Outlook 2010/2013 profile issues after installing Exchange 2016 RRS feed

  • Question

  • Exchange 2010/2013 coexistence environment:

    2 Exchange 2010 Multi-Role servers (Ex 2010 SP3 UR10):

    Exchange 2010 CAS Array points to Exchange 2010 CAS server (outlook.contoso.com)
    Exchange 2010 configured for Kerberos Auth

    2 Exchange 2013 Multi-Role servers (Ex 2013 CU10):

    Exchange 2013 Outlook Anywhere internal/external host name: mail.contoso.com (points to Exchange 2013 CAS)
    Exchange 2013 MAPI/HTTP not yet configured (Get-OrganizationConfig: MapiHttpEnabled: False)
    Exchange 2013 not yet configured for Kerberos Auth because of issue: https://support.microsoft.com/en-us/kb/2834139
    SCP: Set-ClientAccessServer <ex 2013 cas> -AutoDiscoverServiceInternalUri https://mail.contoso.com/Autodiscover/Autodiscover.xml

    No load balancers
    Split-DNS config

    Outlook clients:
    Outlook 2010 SP2 with latest updates connect to Exchange 2010 mailbox
    Outlook 2013 SP1 with latest updates connects to Exchange 2013 mailbox

    I have installed two Exchange 2016 Mailbox servers. Only changed SCP after installation:
    Set-ClientAccessServer <ex 2016 server> -AutoDiscoverServiceInternalUri https://mail.contoso.com/Autodiscover/Autodiscover.xml

    No mailboxes have been moved to Exchange 2016.


    Outlook 2010 Connection Status shows Proxy Server: <Exchange 2016 FQDN>

    After starting Outlook 2013:
    Credential window appears. After clicking on Cancel, Outlook 2013 shows ‘Need Password’. After clicking on ‘Need Password’, Outlook 2013 connects to Exchange without asking for credentials again.

    Tab Connection (Exchange Proxy Settings…) shows random URL https://mail.contoso.com or https://<ex-2016-fqdn>

    Outlook 2013 Connection Status shows random different names for Proxy Server:
    Proxy Server: <Exchange 2016 FQDN> or Proxy Server: mail.contoso.com

    Tested this also with new Exchange 2013 mailbox with the same issues.

    Friday, December 11, 2015 1:35 PM

All replies

  • Hi,

    Please check the outlook anywhere setting on exchange 2016 with the following command, especially the Internal/External hostname and post the result.

    Get-OultookAnywhere Server2016 | fl

    Best Regards.

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    TechNet Community Support

    Monday, December 14, 2015 10:04 AM
  • Hi,

    Outlook Anywhere is not configured yet on Exchange 2016 Mailbox servers and runs in default configuration:

    ExternalHostname: <empty>

    InternalHostname: <ex 2016 fqdn>

    Only changed SCP after installation (which points to Ex 2013 CAS):

    Set-ClientAccessServer <ex 2016 server> -AutoDiscoverServiceInternalUri https://mail.contoso.com/Autodiscover/Autodiscover.xml

    After installing Exchange 2016 you need time to configure & test Exchange 2016 functionality. Then, switch namespace to Exchange 2016 (Exchange 2010 coexistence) or add Exchange 2016 servers to load balancer.

    Monday, December 14, 2015 1:25 PM
  • I am able to reproduce this in another environment.

    After installing Exchange 2016 Mailbox Server, Outlook Connection Status shows Exchange 2016 fqdn as Proxy Server.

    No mailboxes moved to Exchange 2016.

    Monday, December 21, 2015 2:22 PM
  • You write that you have EX2010 RU10. But ex2010 is supported with minimum Ru11 together with 2016.Mybe it helps to update? For Outlook this update should be installed: KB2965295.


    Tuesday, January 5, 2016 12:43 PM
  • Exchange 2010 SP2 now runs with UR12

    Outlook 2010 SP2 was already up-to-date with latest updates. KB3114409 (8 dec 2015) was already installed. Ik think this one supersedes previous ones?

    When manually installing KB2965295 (14 april 2015) pop-up window: There are no products affected by this package installed on this system

    Still having the same OL profile issues with OL 2010 & 2013

    Wednesday, January 6, 2016 10:00 AM
  • I agree with you Martijn, we had the same issue today in a Customer project...; such situations should be avoided by the Exchange PG...

    See also: http://blogs.technet.com/b/exchange/archive/2015/11/18/exchange-ad-deployment-site.aspx

    Tuesday, January 12, 2016 5:38 PM
  • Hi Guys,

    I'll be doing this soon so interested in any solutions. I can't do a deployment site as referenced in the blog, I think I will be the position as Martijn and Steffen.

    so is the solution just to update the 2010 server internaluris to point to the 2016 server quickly and hope it works?

    David Hood www.consilium-uk.com

    Wednesday, February 10, 2016 11:58 PM
  • I'm also having a similar problem.

    Started to configure Exchange 2016 in a 2013 site.

    No mailboxes etc on the 2016 server.

    I have finished the 2016 configuration now (valid certificates, split DNS, internal and external connectivity etc), but still I wonder why are my Outlook clients using the 2016 server as a proxy?

    Both CAS's autodiscover SCP is pointing at the 2013 server.

    Today, the 2016 server was shut down for 30 minutes and all of my clients lost connectivity to their mailboxes which are on the 2013 server.

    Is this expected behaviour?

    Thursday, April 13, 2017 8:49 AM