asked on
How to setup outlookanywhere in MS Exchange 2010 server?
This is using MS Exchange 2010 server on W2K8 server. My management wants to implement Outlook Anywhere. After getting the SSL certificate from Go-Daddy, I use EMC and run "New exchange certificate" and finally run "import exchange certificate" to bind the ssl certificate. After that, I checked that the rpc over http is installed and "start" the service as service is set to manual and stopped before this. The last thing is, on EMC, I click "Enable Outlook Anywhere", with the message telling me to wait for up to 15 minutes.
To test, I tried to browse to OWA in https, and successfully logged on. But, when I tried the Outlook connectivity in ExCRA, the test failed with the following error:
Testing Outlook connectivity.
The Outlook connectivity test failed.
Additional Details
Elapsed Time: 9359 ms.
Test Steps
Testing RPC over HTTP connectivity to server mail.abc.com
RPC over HTTP connectivity failed.
Additional Details
HTTP Response Headers:
Content-Length: 58
Content-Type: text/html
Date: Tue, 02 Dec 2014 01:36:35 GMT
Server: Microsoft-IIS/7.5
WWW-Authenticate: Basic realm="mail.abc.com"
X-Powered-By: ASP.NET
Elapsed Time: 9359 ms.
Test Steps
Attempting to resolve the host name mail.abc.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 203.xxx.xx.xx
Elapsed Time: 320 ms.
Testing TCP port 443 on host mail.abc.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 227 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 476 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.hutcabb.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.abc.com, OU=Domain Control Validated, Issuer: CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.
Elapsed Time: 431 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name mail.abc.com was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.abc.com, OU=Domain Control Validated.
One or more certificate chains were constructed successfully.
Additional Details
A total of 2 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
Elapsed Time: 20 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 2 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 12/1/2014 10:02:01 AM, NotAfter = 11/1/2015 7:00:00 AM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 1836 ms.
Testing HTTP Authentication Methods for URL https://mail.abc.com/rpc/rpcproxy.dll?mail.abc.com:6002.
The HTTP authentication methods are correct.
Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
Content-Length: 58
Content-Type: text/html
Date: Tue, 02 Dec 2014 01:36:35 GMT
Server: Microsoft-IIS/7.5
WWW-Authenticate: Basic realm="mail.abc.com"
X-Powered-By: ASP.NET
Elapsed Time: 750 ms.
Attempting to ping RPC proxy mail.abc.com.
RPC Proxy was pinged successfully.
Additional Details
Elapsed Time: 241 ms.
Attempting to ping the MAPI Mail Store endpoint with identity: mail.abc.com:6001.
The attempt to ping the endpoint failed.
Tell me more about this issue and how to resolve it
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 5507 ms.
Just wondering why the test failed. Appreciate help.
To test, I tried to browse to OWA in https, and successfully logged on. But, when I tried the Outlook connectivity in ExCRA, the test failed with the following error:
Testing Outlook connectivity.
The Outlook connectivity test failed.
Additional Details
Elapsed Time: 9359 ms.
Test Steps
Testing RPC over HTTP connectivity to server mail.abc.com
RPC over HTTP connectivity failed.
Additional Details
HTTP Response Headers:
Content-Length: 58
Content-Type: text/html
Date: Tue, 02 Dec 2014 01:36:35 GMT
Server: Microsoft-IIS/7.5
WWW-Authenticate: Basic realm="mail.abc.com"
X-Powered-By: ASP.NET
Elapsed Time: 9359 ms.
Test Steps
Attempting to resolve the host name mail.abc.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 203.xxx.xx.xx
Elapsed Time: 320 ms.
Testing TCP port 443 on host mail.abc.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 227 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 476 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.hutcabb.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.abc.com, OU=Domain Control Validated, Issuer: CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.
Elapsed Time: 431 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name mail.abc.com was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.abc.com, OU=Domain Control Validated.
One or more certificate chains were constructed successfully.
Additional Details
A total of 2 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
Elapsed Time: 20 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 2 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 12/1/2014 10:02:01 AM, NotAfter = 11/1/2015 7:00:00 AM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 1836 ms.
Testing HTTP Authentication Methods for URL https://mail.abc.com/rpc/rpcproxy.dll?mail.abc.com:6002.
The HTTP authentication methods are correct.
Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
Content-Length: 58
Content-Type: text/html
Date: Tue, 02 Dec 2014 01:36:35 GMT
Server: Microsoft-IIS/7.5
WWW-Authenticate: Basic realm="mail.abc.com"
X-Powered-By: ASP.NET
Elapsed Time: 750 ms.
Attempting to ping RPC proxy mail.abc.com.
RPC Proxy was pinged successfully.
Additional Details
Elapsed Time: 241 ms.
Attempting to ping the MAPI Mail Store endpoint with identity: mail.abc.com:6001.
The attempt to ping the endpoint failed.
Tell me more about this issue and how to resolve it
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 5507 ms.
Just wondering why the test failed. Appreciate help.
Exchange
Last Comment
MichaelBalack