# Exchange

# Introduction

**Ver.** 01-27-2023

Plugin for monitoring an Exchange server, works on versions later than Exchange 2010.

**Type**: Agent plugin

# Compatibility matrix

<table border="1" id="bkmrk-sistemas-donde-se-ha" style="font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Oxygen, Ubuntu, Roboto, Cantarell, 'Fira Sans', 'Droid Sans', 'Helvetica Neue', sans-serif; font-size: 14px; width: 564px; height: 70px;"><tbody><tr style="height: 35px;"><td style="width: 234px; height: 35px;">**Systems where it has been tested**</td><td style="width: 330px; height: 35px;">Exchange 2016

</td></tr><tr style="height: 35px;"><td style="width: 234px; height: 35px;">**Systems where it should work**</td><td style="width: 330px; height: 35px;">Exchange versions 2013 and above

</td></tr></tbody></table>

# Pre requisites

- Have the PandoraFMS agent installed.
- An Exchange 2013 or later server and have PowerShell and the Exchange shell available.

The plugin must be run by a user with permissions to connect to the Exchange management shell according to the server we want to connect to. That user must have sufficient privileges to use the cmdlets necessary to obtain the information.

To prepare for the use of the Exchange administration shell, you must have a user with access privileges for some of the cmdlets. If you have the necessary permissions, a default installation of the Pandora agent is sufficient, and no additional configuration is required.

# Parameters

<table border="1" id="bkmrk--all-saca-todos-los-" style="border-collapse: collapse; width: 100%;"><tbody><tr><td style="width: 50%;">-all</td><td style="width: 50%;">Get all modules</td></tr><tr><td style="width: 50%;">-mailbox</td><td style="width: 50%;">Get the mailbox modules.</td></tr><tr><td style="width: 50%;">-cas</td><td style="width: 50%;">Get the cas modules</td></tr><tr><td style="width: 50%;">-services</td><td style="width: 50%;">To monitor detected Exchange services</td></tr></tbody></table>

# Manual execution

```
powershell.exe -PSConsoleFile “<path_to_exchange_shell>\exshell.psc1” -command “C:\‘<path_to_plugin>\Pandora_Plugin_Exchange.ps1’ <parameters> 3> $NULL”
```

<span style="text-decoration: underline;">Example</span>

[![imagen.png](https://pandorafms.com/guides/public/uploads/images/gallery/2025-12/scaled-1680-/i0qimagen.png)](https://pandorafms.com/guides/public/uploads/images/gallery/2025-12/i0qimagen.png)

# Configuration in PandoraFMS

To obtain the information, the exchange plugin must be configured in the Pandora agent.

To be able to monitor from Pandora FMS with the plugin, we must call it from the EndPoint config file located in the following path:

```
/etc/pandora/pandora_agent.conf
```

We will call it in the last line of the conf with the module\_plugin command, followed by the following command:

```
module_plugin powershell.exe -PSConsoleFile "<exchange_shell_directory>\exshell.psc1" -command "C:\'<plugin_directory>\Pandora_Plugin_Exchange.ps1' <parameters> 3> $NULL"
```

This can also be done from the console if remote configuration is enabled.

# Modules generated by the plugin

The plugin will remove the following modules:

<table border="1" id="bkmrk-message-count-%3Cserve" style="border-collapse: collapse; width: 100%;"><tbody><tr><td style="width: 100%;">Message count &lt;server&gt;</td></tr><tr><td style="width: 100%;">CPU Average &lt;server&gt;</td></tr><tr><td style="width: 100%;">MEM Average &lt;server&gt;</td></tr><tr><td style="width: 100%;">Capacity(GB) &lt;server&gt; &lt;unidad&gt;</td></tr><tr><td style="width: 100%;">FreeSpace(GB) &lt;server&gt; &lt;unidad&gt;</td></tr><tr><td style="width: 100%;">Free(%) &lt;server&gt; &lt;unidad&gt;</td></tr></tbody></table>

**Mailbox**

<table border="1" id="bkmrk-database-replication" style="border-collapse: collapse; width: 100%;"><tbody><tr><td style="width: 100%;">Database replication</td></tr><tr><td style="width: 100%;">Mapi connectivity</td></tr><tr><td style="width: 100%;">Dag status</td></tr></tbody></table>

**CAS**

<table border="1" id="bkmrk-owa-activesync-web-s" style="border-collapse: collapse; width: 100%;"><tbody><tr><td style="width: 100%;">OWA</td></tr><tr><td style="width: 100%;">ActiveSync</td></tr><tr><td style="width: 100%;">Web Services</td></tr><tr><td style="width: 100%;">Remote powershell</td></tr><tr><td style="width: 100%;">POP</td></tr><tr><td style="width: 100%;">IMAP</td></tr><tr><td style="width: 100%;">ECP</td></tr><tr><td style="width: 100%;">Autodiscover</td></tr><tr><td style="width: 100%;">Outlook client connectivity</td></tr><tr><td style="width: 100%;">SMTP connectivity</td></tr></tbody></table>

If the “-services” parameter is used, a separate module will be created for each detected service.