Outlook referencing server.domain.local after Exchange SSL update

Hi All,
   I have googled like mad on the issue and can not fix the following:

I changed the SSL on the exchange from domain.local to domain.com, i had to apply the certificate via IIS to the exchange service and can confirm that all external Web access and SSL is working as expected. I have changed the local exchange URL to match the external URL and have confirmed via EMS, my internal client machines are failing on the Exchange Server name now when connecting.

The SAN certificate has the following 5:

when the client outlook connected to the exchange the server settings are still ServerName.Domain.Local and not ServerName.Domain.Com and as such they are failing on the final check each time.

Am i missing a step here to point the client to the correct new server name?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeremy WeisingerSenior Network Consultant / EngineerCommented:
One thing that is often missed is the Autodiscover URI.
To check what it is currently, run the following:

Get-ClientAccessServer | fl name,AutoDiscoverServiceInternalUri

Open in new window

To set the URI on all CAS servers:
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://owa.domain.com/Autodiscover/Autodiscover.xml

Open in new window

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kash2nd Line EngineerCommented:
run test on your server >>> http://testexchangeconnectivity.com/ and post the results back.
Jason CrawfordTransport NinjaCommented:
What version of Exchange?
ncomperAuthor Commented:
Jeremy: Thanks, confirmed already pointing to the external URL
Kash: RPC over HTTP connectivity failed
Keyser: Exchange 2010 SP2 (need to update to SP3 Friday out of hours)
Jason CrawfordTransport NinjaCommented:
Thank you.  Don't forget about Outlook Anywhere.  For Exchange 2010:

Get-OutlookAnywhere | Set-OutlookAnywhere -ClientAuthenticationMethod basic -IISAuthenticationMethods basic,ntlm

Open in new window

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.