<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Exchange Database DAG (PowerShell) Sensor

Remote PowerShell and Remote Exchange Management Shell

This sensor uses PowerShell commands. To monitor Exchange servers with this sensor, you must enable Remote PowerShell and Remote Exchange Management Shell on the target servers that you want to monitor. Also ensure you have at least PowerShell 2.0 installed on the probe system.

In larger environments, the default memory limit for the remote shell might be insufficient. This might result in the error message The WSMan provider host process did not return a proper response. In this case, increase the memory limit for Remote PowerShell.

For more information, see the Knowledge Base: How do I enable and use remote commands in Windows PowerShell? and How can I increase memory for Remote PowerShell?

Exchange user account permissions

This sensor requires a user account that must be either in the Exchange management role group View-Only Organization Management or be in a group with the following assigned management roles:

• Monitoring

• View-Only Configuration

• View-Only Recipients

FQDN

To connect to Exchange servers, this sensor needs the FQDN. In the device settings of the Exchange server, provide the FQDN instead of the IP address.

For more information, see the Knowledge Base: I have problems with the PowerShell Exchange sensors, what can I do?

.NET 4.7.2 or later

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).

If the framework is missing, you cannot create this sensor.

For more information, see the Knowledge Base: Which .NET version does PRTG require?

Database

Select the databases that you want to monitor. PRTG creates one sensor for each database that you select.

Enable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.

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.

If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?

Parent Tags

Shows tags that the sensor inherits from its parent device, parent group, and parent probe.

This setting is for your information only. You cannot change it.

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.

It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

For performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

• exchange
• powershell
• database
• dag

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 () to the highest priority ().

Database

Shows the name of the database that this sensor monitors.

PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Result Handling

Define what PRTG does with the sensor result:

• Discard result: Do not store the sensor result.

• Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt, Result of Sensor [ID].Data.txt, and Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

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.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

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.

Activation Suspended

If the activation is suspended

• Up status: No
• Warning status: Yes

Active Copy

The copy status

• Up status: Active, Not Active
• Warning status: Active But Not On The Preferred Server, Could Not Read Activation Preference, Not Active But This Is The Preferred Server

Content Index State

The content index state

• Up status: Healthy, Not Supported In 2019
• Warning status: Crawling
• Down status: Error

Copy Queue Length

The number of items in the copy queue

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

Log Copy Queue Increasing

If the log copy queue is increasing

• Up status: No
• Warning status: Yes

Log Replay Queue Increasing

If the log replay queue is increasing

• Up status: No
• Warning status: Yes

Replay Queue Length

The number of items in the replay queue

Single Page Restore

The number of single page restores

Status

The overall DAG status

• Up status: Healthy, Mounted
• Warning status: Disconnected and Healthy, Disconnected and Resynchronizing, Dismounting, Initializing, Mounting, Resynchronizing, Seeding, SeedingSource, SinglePageRestore, Suspended
• Down status: Dismounted, Failed, Failed and Suspended, Service Down

This channel is the primary channel by default.