new2scom
2010-04-16 07:59:01 UTC
Hi, I've been getting the following error in exchange 2007 MP which I have
read various similar issues in other posts - (see
http://social.technet.microsoft.com/Forums/en/operationsmanagermgmtpacks/thread/a6258ead-a457-4cc6-9213-ca71a429acc1 )
Exchange 2007 Test OWA Connectivity Internal Monitor
The test was unable to log on to Outlook Web Access because the SSL
certificate did not validate. You can force the cmdlet to proceed by
re-running it and specifying the �TrustAnySSLCertificate parameter.
URL: https://<FQDN_connector1>/owa/ - One or more of the Outlook Web Access
Connectivity tests generated warnings. Detailed information:
-------------------------------------
Target: <FQDN_connector1>|<FQDN_mailbox1>
Error: The test was unable to log on to Outlook Web Access because the SSL
certificate did not validate. You can force the cmdlet to proceed by
re-running it and specifying the �TrustAnySSLCertificate parameter.
URL: https://<FQDN_connector1>/owa/
As per the advice I have created an override for the Exchange 2007 test
system Health Rule (ie enabled=False) targeted at Exchange 2007 Best
Practice. When I restart the agent on the CAS servers the OWA Coneectivity
Test alerts dissappear from the console so it 'appears' to resolve the
problem. However the alert comes back in at 19:10:20 which seems to be when
the Exchange 2007 Test System Health Rule is configured to run.
If anyone could help resolve this it would be much appreciated as I have a
distributed App for exchange built with Service Level tracking and because of
this issue the Exchange availability is being hammered!!
Many thanks...
read various similar issues in other posts - (see
http://social.technet.microsoft.com/Forums/en/operationsmanagermgmtpacks/thread/a6258ead-a457-4cc6-9213-ca71a429acc1 )
Exchange 2007 Test OWA Connectivity Internal Monitor
The test was unable to log on to Outlook Web Access because the SSL
certificate did not validate. You can force the cmdlet to proceed by
re-running it and specifying the �TrustAnySSLCertificate parameter.
URL: https://<FQDN_connector1>/owa/ - One or more of the Outlook Web Access
Connectivity tests generated warnings. Detailed information:
-------------------------------------
Target: <FQDN_connector1>|<FQDN_mailbox1>
Error: The test was unable to log on to Outlook Web Access because the SSL
certificate did not validate. You can force the cmdlet to proceed by
re-running it and specifying the �TrustAnySSLCertificate parameter.
URL: https://<FQDN_connector1>/owa/
As per the advice I have created an override for the Exchange 2007 test
system Health Rule (ie enabled=False) targeted at Exchange 2007 Best
Practice. When I restart the agent on the CAS servers the OWA Coneectivity
Test alerts dissappear from the console so it 'appears' to resolve the
problem. However the alert comes back in at 19:10:20 which seems to be when
the Exchange 2007 Test System Health Rule is configured to run.
If anyone could help resolve this it would be much appreciated as I have a
distributed App for exchange built with Service Level tracking and because of
this issue the Exchange availability is being hammered!!
Many thanks...