Scenario:

Client contacted me to implement Exchange 2013 in their existing organisation.

Old server is Exchange 2007 installed on a Windows 2003 x64 server

The old server is also a Domain Controller (the only DC)

A UC certificate has been purchased & installed on the new server.

All clients are running Outlook 2010

Problem:

The problem is that after moving mailboxes - the outlook client still attempts to connect to the Old server.

A new user with a new mailbox created on the New Exchange 2013 has the same issue, autodiscover resolves OK, but the SSL error that is presented shows the self-signed cert on the old server.

Accessing the mailbox via OWA is OK indicating that the mailbox is working & mail flow is OK (all mail is routed via the Exchange 2013)

Running "Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri" on the Exchange 2013 gives the correct https://autodiscover.domain.com.au/Autodiscover/Autodiscover.xml for the Exchange server and reports https://oldserver.domain.local/Autodiscover/Autodiscover.xml for the old server.

There is a DNS zone to the domain.com.au on the internal DNS server and there is an entry for autodiscover that resolves to the Exchange 2013 server.

Run Outlook's Test-Email Autoconfiguration and see if any URLs point to the old server.  It might be the OAB--do you have an OAB published on the Exchange 2013 server?

Hi Ed,

thanks for the reply

The Exchange 2013 box has an OAB & it is the default.  Prior to introducing the Exchange 2013 box I had to regenerate the OAB on the Exchange 2007 server as it was missing.

I'm getting the local admin to run the other tests as we are budget-constrained

Best regards,

Steve

Hi Ed,

thanks for the reply

The Exchange 2013 box has an OAB & it is the default.  Prior to introducing the Exchange 2013 box I had to regenerate the OAB on the Exchange 2007 server as it was missing.

I'm getting the local admin to run the other tests as we are budget-constrained

• Edited by Kerr Avon 1 hour 49 minutes ago

It appears that there is a problem with the SCP as checking AD shows an SCP for both servers - however all clients show the old server when the connectivity test is run.

When the user attempts to connect a client with a mailbox on the new server - he gets a certificate presented referencing the old server.

Does anyone have any suggestions as I'm reluctant to make changes here as the only time I have seen this referenced is during a migration form on-premise Exchange to the cloud

Set-ClientAccessServer -Identity OLD_SERVER -AutodiscoverServiceInternalUri https://correct_Autodiscover_URL