PRTG Manual: Exchange Mailbox (PowerShell) Sensor
The Exchange Mailbox (PowerShell) sensor monitors mailboxes of an Exchange server via Remote PowerShell.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Exchange Postbus (PowerShell)
- French: Exchange boîte aux lettres (PowerShell)
- German: Exchange-Postfach (PowerShell)
- Japanese: Exchange Mailbox(PowerShell)
- Portuguese: Caixa de correio Exchange (PowerShell)
- Russian: Почтовый ящик Exchange (PowerShell)
- Simplified Chinese: Exchange 邮箱 (PowerShell)
- Spanish: Buzón Exchange (PowerShell)
- This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
- This sensor requires elevated rights for the user of this sensor on the Exchange system. It is not sufficient to have administrative rights. For more information, see the Knowledge Base: I have problems with the PowerShell Exchange sensors, what can I do? (solution (2) in the reply).
- This sensor requires Remote PowerShell and Remote Exchange Management Shell on the target system and PowerShell on the probe system.
- This sensor requires .NET 4.7.2 or later from Microsoft on the probe system.
- This sensor requires that the parent device is the Exchange server (as of version 2010) that hosts the database that you want to monitor.
- This sensor requires credentials for Windows systems in the settings of the parent device.
- This sensor requires the fully qualified domain name (FQDN) of the Exchange server in the settings of the parent device.
- This sensor only supports IPv4.
- Knowledge Base: Where can I find more information about PowerShell sensors?
You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.
Requirement |
Description |
---|---|
This sensor uses PowerShell commands. This sensor requires that Remote PowerShell and Remote Exchange Management Shell are enabled on the target systems that you want to monitor. Also make sure you have at least PowerShell 2.0 installed on the probe system.
|
|
This sensor requires .NET 4.7.2 or later to be installed on the probe system (on every cluster node, if on a cluster probe).
|
|
To connect to Exchange servers, this sensor requires the FQDN. In the device settings of the Exchange server, provide the FQDN instead of the IP address.
|
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority ( |
Setting |
Description |
---|---|
Mailbox Name |
The name of the mailbox that this sensor monitors. |
Result Handling |
Define what PRTG does with the sensor result:
|
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
Item Count |
The number of items
|
Last Logon Time |
The time since the last mailbox login |
Total Item Size |
The total size of items |
KNOWLEDGE BASE
I have problems with the PowerShell Exchange sensors, what can I do?
Where can I find more information about PowerShell sensors?
How do I enable and use remote commands in Windows PowerShell?
How can I increase memory for Remote PowerShell?
Which .NET version does PRTG require?
What security features does PRTG include?
My PowerShell sensor returns an error message. What can I do?
I get the error "WinRM cannot process the request" when I try to use a PowerShell sensor