Hello,
I have installed the Microsoft Web Platform Installer and from that I have installed Application Request Routing 3.0 (x64)
The trouble is I cannot find the ARRConfig.exe to run. I see that it installs some files to "C:\Program Files\IIS\Application Request Routing" but ARRConfig.exe isn't one of them.
I have read that it should be in C:\Windows\System32\Essentials but as this server doesn't have the Essentials role installed that folder is not here. From the root I have done a dir ARRConf*.* /s and it finds only 2 files buried in strange folders (see screen shot).
According to my search in Google it looks like only me and 1 other person had this issue! and they don't say if they fixed theirs or not.
Any ideas? I have Repaired, Reinstalled etc and still the same.
Thanks
Rob
Without Essentials Experience it does not work.
If you want to use ARRconfig you need to have the Essentials Experience installed. If you do not have that easiest way to publish Exchange Server on port 443 is to use two public IP addresses and different Host A Records.
For completeness if you don't want to install the Essential role then you can manually setup Application Request Routing and this is the best guide:
https://techcommunity.microsoft.com/t5/exchange-team-blog/part-1-reverse-proxy-for-exchange-server-2013-using-iis-arr/ba-p/592526
Don't forget the little bit at the bottom about Request Filtering and the other 2 steps it mentions.
So OWA and Active Sync worked fine but RPC Over HTTP failed in the Microsoft Remote Connectivity Analyzer (401 unauthorised). To fix that took a lot of hours, but finally I figured it out. The guide above used the Default Web Site. In my setup I had already installed and configured Remote Desktop Gateway and that had modified the Default Web Site and added it's own RPC info and this was conflicting with the ARR / Exchange RPC over HTTP. The answer was to add a new website and add https on 443 for my mail servers URL - mail.mycompany.co.uk - and bingo, it all tested fine! Learning a bit about ARR was handy and it could be a useful tool for redirecting https to other internal servers etc, if you only have 1 static IP address.