Have a client that likes to use Groupwise Remote quite a bit. He sometimes has extended stays in locations with pay-by-the-minute internet access. So he needs to be able to do the same thing in Outlook that he does in Groupwise Remote. The closest thing I found was Outlook Anywhere.
Trying to configure with Outlook 2007 offsite so to set it up over the internet. When I try to Check name it fails, but after I still click next and run Outlook, I get “There is a problem with the proxy server’s security certificate.” At least it’s more descriptive than the other errors I got. We don’t have a trusted third party certificate, but I had went to the servernamepublic directory and downloaded the Certificate Distribution program (an executable plus the server’s certificate) Ran this so that the computer trusts certificates created by the server.
Had the client contact their external DNS admins and add a remote.domain.com host with the external IP and add a SRV record for _tcp, port 443
Confirmed that IExplorer trusts the certificates by going to http:remote.domain.com and not seeing IExplorer complain of an invalid certificate.
I have success.
In Mail control panel, put in the users email address and name. Typed in their password. Chose Manual in the setup and configured the Exchange Server with the name of the server.domain.local (the name that would appear if this machine was on the internal network) and user name. (Do NOT check name, yet) Under More Settings | Connection | checked Connect to Microsoft Exchange using HTTP under Outlook Anywhere. Under Exchange Proxy settings typed in remote.domain.com in Use this URL to connect to my proxy server. I checked Connect using SSL only. I could not check Only connect to proxy servers that have this principle name in their certificate (This setting would not work as it complained of a problem in the certificate when connecting…I put remote.domain.com). I confirmed that the settings of Outlook Anywhere on the Exchange Server (client access piece) was set for NTLM Authentication and kept the settings to NTLM Authentication on the client.
Now the Use Cached Exchange Mode is greyed out. I need this for the client to be able to work offline remotely. After quick research, it looks like it’s because I’m testing this on a Terminal Server so it would probably be fine for the client.