Get-WebApplicationProxyApplication "/owa" | Format-ListĪll of this looks OK. We can use the Remote Access Management console to open the properties of the published application, or use PowerShell. The OWA published application is highlighted, and then a zoomed view is shown for OWA. Below is the Remote Access management console on server WAP-2016-1. Reviewing WAP ConfigurationĪll of the required Exchange CAS namespaces were published using WAP. The issue is onlywith the external publishing. OWA and ECP can also be rendered as expected on the WAP server. From the WAP servers themselves, DNS resolves to the correct endpoints. Internally everything is just fine and all is working as expected. Maybe OWA is not running on the published Exchange server – let's try ECP instead. Instead of being able to see your lovely OWA splash screen when at Starbucks you instead are greeted with the below rather sad page:įor make most glorious search engine benefit: Unfortunately no plan survives contact with the enemy. After verifying that core AD FS and WAP functionality works as expected you then move onto using WAP to publish Exchange to the Internet using pass through authentication.
This is an interesting deployment project and all is going well. There are multiple AD FS servers and WAP servers. You just finished deploying AD FS 2016 and Web Application Proxy (WAP) servers in a highly available environment with the AD FS namespace load balanced internally and externally.
0 kommentar(er)
