I need to implement RPC over HTTPs (now called Outlook Anywhere) and I am having a bit of difficulty. Any help is greatly appreciated. We have a couple of users that work for the company but don't use an office computer, so it would be very helpful for them to be able to configure their external Outlook to connect to our Exchange server as OWA only gives web access to internal Outlook.
Here's some details:
RPC over HTTP Proxy is installed on the IIS server. Exchange is hosted on the same server. I believe it was installed automatically during the Essential Business Server Messaging Server installation process.
I purchased a SSL certificate through GoDaddy and users can access OWA with no problems or cert errors.
I went to https://testexchangeconnectivity.com
and used a newly created domain test account to verify connectivity. I had to input the exchange settings manually, autodiscovery was not successful. After that, everything succeeded and the connectivity test was successful, however, when I configure a remote users' Outlook to connect to Exchange it will not connect. Outlook reports an error during setup: "The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action."
I am thinking that the issue is in IIS. There is the Default Site, with all of the virtual directories containing owa, oab, autodiscovery, exch, exchweb etc... and then there is another site called HTTP Redirect and it's only purpose seems to be to direct any HTTP requests to the OWA directory using HTTPS (when users navigate to http://email.domain
they are redirected to https://email.domin/owa
). I remember setting this up as part of a walkthrough on configuring OWA. Could this be the problem, as the rpc virtual directory cannot be accessed using the external exchange URL?
Let me know if you need any more information. I look forward to your input!