Hello all
I am running SCOM 2012 rollup2, and i have installed the latest Exchange 2010 MP (14.3.38.4) I get many alerts for "Test-OutlookConnectivity diagnostic cmdlet (AutoDiscover)" (HTTP) If i log on to one of my 2010 sp2 (rollup4) CAS servers and manually
run the the below command I notice that the results from running the command manually on the CAS server itself take between 1 to 2 minutes before the results are returned. When i examine the alert that SCOM generates it says the "cn=extest_590edabe165f4a15'failed
1460(This operation returned because the timeout period expired". So it appears that SCOM is raising a valid alert, but at this point i am not sure why the CAS servers are not responding
in a timely manner. In my environment we point "webmail.domain.com", "Outlook.domain.com" and "autodiscover.domain.com" to a vip thats located on the Netscaler, the netsclaer load balances for the the two 2010 CAS servers. On one of the 2010 CAS servers i
edited the local host file to point mail,webmail,autodiscover to itself, itsead of the Netscaler. After waiting a couple of hours i noticed i recived no alerts for the CAS server that i edited the host file on, and I did receive a couple of alerts for the
CAS Server that was still resolving mail,autodiscover,outlook to the vip on the netscaler. When looking at the peformance view for this counter in SCOM i could clearly see a
big difference in performance, the green line is the CAS that had the host file edited, blue line is CAS server that still points to Netscaler. What i am trying to determine is where the problem is? from my research it appears to be that the issue is with
netscaler. It appears that the netscaler is not returning the traffic back to the CAS server in an acceptable amount of time. What i am trying to figure out is this soley a netscaler issue, or could this also be an Exchange issue as well?
Bulls on Parade