Forum Discussion
Exchange 2019/outlook 2016
Hello all. We have three exchange servers in different domains but they all fall under the same site(AD site and services) Our DC's for the three domains also follow that topology. I think this impos...
Outlook client connections on domain joined machines connected to the internal network generally use the SCP record for autodiscover queries, and autodiscover provides the connection URLs the Outlook client uses. You should be able to control access by making sure the SCP record in each domain points to a DNS name that directs the connection to the correct Exchange server and that Exchange server returns the appropriate connection URLs that in turn point to the correct Exchange servers.
If your mailboxes have permissions to mailboxes in other domains, you may see connections to mailbox servers in other domains for that access.
- So when I do the autodiscover test from client and look at the log from it behaves as expcected ie.
Attempting URL https://autodisover.domain.com/autodiscover/autodiscover.xml found through SCP
Autodiscover to https://autodisover.domain.com/autodiscover/autodiscover.xml starting
GetLastError=0, httpStatus=401
GetLastError=0, httpStatus=200
Autodiscover to https://autodisover.domain.com/autodiscover/autodiscover.xml Succeded.
When I go to mailbox delegation the only thing that has full access to the mailbox are exchange servers and exchange trusted subsystem would these groups be causing my issue- And the URLs are correct that autodiscover returns?
What about the connection status? Which URLs are used for each connection?
What abut DNS...Are all DNS names pointing to the correct location, and if you have load balancing is that redirecting to the correct namespace
It's more about what this mailbox has delegate access to (connection status might show the details of this)- Forgot to mention we dont have load balancing.
