Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
Directory Tree
Exchange 2010 CAS
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
These use the inbuilt test functionality in Exchange through the Exchange Management Shell. These tests log in using the test cas users to the various servers and actually test functionality AND response. So it will fail if something underlying is failing in the system too.
Before running these - you must have created the test cas user using the "new-testcasconnectivityuser.ps1" script found in your Exchange Management tool installation (under scripts folder).
Check scripts for:
- ActiveSync Connectivity
- IMAP Connectivity
- MAPI Connectivity
- Outlook TCP (RPC) Connectivity
- OWA Connectivity
- WebServices Connectivity
I have not been able to test all of the failure cases yet.
A work in progress..
Reviews (2)
byTheMichi44, December 10, 2014
here is the first problem:
###########################
$status = 0;
$desc = "";
test-activesyncconnectivity | ForEach-Object {
[snippet]
elseif ($status -eq "0") {
Write-Host "OK: ActiveSync Connectivity OK"
###########################
if you have an error on "test-activesyncconnectivity" the status will be "OK" at the end.
i would do the following as a fast fix:
###############
$status = 2; # 2 = critical
$desc = "";
test-activesyncconnectivity | ForEach-Object {
if($_.Result -like "Success") {
$status = 0;
###############
So you would get a "critical" output at the end if you have a problem at "test-activesyncconnectivity".
fast hint for other languages:
######################
elseif($_.Result -like "Failure") {
######################
in german it would be:
######################
elseif($_.Result -like "Erfolgreich") {
######################
greetz
###########################
$status = 0;
$desc = "";
test-activesyncconnectivity | ForEach-Object {
[snippet]
elseif ($status -eq "0") {
Write-Host "OK: ActiveSync Connectivity OK"
###########################
if you have an error on "test-activesyncconnectivity" the status will be "OK" at the end.
i would do the following as a fast fix:
###############
$status = 2; # 2 = critical
$desc = "";
test-activesyncconnectivity | ForEach-Object {
if($_.Result -like "Success") {
$status = 0;
###############
So you would get a "critical" output at the end if you have a problem at "test-activesyncconnectivity".
fast hint for other languages:
######################
elseif($_.Result -like "Failure") {
######################
in german it would be:
######################
elseif($_.Result -like "Erfolgreich") {
######################
greetz
byalfred, November 24, 2011
just works :-)
exchange 2010 SP1
exchange 2010 SP1