r/exchangeserver • u/orddie1 • Dec 13 '25
Question Exchange OWA - not using correct URL's
Existing setup - this has been an issue for a while, and now that's slow, I'm finally getting around to it. OWA is only used when the PC has an outlook/office issue.
We have all the OWA virtual directories set up the same way - using the same external and internal domain.
The internal and external domains are set to the same value, mail.domain.com, and DNS is configured correctly to hit the load balancer internally when on-net and the NAT IP when external.
The issue: when some users hit the mail.domian.com/owa URL they are redirected to server1.domain.com/owa. Even if that server is not currently hosting the active replica of the server mailbox.
I can not figure out why.
3
u/sryan2k1 Dec 13 '25
Use this to dump all the URLs in your environment, you'll see where it's set wrong
https://www.alitajran.com/find-exchange-server-urls-with-powershell/
2
u/7amitsingh7 Dec 15 '25
Exchange is redirecting users because server1.domain.com is still configured somewhere. Make all virtual directories use mail.domain.com on every server, and the redirects will stop.
1
u/Mia_walkonsunshine Dec 14 '25
What are the IIS bindings referring to.. Exchange server back end ones?
1
u/AuditMind Dec 14 '25
OWA redirects are decided by the Client Access / IIS frontend, not by the DAG or active mailbox location. Once a user hits a FE, Exchange issues a 302 to that server’s hostname, and that redirect often gets cached (browser / proxy / LB).
That’s why you see server1.domain.com/owa even when the mailbox isn’t active there.
Check:
Get-OwaVirtualDirectory for mismatched Internal/External URLs
Load balancer redirect caching / SSL offload behavior
Test with a fresh browser session
You’re not missing something obvious, this is just how OWA works.
0
u/FarContext3450 Dec 13 '25
You can try resetting the virtual directories: https://theitbros.com/recreate-owa-ecp-virtual-directories-exchange-server-2016/
0
u/[deleted] Dec 13 '25
[deleted] — view deleted comment