Of course the client can see the internal OOS URL without fault. Strangely, if I access the external OWA site fromĪn internal client, OOS works as intended. It either isn't doing that, or TMG is unable to interpret the links that Exchange sends back to the client. It already internally rewrites links in content returned to clients using its own Link Translation rules, so I figured I could try adding additional rewrite rules so it would catchĪnd replace '' with ''. I use an older Forefront TMG server to publish OWA and many other things. So it appears Exchange is providing internal links to OOS always. I can also browse '' from external clients,Īnd all of the XML content refers to the OOS external URL. Outlook Web App otherwise works correctly from outside.
Internally, I can view MS Office and PDF attachments from Outlook Web App in the browser.Įxternally, I get a 'cannot find message. So far so good, so I also pointed a new Office Online server at it. I've migrated a few mailboxes to a new Exchange 2016 installation.