New Exchange 2019 installation: Outlook autodiscover works externally, but not internal to the domain
We have a new Exchange 2019 installation for a small three-person business, with mailboxes brought over from a budget hosting provider.
Right now they're using OWA since we can't get Outlook working internally to their Active Directory. Externally works fine, verified both with https://testconnectivity.microsoft.com/tests/exchange
and by using Autodiscover with Outlook clients outside the domain.
Internally, we have verified DNS (A, CNAME, and SRV records), Autodiscover URL paths and permissions internally and externally, verified the IIS "Default Web Site" and "Exchange Back End" SSL settings and permissions according to this Microsoft reference article
, we've run "iisreset" multiple times after each step, and we're absolutely spent on why this isn't working correctly.
Where else can we look to resolve this issue? What are we missing?
Note: Don't ask why we didn't move them to Office 365 - we have beat this conversation into the ground with them - they absolutely hate anything "cloud". #smh
- "Exchange Back End" is using self signed "Microsoft Exchange" SSL certificate.
- SCP URL is "https://mail.domain.com/AutodiscoveAutodiscover.xml
" and displays the following after authenticating with valid credentials:
This XML file does not appear to have any style information associated with it. The document tree is shown below. 600 Invalid Request
- Running "Get-ClientAccessService | fl *uri*" returns the correct SCP URL shown above.
For future visitors, Outlook was trying to reach out to Office 365 even though this is an on-premise Exchange installation. Here's how we fixed it:
- In the registry on the affected machine, go to: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover
- Create a DWORD (32-bit) value for "ExcludeExplicitO365Endpoint" and change the value to “1” to enable it.
- Reboot the affected machine, and set up your on-premise Exchange account in a new Outlook profile.
submitted by HappyDadOfFourJesus
Can't get the "Reload Page in Internet Explorer Mode" menu option to show up on my work laptop
I want to test IE mode with Edge on a single website that requires some extremely old ActiveX controls in IE mode. I don't have any issues getting that option available on my home PC, but I'm having issues on my work laptop.
I have local admin rights, and I ran an rsop. The only thing that I can see is the Computer Config > Admin Templates > Windows Components > Microsoft Edge > Set default search engine GPO is configured. Would that possibly prevent me from seeing the "Internet Explorer compatability" sub-menu under the "Default browser" menu? I AM able to create a site list .xml file, but it forces a re-direct to IE instead of loading in Edge Mode.
So far I've tried the following:
- Installed the dev and beta builds
- Re-ran the stable build installer
- Added in admin templates to setup "Configure Internet Explorer integration" and "Configure the Enterprise Mode Site List" (both show up fine in edge://policy - there are no other policies set for Edge there)
I think on my home PC, I also did the edge://flags setting for enabling IE mode, but that doesn't appear to exist anymore.
submitted by cowmu