For those who don’t know, we can no longer use internal domain names like server.domain.local as of 2015. The people who manage SSLs decided that is no longer accepted.
This poses a problem for many of our SSLs where we use that to avoid internal resolution issues as now any Outlook connecting to server.domain.local will pop up a message error constantly.
These are the steps I’ve done to fix it in the past combined with a related issue today.
Get-ClientAccessServer - Identity server | fl
Look at the AutodiscvoerServiceInternalUri and if it is looking internally update it with the following
Set-ClientAccessServer -Identity CAS1 -AutodiscoverServiceInternalUri https://remote.domain.com/autodiscover/autodiscover.xml
Get-WebServicesVirtualDirectory | fl
Look at the internal URL setting and update if wrong:
Set-WebServicesVirtualDirectory -Identity "CAS1\EWS (Default Web Site)" -InternalUrl https://webmail.mycompany.com/ews/exchange.asmx
Get-OABVirtualDirectory | fl
Check internal URL and correct if wrong:
Set-OABVirtualDirectory -Identity "CAS1\oab (Default Web Site)" -InternalUrl https://webmail.mycompany.com/oab
This last one isn't normally used and is for Unified Messaging. I did not want to leave it out.
Set-UMVirtualDirectory -Identity "CAS1\unifiedmessaging (Default Web Site)" -InternalUrl https://webmail.mycompany.com/unifiedmessaging/service.asmx