Build precise queries to find exactly what you need
Press ESC to close
Join our next live webinar: “Advanced Nagios Monitoring Techniques” – Register Now
Your review has been submitted and is pending approval.
Exchange Client Access Checks for 2010
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..
Current Version
0.1
Last Release Date
2011-05-19
Owner
Cameron Murray
Website
http://www.camm.id.au
Compatible With
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
just works :-) exchange 2010 SP1
You must be logged in to submit a review.
To:
From: