Ever wanted to ~MONITOR~ you ORG's Mailboxes in Zabbix? NOW YOU CAN!!!

The "Exchange 2016 - Mailbox" is mostly used to monitor and alert when a mailbox is over quota or  need other statics asap (When you don't have credentials to the Exchange ECP)

It will monitor and trigger the following.

* Mailbox Size
* Inbox Size
* Sent Items Size
* Junk Mail Size
* Drafts Size
* Deleted Items Size
* Show Mailbox Quota and Calculate Percentage for Triggers
* Show On-Line Archive Quota and Calculate Percentage for Triggers
* Mailbox Triggers defined in stages (25%, 50%, 75%, 85%, 95%, 100%) Independently
* On-Line Archive Triggers defined in stages (25%, 50%, 75%, 85%, 95%, 100%) Independently
* Mailbox Triggers - Erratic Growth By 2% Gain
* On-Line Archive Triggers - Erratic Growth By 2% Gain
* Calculations based on bytes, not Mega/Giga


This works with Exchange 2016 CU12 or Higher (Or will it?)

Zabbix Version Minimum is 4.0, Built on 4.4

(Template Version 1.0.2)

Current: Version 1.0.2
Notes: Did not have Trigger "{#MAILALIAS} | 2% Abnormal On-Line Archive Growth Since Last Check" setup

(PS Script Version 1.1
Notes: Added calculation fix for arguments "mailboxpercentage" & "archivepercentage" to use 2 decimal place values for triggers to correctly update.

OK, this template uses the following:

1: Zabbix Agent Active
2: LLD (Low-Lever Discovery)
3: Triggers
4: Graphs
5: Powershell Script (REQUIRED)
6: ALERTS (Easily Configurable for EVERYONE ~YEAH!~) - But not deployed via Template "I'll get some work out of you all" Ha.. ha.. */sigh/*
7: My Insanity

Okay...

This template will "Discover" all mailboxes within ~TWENTY-FOUR (24) Hours~ then check every day for changes.

This script will pull based on each criteria and will be a resource hog for about 10mins on your server ~Depending on you resource levels~ (Hahhahahaa)

UPDATE: Apparently, the Zabbix Share website will not allow too much information stored in the description.  For updates on the Template, Powershell script or any changes made, please visit the github account and view the readme for more details.  Will try to keep the zabbix share updated with the current version information to identify in the github readme's.