cwelectric
asked on
Setting up Outlook Anywhere in Exchange Server 2007
I have gotten Exchange working internally, as well as gotten Outlook Web Access working internally and externally.
I have looked over various articles regarding how to setup a Microsoft Outlook client to connect to Exchange server externally via Outlook Anywhere, but I seem to be missing something, as I cannot get it to work.
Any tips, links to reading material, etc?
I have looked over various articles regarding how to setup a Microsoft Outlook client to connect to Exchange server externally via Outlook Anywhere, but I seem to be missing something, as I cannot get it to work.
Any tips, links to reading material, etc?
There isn't much to it really.
Install the RPC Proxy component then enable the component in Exchange 2007.
Do ensure that you are using a commercial SSL certificate, as the self generated certificate is not supported for Outlook Anywhere.
You can test it from outside using the Microsoft test site and a test account.
https://www.testexchangeconnectivity.com
-M
Install the RPC Proxy component then enable the component in Exchange 2007.
Do ensure that you are using a commercial SSL certificate, as the self generated certificate is not supported for Outlook Anywhere.
You can test it from outside using the Microsoft test site and a test account.
https://www.testexchangeconnectivity.com
-M
ASKER
The self signed certificate is most likely what's stopping me, then. I have installed the RPC Proxy component on the Exchange server.
On a somewhat unrelated note...I am a bit unfamiliar with SSL certificates. From what I understand, GoDaddy.com offers fairly cheap ones. They have an option on their site for ones that you can use for up to 5 domains. Would this be the certificate I would need to purchase if the external and internal domains were different?
I will check out those links, too..
On a somewhat unrelated note...I am a bit unfamiliar with SSL certificates. From what I understand, GoDaddy.com offers fairly cheap ones. They have an option on their site for ones that you can use for up to 5 domains. Would this be the certificate I would need to purchase if the external and internal domains were different?
I will check out those links, too..
The Godaddy certificate will probably work for you as I believe it is piggy backing off of entrust. You need to purchase this certificate if you want your external users to connect to OA or OWA or activesync securely externally. When you configure your external URLs on your Exchange server, you will need to make sure that they are included on your Subject Alternative Name (SAN) certificate.
For example:
email.yourdomainname.com
autodiscover.yourdomainnam e.com
You will also need the FQDN of your CAS server on the certificate as well if you are going to keep the Exchange internal URLs the same.
To request a certificate you can watch the demo using powershell here: http://www.microsoft.com/b elux/TechN et/nl/chop sticks/def ault.aspx? id=763
For example:
email.yourdomainname.com
autodiscover.yourdomainnam
You will also need the FQDN of your CAS server on the certificate as well if you are going to keep the Exchange internal URLs the same.
To request a certificate you can watch the demo using powershell here: http://www.microsoft.com/b
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The SSL certificate was the only problem, I had everything else configured properly. Once I purchased and installed the certificate from GoDaddy, everything worked just fine. Thanks!
http://www.exchange-genie.com/2007/07/exchange-2007-autodiscover-service-part-1/
http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/