PRTG Plugins Admin Guide 1.4.506

-i[
PRTG PLUGINS ADMIN GUIDE

www.prtgplugins.com
PRTG Plugins Version: 1.4.506

[PRTG PLUGINS ADMIN GUIDE]
October 27, 2017 www.prtgplugins.com
Table of Contents
PRTG PLUGINS ADMIN GUIDE ........................................................................................................................... 9
PRTG PLUGINS MONITORING SUPPORTED ENVIRONMENTS........................................................................ 9
List of Plugins that support monitoring in heterogeneous environments ................................................ 9
List of Plugins that require monitoring in homogeneous environments................................................. 10
What needs to be installed where?............................................................................................................. 10
PRTG Main server .................................................................................................................................... 10
PRTG Remote Probes............................................................................................................................... 10
PRTG PLUGINS INSTALLATION ENVIRONMENT REQUIREMENTS ................................................................ 11
PRTG PLUGINS INSTALLATION PROCEDURE ................................................................................................ 11
PRTG PLUGINS CONFIGURATION PROCEDURE ........................................................................................... 14
What is the Difference between Standard EXE and Advanced EXE versions of PRTG Plugins? .............. 14
Why are the templates important? ......................................................................................................... 14
How plugins authenticate to services ......................................................................................................... 15
Some special configurations considerations ............................................................................................... 16
DISK FRAGMENTATION MONITORING ........................................................................................................ 17
ACTIVE DIRECTORY PLUGIN (STANDARD AND ADVANCED EXE MODE) ...................................................... 19
Key Performance data ............................................................................................................................. 19
Administrative content data.................................................................................................................... 20
Activity and Security related data ........................................................................................................... 21
Table of respective Event codes for Active Directory Servers ................................................................ 22
Usage and parameters............................................................................................................................. 23
Active Directory Group Members Monitoring ............................................................................................ 24
Scanning Interval and Performance [Timeout] ....................................................................................... 25
NETAPP ONTAP7 SERVER V2 PLUGIN .......................................................................................................... 26
Hardware and environment Monitoring ................................................................................................. 26
NetApp Device Basic Hardware Status: HWMINISTAT ............................................................................ 26
NetApp Device Hardware Status: HWSTAT1 ........................................................................................... 27
NetApp Device Capacity Status: HWSTAT2 ............................................................................................. 29
Volume Information and Advanced Monitoring ......................................................................................... 31
Volume Specific Custom Query Example (percentage used only) .......................................................... 32
Volume Specific Custom Query Example (percentage used with Alerts count) ..................................... 33
Aggregate Monitoring and Information ...................................................................................................... 34
1|Page
Predefined Performance Views ................................................................................................................... 36

Performance Predefined Set 1: PFSET1 ....................................................................................................... 36
How to Create Custom Queries based views .............................................................................................. 37
Custom Query example 02 ...................................................................................................................... 37
All NetApp Objects and Counters ................................................................................................................ 38
CIFS .......................................................................................................................................................... 38
PROCESSOR.............................................................................................................................................. 38
IFNET ........................................................................................................................................................ 38
VOLUME................................................................................................................................................... 38
CIFS DOMAIN (CFDOM) ........................................................................................................................... 40
RAID ......................................................................................................................................................... 42
RAIDSTRIPE (RDSTRIPE) ........................................................................................................................... 42
QTREE ...................................................................................................................................................... 42
AGGREGATE (AGGRE1) ............................................................................................................................ 42
LOTUS DOMINO SERVER PLUGIN ................................................................................................................ 46
Prequisites ............................................................................................................................................... 46
Important Note ........................................................................................................................................ 46
The Domino Base Information Sensor ..................................................................................................... 46
Creating the Traveler Monitoring Sensor ................................................................................................ 47
Creating the Database Monitoring Sensor .............................................................................................. 47
Creating the Platform Monitoring Sensor ............................................................................................... 48
Creating the Disks Monitoring Sensor ..................................................................................................... 48
Creating a Domino Monitor with Custom Sensor Channels .................................................................... 49
Domino Custom Sensor Channel Options in Detail ................................................................................. 50
Creating an example Custom Domino Monitoring Sensor ...................................................................... 51
SHAREPOINT/MOSS SERVER V2 PLUGIN ..................................................................................................... 52
SharePoint Content Sensor...................................................................................................................... 52
Example of creating SharePoint Content Monitoring sensor .................................................................. 53
SharePoint Auditing sensor ..................................................................................................................... 54
Example of creating SharePoint Auditing sensor .................................................................................... 54
SharePoint Security Auditing sensor ....................................................................................................... 55
Example of creating SharePoint Security Auditing sensor ...................................................................... 55
Other Plugins to be considered with SharePoint monitoring ................................................................. 56
2|Page
SharePoint Content Sensor Command line ............................................................................................. 56

AMAZON EC2 VOLUME PERFORMANCE MONITORING PLUGIN 1.0 ........................................................... 57
CITRIX MONITORING PLUGINS ROLES ......................................................................................................... 59
CITRIX/XENAPP LICENSING AND REMOTE DESKTOP PLUGIN V2................................................................. 60
Citrix / XenApp Performance and Health Monitoring ................................................................................. 60
Built in Counters with Automatic Warning levels ................................................................................... 61
Citrix / XenApp ICA Session Bandwidth Monitoring ................................................................................ 62
Example of creating Citrix / XenApp Performance sensor ...................................................................... 63
Citrix / XenApp Session Quantity Monitoring.......................................................................................... 64
Example of creating Citrix / XenApp Session sensor .............................................................................. 64
Citrix / XenApp Core Performance and Health Monitoring..................................................................... 65
Example of creating Citrix / XenApp Core Performance sensor .............................................................. 65
Licensing mode ............................................................................................................................................ 66
Example of creating Citrix Licensing sensor ............................................................................................ 66
Example of creating Citrix Licensing Pool sensor .................................................................................... 67
Debugging Citrix Licensing Connectivity .................................................................................................. 67
CITRIX XENDESKTOP 7.x AND XENAPP 7.x MONITORING ONLY .................................................................. 69
Monitoring XenDesktop and XenApp 7.x Farms ......................................................................................... 69
Monitoring XenApp/XenDesktop 7.x Farm Server Load and Farm Sessions Count ................................... 70
Setting up XenDesktop Farm Server Load Sensor ................................................................................... 71
Setting up XenDesktop Farm Server Sessions Count Sensor ................................................................... 71
Monitoring XenApp/XenDesktop 7.x Farm for Slow logons........................................................................ 72
Setting up XenDesktop Farm Slow Logons Sensor .................................................................................. 73
Monitoring XenApp/XenDesktop 7.x Farm Broker Connections................................................................. 74
Setting up XenDesktop Farm Broker Connections Sensor ...................................................................... 75
Monitoring XenApp/XenDesktop 7.x Session Brokering Connections ........................................................ 76
Setting up XenDesktop Session Brokering monitoring Sensor ................................................................ 77
Monitoring XenApp/XenDesktop 7.x Sessions and Applications ................................................................ 78
Setting up XenDesktop Session and Applications monitoring Sensor ..................................................... 79
Monitoring XenApp/XenDesktop 7.x Citrix Logon Performance................................................................. 80
Setting up XenDesktop Logon Performance Sensor ................................................................................ 81
Monitoring XenApp/XenDesktop 7.x Citrix End User Experience (EUEM) .................................................. 82
Setting up XenDesktop Citrix End User Experience Monitoring (EUEM) Sensor..................................... 83
3|Page
CITRIX/XENAPP APPLICATION SIMULATION AND MONITORING ................................................................ 84

Installation steps to be followed on the computer simulating the sessions ........................................... 86
Example of creating Citrix Session Simulation sensor ............................................................................. 89
NETSCALER VPX MONITORING PLUGIN....................................................................................................... 91
NetScaler Base Monitoring .......................................................................................................................... 92
Example of creating NetScaler VPX Base Monitoring Sensor .................................................................. 92
NetScaler Certificates Monitoring ............................................................................................................... 93
Example of creating NetScaler Certificates Monitoring Sensor .............................................................. 93
NetScaler Load Balancing Virtual Servers Monitoring................................................................................. 94
Example of creating NetScaler Load Balancing Virtual Servers Monitoring Sensor ................................ 94
Excluding Virtual Servers from Sensor..................................................................................................... 95
Using the sensor parameter method ...................................................................................................... 95
Using the exclusion file method .............................................................................................................. 95
NetScaler Gateway Virtual Servers Status Monitoring................................................................................ 96
Example of creating NetScaler Gateway Virtual Servers Monitoring Sensor .......................................... 96
NetScaler Modes Monitoring ...................................................................................................................... 97
Example of creating NetScaler Modes Monitoring Sensor ..................................................................... 97
NetScaler Features Monitoring ................................................................................................................... 98
Example of creating NetScaler Features Monitoring Sensor .................................................................. 98
Example of creating NetScaler Gateway Statistics Monitoring Sensor ................................................... 99
NetScaler Gateway Virtual Server Performance Monitoring .................................................................... 100
Example of creating NetScaler Gateway Virtual Server Performance Monitoring Sensor ................... 100
NetScaler AAA Statistics Monitoring ......................................................................................................... 101
Example of creating NetScaler AAA Statistics Monitoring Sensor ........................................................ 101
NetScaler Configuration Backup Age Monitoring ..................................................................................... 102
Example of creating NetScaler Configuration Backup Age Monitoring Sensor ..................................... 102
NetScaler Configuration Unsaved Monitoring .......................................................................................... 103
Example of creating NetScaler Configuration Backup Age Monitoring Sensor ..................................... 104
REMOTE DESKTOP SERVICES MONITORING (RDS 2XXX) ........................................................................... 105
RD Session Host Monitoring .................................................................................................................. 106
RD Gateway Monitoring ........................................................................................................................ 107
RD Licensing Monitoring........................................................................................................................ 108
RD Virtualization Host Monitoring ........................................................................................................ 109
4|Page
RD Connection Broker Monitoring ........................................................................................................ 110

RD Web Access Monitoring ................................................................................................................... 111
Example of creating RDS 2012 Session Host Monitoring Sensor .......................................................... 112
Example of creating RDS 2012 Gateway Monitoring Sensor ................................................................ 113
Example of creating RDS 2012 Licensing Monitoring Sensor ................................................................ 114
REMOTE DESKTOP SERVICES SESSION SIMULATOR (RDS 2XXX) ............................................................... 116
Conditions for Session Monitoring (Important!) ................................................................................... 116
Creating a RD Application Session Simulation with MSPaint ................................................................ 117
Parallels Remote Access Server (2X RAS) Monitoring ............................................................................... 118
Prerequisites .......................................................................................................................................... 118
Creating the 2x RAS Monitoring Sensors ............................................................................................... 120
REMOTE PING V2 PLUGIN ......................................................................................................................... 121
IIS/BITS SERVER V2 PLUGIN ....................................................................................................................... 122
DYNAMICS AX/AOS COMMUNICATIONS SERVER V2 PLUGIN ................................................................... 123
General Information .............................................................................................................................. 123
Dynamics AX Application Object Server Instance Performance............................................................ 124
TOTAL SESSIONS and ACTIVE SESSIONS in AOS Performance ............................................................... 124
Example of creating Microsoft Dynamics AX AOS Sensor: ................................................................... 126
Dynamics AX Client Performance Sensor .............................................................................................. 127
Example of creating Microsoft Dynamics AX Client Sensor: ................................................................. 128
Dynamics AX Portal Performance Sensor .............................................................................................. 129
Example of creating Microsoft Dynamics AX Enterprise Portal Sensor: ............................................... 130
ADVANCED MICROSOFT SQL SERVER V2 (AMSS) PLUGIN......................................................................... 131
Monitoring Databases (Top 10 Most Reads and Writes) ..................................................................... 131
Monitoring Databases (Top 10 Most Waits) ........................................................................................ 131
Monitoring SQL Server Disk latency ...................................................................................................... 131
Monitoring SQL Server IO Bottlenecks .................................................................................................. 132
LYNC 201X (OFFICE 2007/LIVE COMMUNICATIONS 2005) SERVER PLUGIN ............................................. 135
General Information .............................................................................................................................. 135
User load and Usage Counters .............................................................................................................. 136
Usage ..................................................................................................................................................... 138
BACKUPEXEC MONITORING PLUGIN ......................................................................................................... 139
Some Special concerns .............................................................................................................................. 139
5|Page
Running Backup Exec Plugin in a Probe computer with Backup Exec installed .................................... 139
SQL Connectivity topics of the Backup Exec Database .......................................................................... 139
Other Plugins to be considered with Backup Exec Monitoring ................................................................. 140
The new Base sensor ............................................................................................................................. 141
Creating the Backup Exec Base sensor .................................................................................................. 142
Advanced Backup Exec Jobs Monitoring in EXE/XML Mode via SQL Connectivity ............................... 143
Backup Exec Plugin Monitoring Reference Example ................................................................................. 147
Installation Overview ............................................................................................................................. 147
Sensors and options installed in detail .................................................................................................. 148
STEP ONE: Check the prerequisites ....................................................................................................... 148
STEP TWO: Create a new device for your Backup Exec Monitoring...................................................... 149
STEP THREE: Create sensor for Backup Server Running and base information .................................... 149
STEP FOUR: Create sensor for Backup Events ....................................................................................... 150
STEP FIVE: Create sensor for Job status (During last 24 hrs.) ................................................................ 151
STEP SIX: Create sensor for Jobs Failed in 24h ...................................................................................... 152
STEP SEVEN: Create sensor for Last 10 Jobs by size (since last 48 hrs.) ................................................ 152
STEP EIGHT: Create sensor for Last 10 Jobs by Age (since last 48 hrs.) ................................................ 153
STEP NINE: Create sensor for “Hanging Jobs” (Jobs running over 12 hrs.) ........................................... 153
STEP TEN: Monitor Backup Exec Core Services via native PRTG sensors .............................................. 154
Some additional Backup Exec sensors recommended for monitoring.................................................. 155
How to monitor Multiple Backup Exec Servers in one single view ....................................................... 156
HP HARDWARE INFORMATION PLUGIN V2 ............................................................................................... 157
Operational requirements ......................................................................................................................... 159
Presenting the results................................................................................................................................ 160
VEEAM BACKUP & REPLICATION SERVER PLUGIN .................................................................................... 161
Monitoring a Default Veeam Backup installation (v8 and v9)................................................................... 161
Using Exclusions in Jobs ............................................................................................................................. 161
Backup Performance Monitoring .............................................................................................................. 162
Job Statuses Monitoring ............................................................................................................................ 163
Joblogs in Last X hrs ................................................................................................................................... 164
Proxy Status ............................................................................................................................................... 165
Repositories Status .................................................................................................................................... 166
Last Backups Ages ...................................................................................................................................... 167
6|Page
Hanging Jobs .............................................................................................................................................. 169

ARCSERVE BACKUP MONITORING PLUGIN ............................................................................................... 171
Monitoring ArcServe Job Statuses......................................................................................................... 171
Creating an ArcServe Monitoring Sensor .............................................................................................. 172
ESX SERVER PLUGIN V2 ............................................................................................................................. 173
Environment Status (VMSTAT) .............................................................................................................. 173
VMTOOLS............................................................................................................................................... 175
VMTOOLS_VERSIONS ............................................................................................................................ 176
VMDATASTORE_INFO ............................................................................................................................ 177
VMSTAT_VMOS ..................................................................................................................................... 178
SYSTEM CENTER CONFIGURATION MANAGER / WSUS PLUGIN 1.0 ......................................................... 179
Monitoring Package Distributions ............................................................................................................. 180
MICROSOFT CLUSTER MONITORING PLUGIN ............................................................................................ 182
Sensor Channel Statuses for Resources (“2RS-“)....................................................................................... 182
Monitoring Options for very Large Clusters to overcome PRTG Limitations ........................................ 183
Special option for Passive only Clusters ................................................................................................ 184
MICROSOFT FILE SERVICES MONITORING PLUGIN ................................................................................... 185
Statuses and Volumes monitored ............................................................................................................. 185
Logons .................................................................................................................................................... 185
Sessions ................................................................................................................................................. 185
Files Open .............................................................................................................................................. 185
Dir Searches ........................................................................................................................................... 185
Failures and Errors monitored................................................................................................................... 185
Pool Paged Failures................................................................................................................................ 185
Non Paged Failures ................................................................................................................................ 185
Sessions Errored .................................................................................................................................... 185
Sessions Forced Out .............................................................................................................................. 186
Sessions Logged Out .............................................................................................................................. 186
Sessions Timed Out ............................................................................................................................... 186
Work Items Shortages ........................................................................................................................... 186
Requests Rejected ................................................................................................................................. 186
Failures and Errors of Security related monitoring ................................................................................... 186
Errors Logon........................................................................................................................................... 186
7|Page
Errors Access.......................................................................................................................................... 186

Errors Perm ............................................................................................................................................ 186
Errors System......................................................................................................................................... 186
PLUGIN TYPES AND EXECUTABLES NAMES LIST ........................................................................................ 188
KNOWN GENERIC LIMITATIONS AND BUGS .............................................................................................. 189
EXAMPLES .................................................................................................................................................. 189
CASE ONE: SharePoint 2010 Foundation Server on Ontap iSCSI Volume Based database ................... 189
8|Page
PRTG PLUGINS ADMIN GUIDE
PRTG PLUGINS MONITORING SUPPORTED ENVIRONMENTS

There are certain limitations of using some PRTG-Plugins in heterogeneous environments. Plugins that do
not support authentication in a heterogeneous domain environments have be installed on PRTG Server or
Probe device that can authenticate on the target system via homogeneous domain environment like same
forest and domain or trusted domains.
1) Probe.workgroup
PRTG Server
2) Probe.dom.lcl
Targets
Domain: Dom.lcl
Picture 1: Schematics of different PRTG Installation options
Probe 1 is not a part of the same domain environment as the targets so it is regarded as heterogeneous
environment can support installation of plugins that support heterogeneous environments. Probe 2 is part
of the same domain as the targets being monitored and is regarded as homogenous environment that
supports installation of all current plugins.
We encourage you to make the installation of the plugins to a separate device in order not to endanger the
performance of the main PRTG server as it is the preferred set up procedure for a vanilla PRTG environment
as well.
List of Plugins that support monitoring in heterogeneous environments

 Active Directory Plugin (AD2008Monitor.exe)
 Backup Exec Plugin (BEMonitor.exe)
 NetApp/Ontap Plugin (ONTapmon.exe)
 Remote Ping V2 Plugin (REMPingV2.exe)
 VMware ESX Monitoring Plugin (ESXMonitor.exe)
 SharePoint Plugin (MOSSMonitor.exe)
 WSUS/SCCM Plugin (WSUSMonitor.exe)
9|Page
List of Plugins that require monitoring in homogeneous environments

 Dynamics AX Plugin (AXMonitor.exe)
 Internet Information Server Plugin (IISMonitor.exe)
 Remote Desktop Plugin (RDPMonitor.exe)
What needs to be installed where?

In general the installation can be described the following.
PRTG Main server

Execute PRTG Plugins setup and choose to install the templates. This will install the following:
 Template files
PRTG Remote Probes

Suggested installations before installing the PRTG Plugins
 .NET 3.5 environment
Execute PRTG Plugins setup and choose to install the plugins. This will install the following:
 All executables
 Library and Support files (dlls etc)
After the PRTG Plugins Setup you must install:
 Copy your license key(s) to both EXE and EXEXML directories

 Download and replace the executables with updates
(The copy location depends on the PRTG plugin type. Check if the executable is existing in the
directory or if it supports EXE, EXEXML or both)
10 | P a g e
PRTG PLUGINS INSTALLATION ENVIRONMENT REQUIREMENTS

The only real requirement for the device installed with Plugins is the .NET environment. The minimum
version for .NET is 4.0 which is included in many of the new operating systems as an option. Consider
installing the .NET environment prior to the PRTG Plugins installation procedure. If not completed prior
then the PRTG Plugins installation will notify of this missing and fail.
PRTG PLUGINS INSTALLATION PROCEDURE

Setup can be initiated on both PRTG Server and PRTG Probe machines with different options. There is a
video demonstrating the installation and configuration at:
http://www.prtgplugins.com/index.php?option=com_content&view=article&id=57&Itemid=38
11 | P a g e
ABOVE: Choose to install the Plugins only if installing to a probe device
ABOVE: Choose templates only if installing these to a main PRTG server
ABOVE: Choose both options only if installing on a single PRTG server with no probes
(Not preferred option in large scale production environments)
12 | P a g e
ABOVE: Check and revise the installation folder if not a standard PRTG installation.
13 | P a g e
PRTG PLUGINS CONFIGURATION PROCEDURE

What is the Difference between Standard EXE and Advanced EXE versions of PRTG Plugins?
PRTG Programming interface offers two different ways of getting external data. The Standard EXE interface
can support only one value per sensor thus making it tedious to set up complicated service views since you
need to set up a sensor per data that you want to show. Advanced EXE interface was introduced in later
versions of PRTG and is much less tedious to set up since multiple data channels can be presented via single
sensor. Not the least advantage is also the performance improvements since you can present more data via
single execution of the plugin.
Many of our plugins have been initiated to developing at the time when Standard EXE interface was the
only way of presenting data and is the major reason why many of the plugins still support it. Since the
Advanced EXE interface became available we have been enabling the support for the new interface on
older plugins as well but maintained the backwards compatibility to older installations with Standard
interfaces. We encourage you to utilize the advanced EXE version of the plugins where possible.
Why are the templates important?

To make it easier to utilize Standard EXE plugins there is a comprehensive and expanding library of
templates available for the plugins. Templates enable you to create complex device monitoring set up’s in a
single task especially for those Standard EXE’s.
Watch the demonstration video to see how templates are being utilized at:
http://www.prtgplugins.com/index.php?option=com_content&view=article&id=57&Itemid=38
14 | P a g e
How plugins authenticate to services

In general plugins always authenticate to servers and services by Windows credentials. In most cases
domain accounts are to be used but local credentials are supported as well.
When ever there is a reference to %windowsuser placeholder in the parameters section it stands for the
windows account credentials that can do the job. The type of access of the credentials used is entirely up to
you as an administrator. The picture explains the reference of variables used on device and sensor level.
ALWAYS AVOID ‘HARDCODING’ THE CREDENTIALS TO SENSOR PARAMETERS!
15 | P a g e
Some special configurations considerations

As we encourage you to use dedicated remote probe computers in some cases you need to install the PRTG
remote probe and the plugins on the server being the host of the services monitored (error 4: WMI Cannot
connect to target \root\cimv2. Code 0610). To overcome this you can use the target name lh or . or
localhost as the computer name. In many cases this can be given on PRTG’s device parameters section.
The method will use the probe’s environmental credentials (ComputerAccount$) to access the services
instead of invoking the authentication procedure.
16 | P a g e
DISK FRAGMENTATION MONITORING

Disk fragmentation is one of the easiest ways to degrade your Server and Service performance. In order to
avoid this happening the Volume Defragmentation Monitor was developed. The monitor also provides a
consolidated channel (Volumes Needing Defrag) for easy alerting.
17 | P a g e
Create Disk Fragmentation monitoring In PRTG interface:
1 Create a new device

2 Enter values for device name and IP Address/DNS Name of your SharePoint Front End
server
3 Check the Inherit Credentials for Windows Systems field for sufficient credentials or enter
your own values
4 Check that scanning interval is set to 5 minutes or more
Create the sensor for Disk Fragmentation Monitoring in PRTG interface:
1 Create a new sensor by Add Sensor

2 Choose EXE/Advanced Script type of sensor
3 Enter Sensor name: “Server Name” Defrag
4 Enter tags: DISKFRAG
5 Choose volmonitor.exe from the Exe/Script drop down box
6 Enter the following In the parameters section:
-t:%host -u:%windowsuser -p:%windowspassword -
d:%windowsdomain -i:frag
7 Set the timeout for 280 to ensure that the sensor has time to respond
8 Click on Continue to Save
18 | P a g e
ACTIVE DIRECTORY PLUGIN (STANDARD AND ADVANCED EXE MODE)
Active directory plugin consists of three main areas:
 [10] Active Directory Key performance data

 [20] Active Directory Administrative content data
 [30] Active Directory Activity and Security related data
Key Performance data
Key performance data is being used to monitor the Active Directory health and performance in each
Domain Controller separately.
Channel data explained:
 Address book Client Sessions

Number of AB Sessions on target Domain Controller. This would be any client applications that
know how to create an address book session to the global catalog through NSPI like Microsoft
Outlook.
 LDAP Client Session Count
Number of LDAP Clients connected to the Domain Controller. In multi Domain Controller
environment this value should reflect the defined Active Directory site structure. If you have a
Domain Controller defined on an Active Directory site this should be a rough number of users
located at the site.
 Data store Threads in Use
Indicates the number of threads which the directory service is currently utilizing.
 DRA Inbound Bytes per Second
Indicates the total number of bytes (compressed and uncompressed bytes) received via inbound
Active Directory replication.
19 | P a g e
 DRA Outbound Bytes per Second

Indicates the total number of bytes (compressed and uncompressed bytes) which were replicated
out by Active Directory replication.
 DRA Pending Replication Syncs
The number of directory synchronizations that are queued for this server that are not yet
processed. This counter helps in determining replication backlog — the larger the number, the
larger the backlog.
 LDAP Bind Time
Indicates the time which the last successful LDAP binding took.
 LDAP Searches per Second
Indicates the number of LDAP search operations performed by LDAP clients.
Administrative content data
Channels explained:
 LDAP Disabled Accounts

Number of User Accounts in Disabled state
 LDAP Password Never Expires Accounts
Number of User Accounts defined as described.
 LDAP User Accounts
Total Number of User Accounts
20 | P a g e
Activity and Security related data
Security aspects related to Active Directory relay almost entirely on each DC’s log files and monitoring
activity cannot be done on manual basis regularly. Additionally the event codes for same event on different
operating systems vary. Active Directory plugin automatically correlates the event codes from different
versions of the operating systems. In an operating system upgrade situation you just need to change the OS
version to continue as before.
Based on the information produced by the plugin it is very easy to monitor what is happening in the Active
Directory answering the questions: what, where and when. Monitoring this on regular basis may save you
from a major catastrophe.
21 | P a g e
Table of respective Event codes for Active Directory Servers

Description Event Code 2003 Event Code 2008
Creating a user account 624 4720

Deleting a user account 630 4726
Changing a user account 642 4738
Account name was changed 4781
Change password attempt 627 4723
Attempt to reset password 4724
Password set or reset 628
Unknown user name or password 529 4625
Disabled account 531 4725
Expired account 532
Logon type not allowed 534
Account locked out 539 4740
User account automatically locked 644
Time restrictions 530
Replay attack detected 553 4649
Change directory services restore mode password 698
Clearing the security event logs 517
Changing audit policy 612
Changing the domain security policy 643
Attempted logon using explicit credentials 4648
Domain policy was changed 4739
Kerberos policy was changed 4713
System audit policy was changed 4719
Encrypted data recovery policy was changed 4714
Windows Firewall setting has changed 4950
Service installed in the system 4697
22 | P a g e
Usage and parameters
Setup EXEXML type of sensor in PRTG where in executable choose AD2008Monitor.exe. In parameter
section give the following values in given order:
%host %windowsuser %windowspassword %windowsdomain [Index] [AD/Server Type]
Where:
[Index] Is for selecting the monitoring area. Getting the Performance related data use [index] 10, for
Content data use [index] 20 and for Activity and Security related data use [index] 30.
Important Note: For [index] 30 the server type is defined by the target Server operating system: Since
activity related event codes vary on the server operating system type it is important to use correct
parameter. In case of 2008/R2 type of server operating as a Domain Controller in an 2003 Active Directory
environment use 2008R2 as a parameter.
[AD/Server Type] Is the Active Directory or Server operating system version in question.
Possible values are:
 2003 for 2003 based active directories and 2003 or 2003 R2 type of Domain Controllers
 2008 for 2008 based active directories and 2008 type of Domain Controllers
 2008R2 for 2008R2 based active directories and 2008 R2 type of Domain Controllers.
Example:
Getting Performance Data of a 2008 level Domain Controller.
23 | P a g e
Active Directory Group Members Monitoring

The latest addition to the sensor options allows you to monitor and report members in a group. The sensor
status lists all group’s member account and full name information. Also it reports and log all users removed
and added to the group. This information is also saved to the sensors log.
Create content monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your AD Server.
your own values
Create the sensor for Content Monitoring in PRTG interface:

7 Enter Sensor name: AD Group Memebers NN
8 Enter tags: ADG_CONTENT
9 Choose ad2008monitor.exe from the Exe/Script drop down box
%host %windowsuser %windowspassword
%windowsdomain 40 2012R2 subgroup1
where subgroup1 is the name of the group to monitor.
24 | P a g e
Scanning Interval and Performance [Timeout]
Finding out the optimal value for sensor timeouts depends entirely on your environment’s performance
and the decision how you choose to configure the monitoring (WAN/LAN). Security [30] and Content [20]
type of sensors are more dependent on target computers performance than Performance [10] sensor
based monitoring. You can expect to wait some 1-3 minutes for the polling to finish on both of them
regardless of the connectivity type. For performance based data [10] the polling should finish in a few
seconds.
Scheduling the sensor’s scanning and timeouts is based on the performance tests and you should reserve a
reasonable time frame for variations in general performance. Overlapping polling (new poll starts before
old one was finished) can result in serious defections on the target server performance and endanger the
services.
25 | P a g e
NETAPP ONTAP7 SERVER V2 PLUGIN
You can monitor virtually any Performance counter value within the NetApp API context.
Use Best practice based predefined sets or design your own views based on best practices or your own
taste.
Hardware and environment Monitoring

Hardware and environment monitoring have been divided to the following sections:
NetApp Device Basic Hardware Status: HWMINISTAT

This is the most basic view on the performance data of your NetApp device.
1. System Uptime
2. Global Status
3. CPU Busy
4. Net Received Total
5. Net Send Total
6. nfs_ops
7. cifs_ops
8. http_ops
9. fcp_ops
10. iscsi_ops
11. read_ops
12. write_ops
13. sys_read_latency
14. sys_write_latency
15. sys_avg_latency
Command line:
%host %windowsuser %windowspassword HWMINISTAT
26 | P a g e
NetApp Device Hardware Status: HWSTAT1

This is the Primary Hardware and Capacity view your NetApp device. Implement your Hardware and
Capacity related alerts here.
 CPU Busy
 Global Status
Triggering:
1: other
2: unknown
3: OK
4: no critical = Default Value
5: critical
6: non recoverable
 Env Over Temp
 Fan Failed
Triggering Value > 0
 Power Failed
 Support Enabled
 Support Msgs Failed
 Disks Total
 Disks Reconst
 Disks ReconstPar
 Disks Scrubbing
 Disks Failed
 Disks Spare
 Disks Zero
 NVRAM Status
 Cluster State
 FS Overall Status
 FS Max Used %
 FS Max Used Nodes %
 FS Max Used Reserved %
 CP NV Full
 CP Total
 CP FS Sync
27 | P a g e
Command line:
%host %windowsuser %windowspassword HWSTAT1
28 | P a g e
NetApp Device Capacity Status: HWSTAT2

This is the generic view on the Performance Counters of the NetApp Device.
 CPU Busy
 Net Received Total
 Net Send Total
 CIFS Ops
 CIFS Ops High
 CIFS Ops Low
 FC High Ops
 FC low Ops
 FC High Read
 FC High Write
 FC Low Read
 FC Low Write
 LUN High Errs
 LUN High Ops
 LUN High Other Ops
 LUN High Read
 LUN High Read Ops
 LUN High Write
 LUN High Write Ops
 LUN Low Errors
 LUN Low Ops
 LUN Low Other Ops
 LUN Low Read Bytes
 LUN Low Read Ops
 LUN Low Write Bytes
 LUN Low Write Ops
 Misc High Disk Read Bytes
 Misc Low Disk Read Bytes
 NFS Ops
 NFS Ops High
 NFS Ops low
29 | P a g e
Command line:
Create EXE/Advanced Script type of sensor and choose ontapmon.exe
Parameters:
%host %windowsuser %windowspassword HWSTAT2
CPU
 CPU Busy %
UPTIME
 System Uptime
(Presented as days)
30 | P a g e
Volume Information and Advanced Monitoring

Enables comprehensive ways of monitoring and displaying data of all or just selection of volumes in
Customer cases. By default the monitoring consists of the following data for each of the volumes:
 Percentage used
 Total size of the volume in bytes
 Size used in bytes
 Size available in bytes
 Alerts Count Channel
For space usage monitoring you can set an Alert level which indicates a warning and information of the
volume as text. You can also use filtering on volume Names and Channels. See the following Custom Query
example
.
Command line:
Parameters:
%host %windowsuser %windowspassword VOLINFO [-i:xx,yy,zz] [-c:aa,bb,cc] [-ul:99]
[-i:] Instances list (names of the volumes comma separated)
[-c:] List of channels comma separated:
PUSED – Percentage Used

STOT – Volume Size
SUSED – Volume Used
SAVA – Size Available
WARN – Show warning channel if needed.
[-ul:] The alert level for percentage used value –ul:70 alerts of the volume if used capacity of over 70%
31 | P a g e
Volume Specific Custom Query Example (percentage used only)

Volume Information supports some additional features like filtering the output channels.
We want to display the percentage used values only and have warnings generated if over 30% of the
capacity is exceeded. Set the parameters to –c:pused and –ul:30
The Output shows only the Percentage Used values and the volumes exceeding in the message (The alerts
channel is missing):
32 | P a g e
Volume Specific Custom Query Example (percentage used with Alerts count)
You can enable the alerts channel visibility easily by adding that to the list of channels shown:
Result shows a separate Alerts channel presenting the number of volumes exceeding the limits.
You can set the PRTG alerting based on the alerts channel data values and it is still valid even if any volume
is omitted from or added to the filer.
33 | P a g e
Aggregate Monitoring and Information

Enables comprehensive ways of monitoring and displaying data of all or just selection of aggregates in
Customer cases. By default the monitoring consists of the following data for each of the Aggregates:
CHANNEL Filtering Key Description Options

_Size TSIZE Total size of the Aggregate in Bytes
_Used SUSED Used amount in Bytes
_Free SAVAI Bytes free
_Used% PUSED Used Percentage
_Files_Total FTOT Total Number of Files
_Files_In_Use FUSED Number of Files in use
_Online OFFL Is Online If Offline the instance
is indicated in the
information text area
and Sensor status is set
to warning
Alerts WARN Number of errors detected If filtering channels is
used then status text is
shown ONLY if alerts
are allowed.
Offline OFFL Number of Offlines detected
The use and functionality of parameters for instances, channels and alerts is the same as described
in VOLINFO paragraph. Please refer to it for more details.
Command line:
Parameters:
%host %windowsuser %windowspassword AGGRINFO [-i:xx,yy,zz] [-c:aa,bb,cc] [-ul:99]
[-i:] Instances list (names of the volumes comma separated)
[-c:] List of channels shown as comma separated list. See the above list of Filtering Keys
[-ul:] The alert level for percentage used value –ul:70 alerts of the volume if used capacity of over
70%
34 | P a g e
35 | P a g e
Predefined Performance Views

These are predefined sets of information from several different sources based on “Best-Practices” solutions
to help you implement detailed views on Performance and Services of NetApp.
Performance Predefined Set 1: PFSET1
 CPU Busy
 nfs_ops
 cifs_ops
 http_ops
 fcp_ops
 iscsi_ops
 read_ops
 write_ops
 sys_read_latency
 sys_write_latency
 sys_avg_latency
 recv_data
 send_data
Command line:
Parameters:
%host %windowsuser %windowspassword PFSET1
36 | P a g e
How to Create Custom Queries based views

If the predefined views are not enough there is a method creating one based on your requirements. You
can “call out” items from any Performance API area (CIFS, VFILER) and also define the Counter values of
each area that are shown. Also you can filter the actual items that are shown on the list based on item
names used in installation.
Custom Query example 02

If needed you can combine any combination of Objects and Counters to define your own views of Ontap.
Command line examples:
Parameters:
%host %windowsuser %windowspassword ifnet,volume,proc,cifs

-i:vfiler0,processor1,processor0,e0c,e0b,vol0,vol1
-c:recv_data,send_data,recv_errors,send_errors,avg_latency,total_ops,processor_busy,total_ops
[-i:] Describes the actual names of the instances: like vfiler0 is the actual name of one Virtual Filer on the
Ontap Server, vol0 and vol1 are actual volume names.
[-c:]Is the “mix” of Performance counters of all objects we want to monitor.
Given parameters will produce the following data:
Command line syntax (EXE/Advanced Script/ontapmon.exe):
%host %windowsuser %windowspassword [OBJ1],[OBJ2],[OBJ] -i:Inst1,Inst2,Inst3 -c:Count1,Count2,Count3
37 | P a g e
All NetApp Objects and Counters

CIFS
 total_ops
 readx_ops
 writex_ops
 rename_ops
PROCESSOR
 processor_busy
 processor_elapsed_time
 sk_switches
 hard_switches
IFNET
 recv_packets
 recv_errors
 send_packets
 send_errors
 collisions
 recv_data
 send_data
 recv_mcasts
 send_mcasts
 recv_drop_packet
VOLUME
 avg_latency
 total_ops
 read_data
 read_latency
 read_ops
 write_data
 write_latency
 write_ops
 other_latency
 other_ops
 internal_msgs
 read_blocks
 write_blocks
 synchronous_frees
 asynchronous_frees
 df_worker
 nfs_read_data
38 | P a g e
 nfs_read_latency
 nfs_read_ops
 nfs_write_data
 nfs_write_latency
 nfs_write_ops
 nfs_other_latency
 nfs_other_ops
 cifs_read_data
 cifs_read_latency
 cifs_read_ops
 cifs_write_data
 cifs_write_latency
 cifs_write_ops
 cifs_other_latency
 cifs_other_ops
 san_read_data
 san_read_latency
 san_read_ops
 san_write_data
 san_write_latency
 san_write_ops
 san_other_latency
 san_other_ops
 fcp_read_data
 fcp_read_latency
 fcp_read_ops
 fcp_write_data
 fcp_write_latency
 fcp_write_ops
 fcp_other_latency
 fcp_other_ops
 iscsi_read_data
 iscsi_read_latency
 iscsi_read_ops
 iscsi_write_data
 iscsi_write_latency
 iscsi_write_ops
 iscsi_other_latency
 iscsi_other_ops
 flexcache_read_data
 flexcache_read_latency
 flexcache_read_ops
39 | P a g e
 flexcache_write_data
 flexcache_write_latency
 flexcache_write_ops
 flexcache_other_latency
 flexcache_other_ops
CIFS DOMAIN (CFDOM)

 netlogon_latency
 netlogon_latency_base
 lsa_latency
 lsa_latency_base
 samr_latency
 samr_latency_base
CIFS STATS (CFSTAT)
 curr_sess_cnt
 max_sess_cnt
 multi_user_sess_cnt
 sig_sess_cnt
 client_disc_sess_cnt
 filer_disc_sess_cnt
 dup_disc_sess_cnt
 max_cred_sess_cnt
 max_tree_sess_cnt
 max_msg_sess_cnt
 curr_conn_user_cnt
 logon_cnt
 map_null_user_cnt
 uid_hash_alloc_cnt
 curr_share_cnt
 max_share_cnt
 curr_tree_cnt
 max_tree_cnt
 max_fid_tree_cnt
 max_search_tree_cnt
 max_core_search_tree_cnt
 tid_hash_alloc_cnt
 curr_open_file_cnt
 max_open_file_cnt
 curr_open_dir_cnt
 max_open_dir_cnt
 curr_watch_dir_cnt
40 | P a g e
 max_watch_dir_cnt
 fid_hash_alloc_cnt
 fold_attempt_cnt
 fold_rename_cnt
 fold_rename_failure_cnt
 fold_overflow_cnt
 fold_duplicate_cnt
 fold_wafl_too_busy_cnt
 curr_lock_cnt
 max_lock_cnt
 x_or_batch_to_l2_cnt
 x_or_batch_to_none_cnt
 l2_to_none_cnt
 no_break_ack_cnt
 no_break_ack_95_cnt
 no_break_ack_nt_cnt
 ignored_ack_cnt
 delayed_break_cnt
 pdc_auth_cnt
 curr_cred_cnt
 max_cred_cnt
 max_sid_cred_cnt
 built_lgrp_cnt
 user_lgrp_cnt
 sid_lgrp_cnt
 curr_mem_ctrl_blk_cnt
 curr_mem_ctrl_blk_reserve_cnt
 max_mem_ctrl_blk_cnt
 max_mem_ctrl_blk_reserve_cnt
 exhaust_mem_ctrl_blk_cnt
 exhaust_mem_ctrl_blk_reserve_cnt
 wait_mem_ctrl_blk_cnt
 wait_mem_buf_cnt
 auth_qlength
 block_qlength
 timer_qlength
 alf_qlength
 rpc_qlength
 offload_qlength
 max_auth_qlength
 max_block_qlength
 max_timer_qlength
41 | P a g e
 max_alf_qlength
 max_rpc_qlength
 max_offload_qlength
 copy_align_cnt
 small_buffer_align_cnt
 large_buffer_align_cnt
 read_pipe_busy_error_cnt
 write_pipe_busy_error_cnt
 trans_pipe_busy_error_cnt
 read_pipe_broken_error_cnt
 write_pipe_broken_error_cnt
 trans_pipe_broken_error_cnt
RAID
 tetris_written
 stripes_written
 partial_stripes
 full_stripes
 blocks_written
 blocks_read
 raid_read_ops
 raid_read_latency
 raid_tetris_cnt
 raid_tetris_latency
 raid_read_io_latency_histo
 raid_tetris_latency_histo
RAIDSTRIPE (RDSTRIPE)
 stripe_size
 stripe_histogram
QTREE
 nfs_ops
 cifs_ops
 internal_ops
AGGREGATE (AGGRE1)
 total_transfers
 user_reads
 user_writes
 cp_reads
 user_read_blocks
 user_write_blocks
 cp_read_blocks
42 | P a g e
 wv_fsinfo_fs_version
 wv_fsinfo_blks_total
 wv_fsinfo_blks_reserve
 wv_fsinfo_blks_used
 wv_fsinfo_blks_used_by_plane0
 wv_fsinfo_blks_blks_rsrv_holes_cifs
 wv_fsinfo_blks_blks_rsrv_holes
 wv_fsinfo_blks_blks_rsrv_overwrite
 wv_fsinfo_blks_rsrv_absents
 wv_fsinfo_blks_snap_reserve_pct
 wv_fsinfo_blks_res_state
 wv_fsinfo_blks_overwrite_slider_pct
 wv_fsinfo_public_inos_total
 wv_fsinfo_public_inos_reserve
 wv_fsinfo_public_inos_used
 wv_fsinfo_private_inos_total
 wv_fsinfo_private_inos_reserve
 wv_fsinfo_private_inos_used
 wv_fsinfo_blkr_cp
 wvblk_past_eof
 wvblk_snap_reserve
 wvblk_zombie_blks
 wvblk_child_delalloc
 wvblk_child_rsrv_delalloc
 wvblk_rsrv_child_holes
 wvblk_rsrv_child_overwrite
 wvblk_rsrv_child_overwrite_always
 wvblk_child_indirect_blk_cnt
 wvbd_active_frees
 wvbd_whole_frees
 wvbd_active_frees_y
 wvbd_owner_changed_y
 wvbd_whole_frees_o
 wvblk_saved_public_fsinfo_inos_total
 wvblk_saved_public_fsinfo_inos_reserve
 wvblk_saved_public_fsinfo_inos_used
 wvblk_saved_private_fsinfo_inos_total
 wvblk_saved_private_fsinfo_inos_reserve
 wvblk_saved_private_fsinfo_inos_used
 wvblk_delalloc
 wvblk_rsrv_delalloc
 wvblk_rsrv_holes_cifs
43 | P a g e
 wvblk_rsrv_holes
 wvblk_rsrv_overwrite
 disk_type
 wvdf_max_frees
 wvblk_child_to_be_reclaimed
 blkr_async_offline
 blkr_async_no_msg
 blkr_async_no_mem
 blkr_async_launched
 blkr_async_completed
 blkr_blocks_scanned
 blkr_free_blocks_scanned
 blkr_super_blocks_scanned
 blkr_aa_blocks_scanned
 blkr_aggrsnap_blocks_scanned
 blkr_segments_scanned
 blkr_full_segments_scanned
 blkr_empty_segments_scanned
 blkr_rejected_segments_scanned
 blkr_rejected_blocks_scanned
 blkr_reads_launched
 blkr_blocks_read
 blkr_blocks_dummy_read
 blkr_blocks_postfiltered
 blkr_blocks_overwritten
 blkr_blocks_reallocated
 blkr_blocks_redirected
 blkr_blocks_redirected_maybe
 blkr_blocks_redirected_noread
 blkr_blocks_redirected_nol1
 blkr_blocks_redirected_noio
 blkr_blocks_redirected_reread
 blkr_blocks_redirected_noverify
 blkr_redirect_susps
 blkr_redirect_ra_map
 blkr_redirect_ra_l0
 blkr_redirect_kireetis_scanned
 blkr_redirect_ra_l1
 blkr_redirect_demand_req
 blkr_redirect_demand_rereq
 blkr_redirect_demand_drop
 blkr_redirect_indirects_inspected
44 | P a g e
 blkr_redirect_indirects_ok
 blkr_redirect_indirects_updated
 blkr_redirect_blocks_updated
 blkr_redirect_blocks_invalid
 blkr_redirect_blocks_ok
 blkr_policy1_reject_reasons
 wvzmb_num_zmsgs_inuse
 wvblk_space_tax
 wvblk_lev0_over_nominal
 wvblk_ind_delalloc
 wv_fsinfo_containment_version_slc
 wv_fsinfo_containment_version_sle
 wv_fsinfo_containment_version_compression
 wv_fsinfo_containment_version_spare1
 wv_fsinfo_containment_version_spare2
 wv_fsinfo_containment_version_highest_slc
 wv_fsinfo_containment_version_highest_sle
 wv_fsinfo_containment_version_highest_compression
 wv_fsinfo_containment_version_highest_spare1
 wv_fsinfo_containment_version_highest_spare2
 delete_log
45 | P a g e
LOTUS DOMINO SERVER PLUGIN
Prequisites
Install Domino Client on your PRTG Probe computer. Configure the connectivity for all target Domino
systems after which you can use the credentials of these systems to allow the connection for the plugin.
Important Note
As the Domino API poses some limitation of concurrent sessions a suggestion to avoid any timeouts (PE18)
is to utilize the PRTG mutex functionality. For each Domino sensor created on a PRTG Probe computer set a
Mutex value DOMINO_MY_PROBE_NAME eg DOMINO_PRB01.
The Domino Base Information Sensor


2 Enter values for device name. Enter the Domino Server name to IP Address/DNS Name.
3 Enter the Domino User and Password to your Windows Credentials Fields. If password is
not used then leave it empty.

7 Enter Sensor name: Domino Base Sensor
8 Choose dominomon.exe from the Exe/Script drop down box
-t:%host –u:%windowsuser –p:%windowspassword –i:base
11 Enter a valid Mutex Name Value like: DOMINO_PRB01
46 | P a g e
Creating the Traveler Monitoring Sensor


3 Enter Sensor name: Domino Traveler Sensor
-t:%host –u:%windowsuser –p:%windowspassword –i:traveler
Creating the Database Monitoring Sensor


3 Enter Sensor name: Domino Database Sensor
4 Enter tags: DOM_BASE
-t:%host –u:%windowsuser –p:%windowspassword –i:database
47 | P a g e
Creating the Platform Monitoring Sensor


3 Enter Sensor name: Domino Platform Sensor
-t:%host –u:%windowsuser –p:%windowspassword –i:platform
Creating the Disks Monitoring Sensor


3 Enter Sensor name: Domino Disks Sensor
-t:%host –u:%windowsuser –p:%windowspassword –i:disks
48 | P a g e
Creating a Domino Monitor with Custom Sensor Channels

The plugin allows you t0 create a Custom sensor with data and presentation of your own choice. The
channel options are stated in a user defined file as CSV fields.
For each channel state the following:
1. The Domino Status value “Traveler.Status.State”

2. Description of the Channel “Domino Traveler State”
3. The Channel presentation type in PRTG “XMLCustom”
4. The Presentation Format Lookup Key “prtgplugins.domino.traveler.mainstate”
5. The Cumulative Value Save Key “MyKeySerial.0001”
6. Show value as Header Info True/false
7. Mininum Value for warnings 0
8. Maximum Value for warnings 0
"Traveler.Status.State","Traveler State","XMLCustom","prtgplugins.domino.traveler.mainstate","","",0,0
"Server.Task == Traveler:","Traveler Task","XMLCustom","prtgplugins.domino.Server.Tasks","","false",0,0
This will result as the following sensor channels:
49 | P a g e
Domino Custom Sensor Channel Options in Detail
1. The full key to Domino status like

“mail.TotalPending”
“Server.AvailabilityIndex”
“Disk.C.Free”
“Server.Sessions.Dropped”
2. Description of The Channel as free text
3. Channel presentation type in PRTG.

- currently the following options are available for presenting the data from Domino
a. “XMLCOUNTER” is simple numeric data to be shown.
b. “XMLPERCENT2” present the data as Percentage values.
c. “XMLBYTESDISK” for presenting Memory, Disk etc in T/M/K/bytes.
d. “XMLTIMESECONDS2” for presenting Time base data like Milliseconds.
e. “XMLCUSTOM” instructs the channel use a lookup value to present the data.
4. This parameter value is used if previous value is XMLCUSTOM and instructs to use the lookup value
stated here.
“prtgplugins.domino.Server.Tasks”
5. This is the “serial key” to save and compare a channel value to show a cumulative value instead of
actual data. As an example “Server.sessions.dropped” is an ever increasing data and if you want to
see only changed value it needs to be saved for comparison. The Serial key is used for identify the
value to be compared.
“MySerKey.001”
6. Instructs to show the value an information on Sensor header. Use this to show values not in
numeric format like Domino Version information. Value is simply true or false.
“true”/”false”
7. Minimum and Maximum values are used to give warnings if they are met. This is not yet automatic,
so you can discard them and set as 0.
50 | P a g e
Creating an example Custom Domino Monitoring Sensor


2 Enter values for device name. Enter the Domino Server name to IP Address/DNS Name.
3 Enter the Domino User and Password to your Windows Credentials Fields. If password is not
used then leave it empty.

7 Enter Sensor name: Domino Custom Sensor
8 Enter tags: DOM_CUSTOM
-t:%host –u:%windowsuser –p:%windowspassword –i:custom –cs:
"C:\Program Files (x86)\PRTG Network Monitor\Custom
Sensors\EXEXML\tests.cfg"
The –cs: is the full path and filename of your Channel configuration file.
51 | P a g e
SHAREPOINT/MOSS SERVER V2 PLUGIN

SharePoint Plugin enables you to monitor SharePoint documents, repositories and activities related to
them giving you a good insight view how the information in SharePoint is stored and being used. It also
allows capacity management by reporting the sizes of different repositories. Additionally it offers views on
user activities related to SharePoint functions and SharePoint Internal Security model.
SharePoint Content Sensor

You can present the information of more than one content database in a single sensor by listing the
content databases of your choice as parameter.
Identifying the SharePoint content database names you need to access the SharePoint
Administrative site
The SharePoint content sensor consists of the following information:
Sites Capacity Counters

Channels explained:
 Count of Sites
 Count of Webs
 Number of Documents in all sites
 Number of Document Folders in all sites
 Number of lists in all sites
 Site usage bytes n all sites
 Trashed site usage bytes in all sites
Sites Usage Counters

Channels explained:
 Total number Documents Checked Out in all sites

 Number of Documents Checked Out in all sites in less than 30 days
 Number of Documents Checked Out in all sites between 30 and 90 days
 Number of Documents Checked Out in all sites over 90 days
 Scheduled Subscriptions
 Immediate Subscriptions
52 | P a g e
Example of creating SharePoint Content Monitoring sensor


2 Enter values for device name and IP Address/DNS Name of your SQL Server hosting the
SharePoint Content Databases
your own values

3 Enter Sensor name: SharePoint Content
4 Enter tags: SPS_CONTENT
5 Choose mossmonitor.exe from the Exe/Script drop down box
%windowsdomain content_db1,content_db2,content_db3 data
SP2010
Example output of content sensor (1 year):
53 | P a g e
SharePoint Auditing sensor

The sensor reports on all user related activities based on SharePoint auditing capabilities. In order to allow
this sensor functionality the auditing must be enabled on the SharePoint environment. If there are some
functions you don’t want to view/report simply omit the auditing within SharePoint and it is reported as
zero.
Example of creating SharePoint Auditing sensor


server
your own values
Create the sensor for Audit Monitoring in PRTG interface:

3 Enter Sensor name: SharePoint Auditing
4 Enter tags: SPS_AUDIT
NTLMDOMAIN:%windowsdomain any audit SP2010
Example output of auditing sensor (2 days):
54 | P a g e
SharePoint Security Auditing sensor

Many times SharePoint is deployed with shared administration within the organizations making it more
vulnerable to human errors and hacking. This sensor allows monitors on changes within the SharePoint
security model adding the possibility to audit and get alerts on changes.
Example of creating SharePoint Security Auditing sensor

Create SharePoint Security Auditing monitoring In PRTG interface:

server
your own values
Create the sensor for Security Audit Monitoring in PRTG interface:

11 Enter Sensor name: SharePoint Security Auditing
12 Enter tags: SPS_SECAUDIT
NTLMDOMAIN:%windowsdomain any secaudit SP2010
55 | P a g e
Other Plugins to be considered with SharePoint monitoring

We suggest you to consider using also these plugins for comprehensive monitoring solution:
 Active Directory Plugin for monitoring AD activity and performance related SharePoint
 IIS Plugin to monitor the Site sessions and Activity related
 SQL Advanced Performance Plugin to maintain database performance
SharePoint Content Sensor Command line

For SQL TCP/IP Connections:
%host %windowsuser %windowspassword %windowsdomain db1,db2,db3,db4 data

[SharePoint version]
Where db1-db4 are the content databases you want to sum up together.
There is no limitation for the number of databases to be combined.
Where SharePoint version can be:
 SP2010 (for 2013 version too)

 SP2007
For using SQL Named Pipes Connections:
%host\PIPE_NAME %windowsuser %windowspassword %windowsdomain

db1,db2,db3,db4 100 [SharePoint version]
56 | P a g e
AMAZON EC2 VOLUME PERFORMANCE MONITORING PLUGIN 1.0

Monitoring Amazon EC2 volumes with following counters:
 Read and Write Bytes

 Read and Write Operations
 Read and Write Total times
 Volume Idle time as percentage
 Volume Queue
Example of output:
Command line:
-a:[AWSaccesskey] -s:[AWSsecretkey] -l:[location] -v:[volumeID]
EC2 Locations [location]:
us-east-1 = Monitoring.us-east-1.amazonaws.com
us-west-1 = Monitoring.us-west-1.amazonaws.com
us-west-2 = Monitoring.us-west-2.amazonaws.com
sa-east-1 = Monitoring.sa-east-1.amazonaws.com
eu-west-1 = Monitoring.eu-west-1.amazonaws.com
ap-southeast-1 = Monitoring.ap-southeast-1.amazonaws.com
ap-northeast-1 = Monitoring.ap-northeast-1.amazonaws.com
Example monitoring Volume vol-444c002d in EU-WEST EC2:
-a:AKISXMXQ -s:6o75ZcfKhPlE7Hgoghqml -l:eu-west-1 -v:vol-444c002d
57 | P a g e
To ensure your Amazon keys won’t be shown in any case place the Secret- and Access keys as Windows
Parameters as follows (Secretkey=Password):
And use them as replacements in actual parameters as follows:
-a:%windowsdomain -s:%windowspassword -l:eu-west-1 -v:vol-444c002d
58 | P a g e
CITRIX MONITORING PLUGINS ROLES
Citrix Monitoring consist of three different plugins:
1. Citrix Licensing and Performance Plugin (RDPMonitor.exe)

Can be targeted to all Citrix Farm Servers to measure Performance related to each role.
- Sensor output is dependent on the target Citrix version

- Supported Citrix version are Metaframe 4 and above
2. Citrix Session Simulation Plugin (ICAMonitor.exe)

Simulate Sessions and Measure performance on individual Citrix XenApp Servers
- Supported Citrix version are Metaframe 4 and above
3. Citrix NetScaler VPX Monitoring Plugin (VPXMonitor.exe)
IMPORTANT NOTE:
As Citrix based solutions rely on Windows Remote Desktop Technology Components too remember to
utilize and benefit other supporting PRTG plugins information too like RDS licensing information, SMB
monitoring protocol, SQL monitoring and Microsoft Clustering plugin as needed.
59 | P a g e
CITRIX/XENAPP LICENSING AND REMOTE DESKTOP PLUGIN V2

Citrix and XenApp monitoring Plugin offers comprehensive views to monitor virtually all vital areas of your
Citrix and XenApp Server farms for Performance and Health.
Citrix / XenApp Performance and Health Monitoring

The main areas that can be monitored in this mode:
 ICA Session Performance Counters

 ICA Metadata Performance Counters
 Secure Ticketing Authority Values
 IMA Networking Performance Counters
 Licensing Performance and Health
 XenApp Server Load Monitoring
The actual output of the sensor varies based on the Server XenApp Roles and Versions in other word the
performance counters are shown only if the data is available. Also a notable feature of the plugin is the
capability to support all Citrix Versions automatically: In case you change the roles or the versions of the
servers the plugin output always reflects the current setup without any change to it.
Figure 1 Example of Virtualized XenApp Cluster Monitored with ICA, RDP, SQL, Cluster and Volume Fragmentation Plugins.
Please also use RD licensing sensor in conjunction to ensure the operation of your XenApp/Citrix farms.
60 | P a g e
Built in Counters with Automatic Warning levels

There are several Best Practices based Counter values that automatically change the sensor to warning
status:
Mode –i:CORE and –i:META:
 Data Store Connection Failures

Status Warning and message “Check DS Connection.” If datastore connectivity is lost.
 Number of Busy XML Threads
Status Warning and message “Check XML Threads.“ if Number of Busy XML Threads is 10 or
above.
 Resolution Work Item Queue Executing Count (In sensor ‘RWIQE Count’)
OR
ResolutionWorkItemQueueReadyCount (In sensor ‘RWIQR Count’)
In both cases Status Warning and message “App Lauch Problem? “if Number of Queue is 1 or
above.
Mode –i:CORE and –i:IMA:
 IMA Connections
Status Warning and message “IMA Connection?” If Network connectivity is lost.
Mode –i:CORE and –i:LIC:
 LIC Last Check Out

Status Warning and message “LICSRV Performance?“ if Number of latest License Checkout time
was 5 seconds or above.
 LIC Connect Failure
Status Warning and message “LIC Connection?“ if the latest License Checkout was missed.
Mode –i:CORE and –i:LOAD:
 Server Load
Status Warning and message:
Server Load at 100 % Results: “Server Full Load!“
Server Load at 200 % Results: “Server Licensing Error!“
The –i:core option combines all 4 sensor information as a single sensor.

Reporting Meta, Ima, Lic and Load sensor information as a single sensor, use index option:
-i:core
Reporting only Meta and Load sensor information as a single sensor, use index option:
-i:meta,load
Note: The sensor options report the information ONLY if it’s available based on the
installed Citrix Server roles, so this information may vary per Citrix Server.
61 | P a g e
Citrix / XenApp ICA Session Bandwidth Monitoring
Figure 2Citrix Presentation Server 4.5 Data example
Figure 3 XenApp 6.5 Server Data example
62 | P a g e
Example of creating Citrix / XenApp Performance sensor

Create ICA Session monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your Citrix / XenApp Server
your own values
Create the sensor for ICA Session Monitoring in PRTG interface:

7 Enter Sensor name: ICA Sessions
8 Enter tags: CTX_PERF_ICA
9 Choose rdpmonitor.exe from the Exe/Script drop down box
-t:%host -u:%windowsuser –p:%windowspassword
-d:%windowsdomain –i:ica
63 | P a g e
Citrix / XenApp Session Quantity Monitoring

This mode of the sensor you can monitor the following data:
 Active Sessions
 Disconnected Sessions
 Sessions
 Logins Enabled
(0=No logins, 1=Logins allowed)
Reported on versions above Presentation server 4.5
Example of creating Citrix / XenApp Session sensor

Create Session monitoring In PRTG interface:

your own values

7 Enter Sensor name: Sessions
8 Enter tags: CTX_PERF_SESSION
-t:%host –u:%windowsuser –p:%windowspassword
-d:%windowsdomain –i:session
64 | P a g e
Citrix / XenApp Core Performance and Health Monitoring

The following areas are reported if the role and counter data is available:
 Server Load Percentage (XenApp 6.x Only)

 Licensing Response Times
 IMA Connectivity Number of Connections, Bytes In and Out
 Secure Ticketing Authority Counters
 Metadata related Counters
Example of creating Citrix / XenApp Core Performance sensor

Create Session monitoring In PRTG interface:

your own values

7 Enter Sensor name: Core Performance
8 Enter tags: CTX_PERF_CORE
-d:%windowsdomain –i:core
65 | P a g e
Licensing mode
The main function of the plugin is to report the percentage of active use per license type. The plugin
automatically reports the usage percentage of all licenses entered within the Citrix Licensing system.
Example of creating Citrix Licensing sensor

Create Citrix License monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your Citrix Licensing server
your own values

7 Enter Sensor name: SharePoint Security Auditing
8 Enter tags: CTX_LICENSING
-d:%windowsdomain –i:lic
66 | P a g e
Example of creating Citrix Licensing Pool sensor

Create Citrix License monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your Citrix Licensing server
your own values

7 Enter Sensor name: Citrix Licensing
8 Enter tags: CTX_LICPOOL
-d:%windowsdomain –i:pool
Debugging Citrix Licensing Connectivity

Some times the Citrix licensing WMI interface becomes corrupted thus the sensor loses connectivity. Here
are some instructions how to check and restore it.
Checking that Licensing WMI is registered correctly use WMIExplorer (http://www.ks-

soft.net/hostmon.eng/wmi/index.htm) to connect to root\citrixlicensing namespace.
If there is an error generated follow the instructions to restore the services in correct state.
1. Go to your License server.
2. Go into C:\Program Files\Citrix\Licensing\LicWMI
3. Make a backup of Citrix_Licensing_WMI.mof - Make sure the backup does NOT have a .mof extension.
4. Open Citrix_Licensing_WMI.mof in Notepad.
5. Remove HostingModel = "LocalServiceHost";
6. Open CMD.exe, change to the dirirectory listed in step 2, run the following command:
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
(Link: http://support.citrix.com/article/CTX119767)
67 | P a g e
Remote Desktop monitoring indexes are still functional to enable older systems backwards
compatibility but not supported in new installations.
68 | P a g e
CITRIX XENDESKTOP 7.x AND XENAPP 7.x MONITORING ONLY

The following Monitoring is only applicable to XenApp and XenDesktop 7.x Citrix versions but also
previously described Citrix monitoring is applicable and should not be discarded.
Monitoring XenDesktop and XenApp 7.x Farms

Citrix has now bundled Edge Sight functionality into Citrix editions and is called the Director. Unless your
organization has acquired the Platinum-level license the information available within the Director is more
or less limited. Even in case you have the Edge Sight monitoring in place the plugin functionality offers the
incorporating of monitoring to PRTG.
As Edge Sight monitors only Citrix platform we strongly encourage you to incorporate also the following
Plugins to PRTG monitoring environment to supplement the standard PRTG monitoring capabilities:
• Active Directory (Admonitor)
• File Services (SMBMonitor)
• SQL Services (SQLMonitor) / Cluster Monitoring (ClusMonitor)
• Windows RDP Licensing (Rdpmonitor)
Please notice that Citrix has also revised its product line naming since XenDesktop 7 publishing:
 Citrix XenDesktop 7
 Citrix XenDesktop 7.1
 Citrix XenApp 7.5
Are versions all equal in the following documentation and can be monitored the same way.
New only XenApp 7.x based functionality that can be monitored:
 Farm Server Load (Per XenApp Farm)

 Farm Slow Logons (Per XenApp Farm)
 Farm Broker Connections (Per XenApp Broker Server)
 Session Brokering Errors (Per XenApp Broker Server)
 XenDesktop Apps (Per XenApp Server)
 Citrix End User Experience Monitoring (Per XenApp Server)
 Citrix Logon Performance (Per XenApp server)
69 | P a g e
Monitoring XenApp/XenDesktop 7.x Farm Server Load and Farm Sessions Count
Citrix XenDesktop 7.1 and XenApp 7.5 Citrix Server load is not anymore available via WMI as in older
versions. Instead this is available on the database server hosting your Citrix configuration databases thus
making it easier to set up the consolidated monitoring and also being automatically updated in case of
changes in the publication server architecture.
The Plugin option reports the following information on channels:
 Name of the server and its total load percentage

- as defined in the load balancing rules
 _Registered
Number of servers registered in the Citrix environment. Since v 1.7.7 these servers are reported in
Status field by name.
 _Unregistered
Number of server not registered in the Citrix environment
 NEW in Version 1.7.7: _InMaintenance

Number of Servers in Maintenance mode. These servers are reported by name in the Status field.
70 | P a g e
Setting up XenDesktop Farm Server Load Sensor

Create Citrix XenApp 7.5 Farm Server Load monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of the SQL server hosting your
Citrix Configuration Database.
your own values
Create the sensor for Farm Server Load in PRTG interface:

7 Enter Sensor name: Farm Server Load
8 Enter tags: CTX_XA7LOAD
-d:%windowsdomain -i:xdload -db:xd7prodDatabase [–e1:Server1 –
e2:server2 …-e9:server9]
(The Citrix configuration database is identified by the option -db:xd7prodDatabase
and the SQL instance can be identified by -t:%host\instance_name if needed)
With Optional e1:…e9: parameters you can exclude up to nine servers being listed in the
monitoring, for any reason.
Setting up XenDesktop Farm Server Sessions Count Sensor

Exactly as the previous setup but instead use sensor option –i:xdsessions and give the sensor a different
name like “Farm X Sessions Count”
71 | P a g e
Monitoring XenApp/XenDesktop 7.x Farm for Slow logons

Logon duration is a typical area of concern for Citrix administrators. The server logon performance makes a
great difference to end user experience. The plugin helps to identify, initiate troubleshooting and help
optimize logons by showing when slow logons occur and where that time is spent on each server, like the
user profile, Group Policy processing or Active Directory performance. This sensor is based on the Farm
database information so it automatically relates to any changes in the publishing infrastructure. Also as the
information on the sensor is anonymous it can be used to report service levels if needed.
72 | P a g e
Setting up XenDesktop Farm Slow Logons Sensor

1 Create a new device if needed

2 Enter values for device name and IP Address/DNS Name of the SQL server hosting your
Citrix Configuration Database.
your own values

7 Enter Sensor name: Farm Slow Logons
8 Enter tags: CTX_XA7SLOW
-t:%host -u:%windowsuser -p:%windowspassword
-d:%windowsdomain -i:xdslow -db:xd7prod
(The Citrix configuration database is identified by the option -db:xd7prod and the SQL
instance can be identified by -t:%host\instance_name if needed)
73 | P a g e
Monitoring XenApp/XenDesktop 7.x Farm Broker Connections
The following Connector Statuses can be monitored:
 Broker AD Identity Conn.

 Broker Service Conn.
 Configuration Logging Conn.
 Configuration Service Conn.
 Delegated Admin Conn.
 EnvTest Conn.
 Host Service Conn.
 Machine Creation Conn.
 Monitor Conn.
 xQuerytime ms
 xTotal Errors
74 | P a g e
Setting up XenDesktop Farm Broker Connections Sensor


2 Enter values for device name and IP Address/DNS Name of the Citrix Controller.
your own values

7 Enter Sensor name: Broker Connections
8 Enter tags: CTX_XA7BRKSTAT
-d:%windowsdomain -i:brkchk
75 | P a g e
Monitoring XenApp/XenDesktop 7.x Session Brokering Connections
The following Logs Events are being monitored and alerted for:
 Application is Disabled ID 1107

 Desktop Machine already has a Session ID 1108
 Desktop Machine in Maintenance Mode ID 1105
 Desktop Machine Refused Connection ID 1102
 Desktop Machine Session Already Active ID 1103
 Desktop No Longer Available ID 1109
 Folder Redirection Errors ID 1085
 Folder Redirection Errors ID 1112
 HTTP Requests ID 2013
 Licensing Error ID 1160
 Licensing Server Connection ID 1151
 Machine Base Settings ID 1065
 No Desktop Machine is Available ID 1101
 Other Launch Failure ID 1100
 Other Launch Failure on Reconnect ID 1104
 Requested Protocol Type is Not Supported ID 1106
 User Credentials Failure ID 2100
 xQuerytime ms
 _Total Errors
76 | P a g e
Setting up XenDesktop Session Brokering monitoring Sensor


14 Enter values for device name and IP Address/DNS Name of the XenApp Controller.
your own values

19 Enter Sensor name: Session Brokering
20 Enter tags: CTX_XA7BRKLOGS
-d:%windowsdomain -i:brklog
77 | P a g e
Monitoring XenApp/XenDesktop 7.x Sessions and Applications

There many other solutions where host resources usage monitoring is based on identifying ‘Top processes’.
We think different: Our solution reports the quantities of actual applications started on the host giving you
a crystal clear view what applications are utilizing your host resources. The Plugin functionality is available
on both XenApp and XenDesktop platforms but as in XenDesktop the session can contain multiple started
applications making it more difficult to correlate the resource usage in traditional monitoring tools.
This sensor can be used with XenApp 6.x versions as well.
The following can be monitored:
 Applications Running: Application’s Internal Name

 Active Sessions
 Applications
 Lingering Sessions
 Querytime ms
78 | P a g e
Setting up XenDesktop Session and Applications monitoring Sensor


2 Enter values for device name and IP Address/DNS Name of the publishing server.
your own values

7 Enter Sensor name: Sessions and Applications
8 Enter tags: CTX_XAAPPS
-d:%windowsdomain -i:hdxap
79 | P a g e
Monitoring XenApp/XenDesktop 7.x Citrix Logon Performance
The following can be monitored:
 Avg Total
 Avg Logon
 Min Logon
 Max Logon
 Avg GPO
 Min GPO
 Max GPO
 Avg Prof
 Min Prof
 Max Prof
 Sessions
 Querytime ms
80 | P a g e
Setting up XenDesktop Logon Performance Sensor


your own values

19 Enter Sensor name: Logon Performance
20 Enter tags: CTX_XA7LOGPERF

-d:%windowsdomain -i:hdxlon
For all active sessions Logon Performance
OR

-d:%windowsdomain -i:hdxlonts -sp:5
For Performance of sessions Logged On since last 5 Mins
81 | P a g e
Monitoring XenApp/XenDesktop 7.x Citrix End User Experience (EUEM)

The average round trip time. Round trip time (RTT) is a measure of network response. Citrix EdgeSight
agents measures the round-trip time passively during a network connection creation. Whenever a TCP/IP
socket connection is made, the agent records the RTT for that socket connection to the server. RTT can
sometimes be measured to be zero.
The following is measured by the sensor:
 BandWith Input Used

 BandWith Output Used
 Net Latency Avg
 Net Latency Min
 Net Latency Max
 RoundTrip Avg
 RoundTrip Min
 RoundTrip Max
 Server Idle
82 | P a g e
Setting up XenDesktop Citrix End User Experience Monitoring (EUEM) Sensor


your own values

7 Enter Sensor name: End User Experience Monitoring
8 Enter tags: CTX_XA7EUEM

-d:%windowsdomain -i: hdxeuem
83 | P a g e
CITRIX/XENAPP APPLICATION SIMULATION AND MONITORING

XenApp Application monitoring sensor uses actual ICA sessions and measures the time between different
steps giving administrators a good tool to verify systems performance and tools root cause investigation.
Of business point of view the sensor can be used in two main modes to produce evidence of the operations
of your Citrix farms:
 Ensuring that you Citrix farm is operational

o Place the probe measuring in your datacenter or a location close to it
 Measuring Citrix User Performance
o Place the probe in your remote location
(please note that the screen shots produced by the sensor are always stored locally on the
probe)
The sensor is always based on simulating an application per server:

If you have three Citrix servers you want to monitor you’ll need three sensors targeted to each of these
servers. In active/passive Citrix clusters the application can be targeted to cluster only if needed.
The following information is available via the channels:
 ICA connection time

 ICA session login time
 Published application:
o Application Launch time (with Recordings)
o Screen Shot saving enabled
o History view of Application Screen Shots
 ICA session logoff time
 Errors Count
84 | P a g e
The following picture illustrates the connection activity related to sensor output information:
Example of actual sensor information:
85 | P a g e
IMPORTANT NOTES:
Simulating XenApp sessions can be a comprehensive load to both Client machine and XenApp Server.
Setting up the environment for this is complicated and requires technical skills and understanding of the
steps made. It is advised to closely monitor the workload caused by this functionality to XenApp
infrastructure.
The ICA plugin sensor is always targeted to the XenApp Application Server regardless how your User
Clients start their application sessions e.g. via Web Interface. The reason for this is to avoid any load
balancing features built in the structure (Windows or XenApp). This way you are ensured to get readings
on all servers monitored.
Installation steps to be followed on the computer simulating the sessions

1. Install a dedicated PRTG Probe according to PRTG Instructions
2. Install ICA Client software on the probe machine
3. Apply registry keys
4. Modify PRTG Probe service properties and restart the service
5. Install .NET 3.5 environment
6. Install PRTGPlugins.msi
7. Apply any updates
86 | P a g e
STEP 2. Install ICA Client

You can download legacy ICA Clients from:
http://www.xenappblog.com/downloads/?category=2
We have confirmed functionality with ICA Client version 12.1.44.1
NOTE: Install the Full version of the available ICA Clients
STEP 3. Apply the registry keys

The following ‘AllowSimulationAPI’ DWORD value must be created HKLM\Software\Citrix\ICA
Client\CCM. Under that key a DWORD value of 0 or 1 disables and enables access to the ICA Session
object. In 64-bit environments the corresponding key is under
HKLM\SOFTWARE\Wow6432Node\Citrix\ICA Client\CCM.
x86 based systems registry key hive:
NOTE: x64 based systems registry key hive is different:
87 | P a g e
STEP 4. PRTG Probe Service Modification

Allow PRTG Probe Service to interact with desktop
1. Start Computer Management

2. Services
3. PRTG Probe Service Properties
4. Logon properties
5. Check ‘Allow Service to interact with desktop’
For STEPS 5,6 and 7 refer to chapter PRTG PLUGINS INSTALLATION ENVIRONMENT REQUIREMENTS
Choosing the XenApp Application for the simulation

There are requirements for the application name being used for the simulation. The application has to be
published to XenApp farm with single label e.g. it has to be continuous like ‘desktop’ or ‘outlook’.
‘microsoft outlook’ will not work.
Dameware, PCDUO and PowerGUI can be used in simulation:
It is also recommended that you create a dedicated published application and user credentials for this use
in order to separate the simulations from normal operations.
88 | P a g e
Example of creating Citrix Session Simulation sensor

Create ICA Session monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your Citrix Session server
your own values. Credentials used can be normal type.
Create the sensor for ICA Session monitoring in PRTG interface:

7 Enter Sensor name: Citrix Session Monitoring
8 Enter tags: CTX_SESSION
9 Choose icamonitor.exe from the Exe/Script drop down box
-t:%host -u:%windowsuser -p:%windowspassword -d:%windowsdomain
-i:session -po:PCDUO -to:200 -pi:pcduo -st:4 -lc:30 -ic:12
-po:PCDUO
Starts a program named “PCDUO”.
-ST:4
A delay of 4 seconds after successful logon before the screen shot is
taken.
-PI:pcduo
The latest screen shot is saved to pcduo.bmp and pcduo.gif files.
-LC:30
Additionally there’s a screen shot log picture built with 30 latest
screen shots animated with date stamps pcduo_log.gif.
-ic:12
Instructs the sensor to allow maximum of 12 sensor sessions being run
on the probe. If this amount is exceeded then all sessions are
terminated and the process is started again.
-TO:200
Timeout for the whole Procedure is 200 Seconds after which the sensor
aborts the measurements.
89 | P a g e
Tips and tricks

You can define the sensor in more portable way by using the sensor parameters more effectively:
-po:%name -to:200 -pi:%device_%name
The name of the PRTG sensor is being used as the Citrix Program name to be monitored and the screen
shot name will include the citrix host information as well.
Above example will result in two files named:
 Opaser6201_CMD.gif
Containing the latest screen shot of the application
 Opaser6201_CMD_LOG.gif
Containing the latest number of screen shots defined with parameter: –LC
Adding new Applications or Servers to monitor can be easily done just by cloning the device or the sensor
and changing the sensor name.
Operations
It’s is important to know that the sessions simulated are not visible to the desktop on the probe computer
and BY DEFAULT there’s a maximum of two (2) consecutive sessions allowed. If the plugin detects more
than two ICA sessions it will terminate them all and restart the simulation. You can increase the maximum
consecutive sessions with parameter –IC or by using PRTG’s own mutex values
90 | P a g e
NETSCALER VPX MONITORING PLUGIN

There are several different sensor modes available for NetScaler Monitoring:
1. NetScaler Base Monitoring

2. NetScaler Certificates Monitoring
3. NetScaler Load Balancing Virtual Servers Monitoring
4. NetScaler Gateway Virtual Servers Status Monitoring
5. NetScaler Gateway Virtual Server Performance Monitoring
6. NetScaler Gateway Statistics Monitoring
7. NetScaler Modes Monitoring
8. NetScaler Features Monitoring
9. NetScaler AAA Statistics Monitoring
10. NetScaler Configuration Unsaved Monitoring
11. NetScaler Latest Backup Age Monitoring
91 | P a g e
NetScaler Base Monitoring
Example of creating NetScaler VPX Base Monitoring Sensor

Create NetScaler VPX monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your NetScaler Device
3 Enter your credentials for Linux Systems
Create the sensor NetScaler VPX Base Monitoring in PRTG interface:

7 Enter Sensor name: NetScaler VPX Base
8 Enter tags (optional): VPX_BASE
9 Choose VPXMonitor.exe from the Exe/Script drop down box
-t:%host -u:%linuxuser -p:%linuxpassword -i:stats
92 | P a g e
NetScaler Certificates Monitoring

Lists all installed Certificates by name and their days left. Also a generic channel is created for least days left
certificate for generic alerting purposes.
Example of creating NetScaler Certificates Monitoring Sensor

Create the sensor NetScaler Certificates Monitoring in PRTG interface:

3 Enter Sensor name: NetScaler Certificates
4 Enter tags (optional): VPX_CERT
-t:%host -u:%linuxuser -p:%linuxpassword -i:certs
93 | P a g e
NetScaler Load Balancing Virtual Servers Monitoring

Monitor the states of your Load Balancing Virtual Servers.
Example of creating NetScaler Load Balancing Virtual Servers Monitoring Sensor

Create the sensor for NetScaler Load Balancing Virtual Servers Monitoring in PRTG interface:

3 Enter Sensor name: NetScaler Load Balancing Virtual Servers
4 Enter tags (optional): VPX_LBVS
-t:%host -u:%linuxuser -p:%linuxpassword -i:vslb -e1:”Exclusion
1” … -e9:”Exclusion 9”
94 | P a g e
Excluding Virtual Servers from Sensor

There’s two ways to exclude virtual servers from the monitoring, either by parameters from sensor settings
or by a special settings file (VPXExclusions.ini) if you need more than 9 exclusions. The file method allows
you to exclude up to 100 virtual servers from the monitoring.
Using the sensor parameter method

The excluded virtual Servers are given by –e1:”ViRtUaL SrV NaMe” until –e9:”name” and the names are
case sensitive.
Using the exclusion file method

The excluded names are given in the VPXExclusions.ini file located in the same folder with the plugin. The
file structure is the following:
[VPXHTTP]
ex0=" ViRtUaL SrV NaMe"
ex1=" ViRtUaL SrV2 NaMe"
ex100=” ViRtUaL SrV100 NaMe”
Using the file method doesn’t require any additional parameters for the sensor.
95 | P a g e
NetScaler Gateway Virtual Servers Status Monitoring

Virtual Servers Status and AAA users count.
Example of creating NetScaler Gateway Virtual Servers Monitoring Sensor

Create the sensor for NetScaler Gateway Virtual Servers Monitoring in PRTG interface:

3 Enter Sensor name: NetScaler Gateway Virtual Servers
4 Enter tags (optional): VPX_GWVS
-t:%host -u:%linuxuser -p:%linuxpassword -i:gwvsstat
96 | P a g e
NetScaler Modes Monitoring

You can ‘lock’ and monitor your Netscaler Modes changes in PRTG
Example of creating NetScaler Modes Monitoring Sensor

Create the sensor for NetScaler Modes Monitoring in PRTG interface:

3 Enter Sensor name: NetScaler Modes
4 Enter tags (optional): VPX_MODES
-t:%host -u:%linuxuser -p:%linuxpassword -i:mode
97 | P a g e
NetScaler Features Monitoring

You can ‘lock’ and monitor your NetScaler Features changes in PRTG
Example of creating NetScaler Features Monitoring Sensor

Create the sensor for NetScaler Features Monitoring in PRTG interface:

3 Enter Sensor name: NetScaler Features
4 Enter tags (optional): VPX_FEATURES
-t:%host -u:%linuxuser -p:%linuxpassword -i:feat
98 | P a g e
NetScaler Gateway Statistics Monitoring
Example of creating NetScaler Gateway Statistics Monitoring Sensor

Create the sensor for NetScaler Gateway Statistics Monitoring in PRTG interface:

3 Enter Sensor name: NetScaler Gateway Statistics
4 Enter tags (optional): VPX_GWSTATS
-t:%host -u:%linuxuser -p:%linuxpassword -i:vpnstats
99 | P a g e
NetScaler Gateway Virtual Server Performance Monitoring
Example of creating NetScaler Gateway Virtual Server Performance Monitoring Sensor


3 Enter Sensor name: NetScaler Gateway Virtual Server Performance
4 Enter tags (optional): VPX_GWVSPERF
-t:%host -u:%linuxuser -p:%linuxpassword -i:gwvsperf
100 | P a g e
NetScaler AAA Statistics Monitoring
Example of creating NetScaler AAA Statistics Monitoring Sensor


3 Enter Sensor name: NetScaler AAA Statistics
4 Enter tags (optional): VPX_AAASTATS
-t:%host -u:%linuxuser -p:%linuxpassword -i:aaastats
101 | P a g e
NetScaler Configuration Backup Age Monitoring

Easily monitor the age and name of the latest NetScaler backup file. Backup age is reported by total days
and total hours. The file name of the backup is reported on the sensor status line.
Example of creating NetScaler Configuration Backup Age Monitoring Sensor


3 Enter Sensor name: NetScaler Configuration Backup Age
4 Enter tags (optional): VPX_CFGBUAGE
-t:%host -u:%linuxuser -p:%linuxpassword -i:cfgbu
102 | P a g e
NetScaler Configuration Unsaved Monitoring

Allows administrators to ensure that all changes on the configuration are actually saved after a preset time
period. If not an alert is raised by the sensor.
By default the sensor reports ok, If no pending configuration changes exists.
When changes are applied a Safety Time (configured by –st: parameter, default 15 min) starts running and
sensor will report the age of the last configuration saved in total Minutes, Hours and Days. Also Safety Time
left is being reported and sensor will remain Ok until changes are saved or Safety Time is exceeded.
103 | P a g e
If safety time exceeded the sensor will change to Warning and report the exceeded time in minutes.
The sensor will remain in Warning state until changes and saved.
Example of creating NetScaler Configuration Backup Age Monitoring Sensor


3 Enter Sensor name: NetScaler Configuration Unsaved
4 Enter tags (optional): VPX_CFGUNSAVED
-t:%host -u:%linuxuser -p:%linuxpassword -i:conf –st:90
Where –st:90 states a 90 minutes safety time.
104 | P a g e
REMOTE DESKTOP SERVICES MONITORING (RDS 2XXX)

Basically the same plugin (rdpmonitor.exe) used for Citrix monitoring enables monitoring of all the roles
Remote Desktop Services (RDS) holds in Windows Server 2008 and upwards. This means that the following
six roles can be monitored. See also Remote Desktop Session Simulator.
 RD Session Host
 RD Virtualization Host (In dev)
 RD Connection Broker (In dev)
 RD Gateway
 RD Web Access (In dev)
 RD Licensing
105 | P a g e
RD Session Host Monitoring

For the RD Session Host role the following values are being measured:
 Bandwidth TCP Avg

 Bandwidth UDP Avg
 Frames Input Avg
 Frames Output Avg
 Frames Skipped for Client
 Frames Skipped for Net
 Frames Skipped for Server
 Frames Source Avg
 Graph Compr. Avg
 Sent Rate P0 Avg
 Sessions Active
 Sessions Inactive
 Sessions Total
First, an alert should be generated when the number of active RDS sessions reaches a defined number of
sessions (Sessions Active). Second, an alert can be generated when the number of inactive RDS sessions
reaches a defined number of sessions (Sessions Inactive). Third, an alert should be generated when the
value of Frames skipped for poor Network Performance is detected (Frames Skipped for Net). And forth, an
alert should be generated when the value of Frames skipped for poor Server Performance is detected
(Frames Skipped for Server).
106 | P a g e
RD Gateway Monitoring
The number of sessions that run through the RD Gateway are monitored with the following values for
alerting:
 Data Received Avg Per Session

- Average Data in kilobytes received in active sessions
 Data Sent Avg Per Session
- Average Data in kilobytes sent in active sessions
 TSGW Active Sessions
- Number of active sessions on Gateway
 TSGW Idle Sessions
- Number of inactive sessions on Gateway
 TSGW Sessions
- Total Number of sessions on Gateway
107 | P a g e
RD Licensing Monitoring
The Plugin is capable of monitoring Remote Desktop licenses for amounts and percentage used.
108 | P a g e
RD Virtualization Host Monitoring

In development
109 | P a g e
RD Connection Broker Monitoring

In development
110 | P a g e
RD Web Access Monitoring

In development
111 | P a g e
Example of creating RDS 2012 Session Host Monitoring Sensor

Create RDS 2012 Session monitoring In PRTG interface:
1 Create a new device of your RD Session Host(s)

2 Enter values for device name and IP Address/DNS Name of your RD Session Host server
Create the sensor for RDS 2012 Session monitoring in PRTG interface:

7 Enter Sensor name: RDS Session Monitoring
8 Enter tags: RDS_SESSION
-i:rdsfx
112 | P a g e
Example of creating RDS 2012 Gateway Monitoring Sensor

Create RDS 2012 Gateway monitoring In PRTG interface:
1 Create a new device of your RD Gateway Host(s)

2 Enter values for device name and IP Address/DNS Name of your RD Gateway server
Create the sensor RDS 2012 Gateway monitoring in PRTG interface:

7 Enter Sensor name: RDS Gateway Monitoring
8 Enter tags: RDS_GATEWAY
-i:rdsgw
113 | P a g e
Example of creating RDS 2012 Licensing Monitoring Sensor

Create RDS 2012 Licensing monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your RD license server
Create the sensor RDS 2012 Licensing monitoring in PRTG interface:

7 Enter Sensor name: RDS Licensing Monitoring
8 Enter tags: RDS_LIC
-i:rdslic
114 | P a g e
Create RDS 2012 License Use monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your RD License server
Create the sensor RDS 2012 License Use monitoring in PRTG interface:

7 Enter Sensor name: RDS License Use Monitoring
8 Enter tags: RDS_POOL
-i:rdsuse
115 | P a g e
REMOTE DESKTOP SERVICES SESSION SIMULATOR (RDS 2XXX)

RDS Simulator emulates user activity on your RD Sessions hosts to check the capabilities and performance.
There are two different modes; Application and Desktop only -modes.
Conditions for Session Monitoring (Important!)

There are specials requirements for using Session monitoring in your RDS Environment:
 NLA (Network Level Authentication) is required to be disabled

 For Application Session Simulation mode, Command Prompt must be published to user ID used in
monitoring. (CMD.exe in windows\system32-folder)
116 | P a g e
Creating a RD Application Session Simulation with MSPaint

Create RDS 201X Desktop monitoring In PRTG interface:
1 Create a new device of your RD Session Host(s)

2 Enter values for device name and IP Address/DNS Name of your RD Session Host server
Create the sensor RDS 201X Application Simulation monitoring in PRTG interface:

7 Enter Sensor name: RDS Session Host Monitoring
8 Enter tags: RDS_APPSIMPAINT
9 Choose rdpsimulator.exe from the Exe/Script drop down box
-to:40 -wp:"c:\windows\system32\mspaint.exe" -
wd:"c:\windows\system32"
-to: parameter is used for the timeout

-wp: parameter is used for the published application (with full path) to be started on server.
-wd: parameter is the working folder for the application
For the desktop simulation only, omit the parameters –wd and –wp from the sensor settings.
117 | P a g e
Parallels Remote Access Server (2X RAS) Monitoring

Parallels offers 2X Remote Access Server Monitoring via it's built-in reporting features. However this
reporting database information does not always reflect all changes applied within the 2x Server
Infrastructure as this information is stored on the 2x Server's SQLite databases. Combination of the two
database information allows monitoring of both performance data of 2X point of view and more
importantly to monitor each servers update frequency to the reporting database. This allows verification of
proper operations for each 2x Server in the configuration.
Prerequisites
The plugin requires access to both 2x RAS databases: SQL based Reporting and SQLite based Configuration
databases. The SQL Reporting database can be used as in 2x server configuration connection based on the
rasreportingview user.
If the PRTG probe hosting computer is not in the same domain as the reporting server a set of separate
SQL based authentication information needs to be applied.
Creating the hidden share on 2x RAS server for accessing the SQLite Configuration DB
The share allowing access to you SQLite DB hosted on your 2x RAS main servers can be created as your
organization requires.
the SQLIte databases on the 2x servers are located in the following folder (in case of def install) :
C:\Program Files (x86)\2X\Application Server\Appdata
In this example the rasraporting user is being applied for accessing the hidden share appdata$. The share
should be read only type in order ensure security.
118 | P a g e
Creating the SQL User credentials for accessing the SQL Reporting Database
In this example a SQL user named rasreportingview is created. Naturally this can be anything else of your
desire. The user password in the example is PassWord1.
119 | P a g e
Creating the 2x RAS Monitoring Sensors

In this example the previously created users and shares are being used.
Optional parameter –to:2 instructs the sensor allow 2 minutes of timeout for any server to report on
the reporting database before changing it to warning. Using the parameter is optional and the default value
is 2.
The sensor for monitoring the Servers memory performance is created exactly the same but
-i:memperf option is used instead.
Also replace the -cb:\\MY2XRASSERVER\appdata$ information with your server name and share.
Create 2x RAS monitoring In PRTG interface:
1 Create a new device of your 2x Reporting SQL Server Host

2 Enter values for device name and IP Address/DNS Name of your SQL server
Create the sensor 2x RAS Processor performance monitoring in PRTG interface:

7 Enter Sensor name: 2x RAS Processor performance
8 Enter tags: 2X_PROC
9 Choose 2xsmonitor.exe from the Exe/Script drop down box
-ru:rasreportingview -rp:PassWord1 -i:procperf
-cb:\\MY2XRASSERVER\appdata$ [-to:2]
120 | P a g e
REMOTE PING V2 PLUGIN
Enables pinging of multiple targets from single probe. Target types can be NetBIOS names, ip-addresses,
FQDN (Fully Qualified Domain Name) or internet names or any variation of these.
Sensor enters Warning status if ping timeout value (2000 msec) is met or target(s) cannot be resolved.
Respectively the channel data is set to -1 if timeout is met and -2 if target cannot be resolved.
In sensor status the list of not resolved targets is shown.
Command line:
host1 ip1 fqdn1 www1
Where:
[host1] is the name of the target host

[ip1] is the ip address of the target
[fqdn1] is the fully qualified domain name
Example Output of Channels for Pinging Servers for 30 days:
121 | P a g e
IIS/BITS SERVER V2 PLUGIN

IIS enables monitoring IIS Sessions, data and files transferred.
Command line:
%host %windowsuser %windowspassword NTLMDOMAIN:%windowsdomain 10 IIS8
Where:
10 = is fixed index for future usage
IIS8 = Is the IIS version
Possible values are IIS6, IIS7 and IIS8
122 | P a g e
DYNAMICS AX/AOS COMMUNICATIONS SERVER V2 PLUGIN

General Information
Enables the capability to view vital performance data of AOS instances within the servers:
1. Microsoft Dynamics Application Object Server Performance

2. Client Performance
3. Dynamics Enterprise Portal Performance
The plugin supports the following Dynamics AX versions: Microsoft Dynamics AX 2012 R3, Microsoft
Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack and Microsoft Dynamics AX 2012
Example Output of Channels of AOS instance:
123 | P a g e
Dynamics AX Application Object Server Instance Performance
AOS Performance Monitor Channels:
 Active Sessions
 Bytes Received (per interval)
 Bytes Sent (per interval)
 Cache Clears (per interval)
 Cache Clears AOS Sync (per interval)
 Cache Flushes (per interval)
 Cache Hits (per interval)
 Cache Misses (per interval)
 Cache Recs Deleted (per interval)
 Cache Select Hit (per interval)
 Client Requests (per interval)
 Server Requests (per interval)
 Sessions Created (per interval)
Per interval counters show the activity between measuring two points not absolute values of the
counters.
TOTAL SESSIONS and ACTIVE SESSIONS in AOS Performance
The Dynamics AX AOS is regularly validating Client sessions in order to free sessions from inactive Clients.
This is necessary as otherwise over the time inactive Client sessions would use up the available user
licenses.
 Both on the Client and the AOS a background thread exists that is running in a loop
 The background thread on the AOS is every 210 Seconds invalidating all active sessions (marking
them as inactive). Within the next 210 Seconds the sessions have to be validated by the Clients
again (marked as active) otherwise the sessions are considered as inactive and terminated.
 Whenever the Client is talking with the AOS the corresponding session is marked as active. So if the
AOS has marked the Client session as inactive, it is now set as active again. If the session was active
it is kept as active.
 In case the Client is idle and is not communicating with the AOS, there is still the background thread
on the Client that is checking every 60 seconds if within the last 60 seconds the Client has
communicated with the Server. If this was not the case the background thread is calling a "ping"
method on the Server to explicitly validate the Client session as active.
124 | P a g e
Example Outputs of Channels of AOS instance:
125 | P a g e
Example of creating Microsoft Dynamics AX AOS Sensor:

Create Microsoft Dynamics AX monitoring In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your AOS server
Create the sensor Dynamics AX AOS monitoring in PRTG interface:

7 Enter Sensor name: Dynamics AX AOS Performance
8 Enter tags: AOS_PERF
9 Choose axmonitor.exe from the Exe/Script drop down box

-i:stat -ax:01 -v:ax12
(Where –ax:nn is the instance of your AOS server)
126 | P a g e
Dynamics AX Client Performance Sensor

AX Client Performance Monitor Channels:
 AOD Cache Cleanups

 AOD Items Cached
 Form loads
 Form Preload Cache Flushes
 Form Preload Cache Items
 Form Preload Eligible Misses
 Form Preload Ineligible Misses
 Form Preloads
 Remote Calls
 Server Idle
 X++ Cache Cleanups
 X++ Items Cached
127 | P a g e
Example of creating Microsoft Dynamics AX Client Sensor:

Create the sensor Dynamics AX Client monitoring in PRTG interface:

(On a device pointed to your AOS server)
3 Enter Sensor name: Dynamics AX Client Performance
4 Enter tags: AOS_CLIENT

-i:client -v:ax12
128 | P a g e
Dynamics AX Portal Performance Sensor

The sensor offers the following channels:
 Sessions
 Sessions Allocated
 Sessions Disposed
 Session Alloc. Rate
 Session Fatal Exceptions
 Session NonFatal Exceptions
 Web Part Execution time
 X Buffer Instances
 X Class Instances
 X Container Instances
 X Record Instances
 X Session Exceptions
129 | P a g e
Example of creating Microsoft Dynamics AX Enterprise Portal Sensor:

Create the sensor Dynamics AX Portal monitoring in PRTG interface:

(On a device pointed to your AOS Portal Server)
3 Enter Sensor name: Dynamics AX Enterprise Portal Performance
4 Enter tags: AOS_PORTAL

-i:portal -v:ax12
130 | P a g e
ADVANCED MICROSOFT SQL SERVER V2 (AMSS) PLUGIN

In most companies Microsoft SQL Servers are considered as core technology where poor performance
affects severely to many other services. AMSS is a compilation of technologies to identify, monitor and
help mitigating the areas resulting in possible poor performance.
Monitoring Databases (Top 10 Most Reads and Writes)

Identify the most (top 10) Read and Write operation causing databases. Dispersing database activity across
multiple disk drives by request causes less pending IO.
Monitoring Databases (Top 10 Most Waits)

Top 10 databases suffering of Wait statuses.
Monitoring SQL Server Disk latency

High Disk latency can cause Disk saturation which results in overall server unresponsiveness. Saturation
occurs when latency increases and throughput stays the same. An example of disk saturation is shown in
the following figure(RED).
131 | P a g e
Monitoring SQL Server IO Bottlenecks

Determining which SQL activity causes the most bottlenecks with in the SQL server Pending IO should be
monitored closely. How do we know how many pending IO requests are there for database files
individually? The following figure shows the count of pending IO, the higher the column the more is the
risk total of disk saturation. In addition the Message identifies the database(s) causing the Pending IO.
132 | P a g e
There are permission requirements for this plugin operate:
1) Sql login must be a (normal) Windows user account
The minimum permissions that are required to see the corresponding results is:
VIEW ANY DEFINITION and VIEW SERVER STATE
Execute the following to grant the right to a domain account:
USE master
GO
GRANT VIEW ANY DEFINITION, VIEW SERVER STATE TO [domain\SqlMonUserAccount]
Command line (EXE/XML): -t:[%host] -u:[%windowsuser] -p:[%windowspassword] -

d:[%windowsdomain]
-i:[topwait] -db:[dpmdb] -to:[120]
Where
-t:[%host] = Is the Target/ SQL Host

-u:[%windowsuser] = User Account for the connection
-p:[%windowspassword] = Password for the connection
-d:[%windowsdomain] = Domain for the connection account
-i:[topwait] = Monitoring Index :

[topwait] for
[topread] for TOP 10 Total Reads Databases within period
[topwrite] for TOP 10 Total Writes Databases within period
[disklat] for Disk Latency (AvgLat, AvgRead and AvgWrite) of all Drives used for SQL activity
[PendIO] for Count of pending IO operations in Total. Pending databases names returned in Message part.
-db:[dpmdb] = Optional, Database name for the connection, (Master) used if not given
-to:[120]= Optional, Timeout for the connection, 30 sec if not given
133 | P a g e
134 | P a g e
LYNC 201X (OFFICE 2007/LIVE COMMUNICATIONS 2005) SERVER PLUGIN
Microsoft offers a solution to monitor LYNC 2010 and 2013 servers via implementing LYNC Monitoring
Server on a separate hardware but there is no official solution for still widely used older versions of
communications server family like OCS and LCS. However both of these older versions offer the same vital
monitoring capabilities as their younger brother.
General Information
This Plugin supports monitoring both single server and large server farms installations for service usage and
capacity management. The monitoring capabilities can be divided into different sub categories created to
support monitoring Frontend and Backend servers based on their respective roles.
 User load and usage counters

Number of users, Messages sent, Conferences, Participators
 Server Health related counters
 Web Conferencing MCU counters
 Peers/HTTPS Transport counters
 Database performance counters
135 | P a g e
User load and Usage Counters

Gives you an insight view of the usage of the Communications Servers. You can track down the type of
sessions and Conferences.
Graph shows the number of sessions and IM Messages sent in last 30 days
Graph shows the number of user sessions, connections and IM Messages sent in last 30 Days
136 | P a g e
LYNC/OCS/LCS Indexes for monitoring
TAG Cval Index Value Desc

pcs 10 User Connections Active Total number of
sessions
pcs 20 Messages Processed IM Messages
processed
User Load Counters

pcs 100 Number of AV Conferences
pcs 110 Number of AV Conference Users
pcs 120 Number of Conferences
pcs 130 Number of Conferences Connected Users
pcs 140 Incoming Transactions Processed/t Sigma parameter =
t0-t1 value
pcs 150 Incoming Messages/t sigma
pcs 160 Outgoing Messages/t sigma
pcs 170 Files Transferred
Server Health
Trigger 200 Global health 1=Normal Value
0=Disabled
2=Lightload
3=Heavyload
4=Overload
pcs 210 TCP disconnects because remote out of sync sigma

pcs 220 Relay allocation failures sigma
pcs 230 Number of packets dropped by Secure RTP/sec
pcs 240 Number of conferences with NORMAL health
pcs 250 Number of conferences with OVERLOADED health
pcs 260 Number of packets dropped in flow control/t sigma
pcs 270 Number of failed end to end connectivity checks/t sigma
msec 280 Average time spent in processing audio packets
pcs 290 Conference process rate
Trigger 300 Thread Pool Health State
trigger 310 MCU Health State
pcs 320 Local 503 Responce/s Service
pcs 330 Local 504 Responce/s Server Time-Out
Web Conferencing MCU

400 Thread Pool Load
410 Thread Pool Health State
420 MCU Health State
430 MCU Draining State
Peers/HTTPS Transport
pcs 500 Flow-controlled Connections dropped
pcs 510 Sends Outstanding
sec 520 Average Flow-Control Delay (in seconds)
pcs 530 Number of failed connection attempts / sec
pcs 540 Number of failed connection attempts
pcs 550 Number of outgoing requests that timed out
pcs 560 Number of outgoing requests that timed out / sec
pcs 570 Add Conference Requests
pcs 580 Add Conference requests succeeded
590 Local C3P success response
600 Local C3P pending responce
pcs 610 Factory Unreacable Failures
pcs 620 Factory Calls Timed-Out
pcs 630 Create Conference MCU Unreachable Failures
pcs 640 Create Conference Requests Timed-Out
Database
msec 700 Queue Latency
msec 710 Sproc Latency
137 | P a g e
Usage
You can easily create a full installation with template in the www.ptrgplugins.com templates section and
the template is also included in the installation package.
Templates are available for easy installation for the following versions in the download templates section:
 LYNC 2013veeam
 LYNC 2010
 OCS 2007
 LCS 2005
Command line:
%host %windowsuser %windowspassword %windowsdomain [Index] [ServerType]
Where [Index]:
Is the index from the table
and the [ServerType] states the target server version:
[LCS] for LCS server versions

[OCS] for Office Server versions
[LNC] for Lync 2010 Server version
138 | P a g e
BACKUPEXEC MONITORING PLUGIN

The Symantec Backup Exec Plugin is designed to help system administrators:
 Manage and monitor their backup systems in PRTG Network Monitor

 Enable automation and delegate backup execution and jobs success validation to PRTG
 Generate information of multiple Backup Exec environments (with different versions) in a
consolidated view
 Allow administrators to streamline their backup strategies by providing information of the backups
speed, volume and timings
There are multiple methods of achieving the above and we have taken the general approach to ensure the
proper functioning of the Backup Exec installation by alerting on the defects only rather than reporting on
successfully completed activity. There are better native tools available for investigating the success.
The Backup Exec Plugin generates alerts only on exceptions thus suggesting actions only when they are
necessary reducing administrative work load related to backup management.
Backup Exec Plugin offers many functions to fulfill these requirements by checking:
 That Backup Exec is Running

 For Active Jobs at point of time
 For “hanging jobs” (Jobs exceeding time expected)
 For Alerts and Events generated by Backup Exec Job Engine
 …..
 the amount of data being backup
Some Special concerns

Please note that Backup Exec plugin can be utilized as both EXE and EXEXML sensor type. Refer to
command line and create the sensor type accordingly. See using option –i:base instead to replace all
template based sensors
Running Backup Exec Plugin in a Probe computer with Backup Exec installed
In some cases you have installed the PRTG probe functionality on the same server as Backup Exec server is
running. In this scenario you just need to replace the target computer name with static LH in order to
instruct the plugin monitor the local host. This does not apply to SQL based queries.
SQL Connectivity topics of the Backup Exec Database

By default Backup Exec is installed with local SQL installation as an instance named
SERVERNAME\BKUPEXEC and this is supported via the plugin parameter –n:[instance name]. If you have
chosen to install the database to a different server and/or instance it is supported as well but you need to
regard this when setting the target of the sensor.
139 | P a g e
Other Plugins to be considered with Backup Exec Monitoring

In order to verify the proper SQL performance of your Backup Exec installation you may refer to “Advanced
Microsoft SQL Monitoring plugin”.
In addition there is an event based monitoring capability for you to trigger alerts on most common failures.
Events Monitoring supported by the Backup Exec Plugin:
140 | P a g e
The new Base sensor

The new ‘base’ sensor replaces all previous versions EXE based templates, simplifying the implementation
of the monitoring. The sensor contains the following information:
Backup Server operational (tickers):
 Server Running
 Server Active
Server Jobs information:
 Server Jobs
 Server Active Jobs
 Server Normal Jobs
 Server Differential Jobs
 Server Job Failed
Server Data information:
 Bytes Container
 Bytes Directory
 Bytes File
 Bytes Non Container
 Bytes Transferred
 Server Active VSNs
 Server Corrupted Object
 Server Shadow Copy Writers
 Server Skipped Object for Error
 Server Skipped Object In Use
141 | P a g e
Creating the Backup Exec Base sensor

In order to verify the proper Backup Exec operations and performance a “base” sensor can be used
In PRTG interface:

2 Enter values for device name and IP Address/DNS Name of your Backup Exec server
your own values
Create a new sensor in PRTG interface:

5 Choose EXE/Script Advanced type of sensor
6 Enter Sensor name: Backup Exec Basic Information
7 Enter tags: BE_BASE
8 Choose bemonitor.exe from the Exe/Script drop down box
–d:%windowsdomain –i:base –s:BE10
142 | P a g e
Advanced Backup Exec Jobs Monitoring in EXE/XML Mode via SQL Connectivity
Backup Exec plugin offers an extended way of monitoring backup jobs by Status, Volume and Age.
Monitoring Jobs by Backup Volume

In this mode the sensor lists last 10 backup jobs by Backup Size. In addition the sensor status field will
contain information of the latest job: Name and Age of the job and also the information if the latest job is
currently Active or Finished.
Command line (EXEXML-type):

-t:%host –u:%windowsuser –p:%windowspassword –d:%windowsdomain -i:top10size
–s:[ServerType] –db:[database] –ts:[time span]
the [ServerType] states the target server version:
•[BE2010] - Backupexec 2010, Backup exec 2012

•[BE10] - BackuExec 10, 11
•[BE9] - Backupexec 9
Command line example of Monitoring Backup Exec 2010 or 2012 with default database (bedb) for a
time span of 48 hrs (Target set to SQL-server of the database):
-t:%host -u:%windowsuser -p:%windowspassword -d:%windowsdomain -i:top10size -s:BE10

-db:bedb -ts:48
143 | P a g e
Monitoring Jobs by Backup Age

In this mode the sensor lists last 10 backup jobs by Backup Age. In addition the sensor status field will
contain information of the latest job: Name and Size of the job and also the information if the latest job is
currently Active or Finished.
Command line (EXEXML-type):

%host %windowsuser %windowspassword %windowsdomain [Index] [ServerType]
Where [Index]:
Is the index from the following BE Indexes table
and the [ServerType] states the target server version:
•[BE2010] - Backupexec 2010, Backup exec 2012

•[BE10] - BackuExec 10, 11
•[BE9] - Backupexec 9
144 | P a g e
Monitoring Job statuses

Sensor mode gives the complete list of Backup Exec Event Codes within the given time period. You can set
triggering based on the following table.
Above: Job Status Codes explanation in detail
145 | P a g e
Command line (EXEXML-type SQL-Mode):

-i:[Sensor Index] -s:[SType] -db:[DatabaseName] <–ts:TimeSpan_Optional>
<-n:NamedPipe_Optional>
Note: Options can be in any order.
Options explained:
-t:%host
Is the name or ip of the target hosting the database of the backup services.
This can be separate of Backup Server itself. By default SQL is installed with SQL Named Pipes and is usually
named as BKUPEXEC then use the –n:BKUPEXEC option.
Additionally remote connectivity to SQL instance has to be allowed.
-u: is the UserID

-p: Is the password
-d: Is the Windows Domain
-i:[Sensor Index]
Where the Index can be:

stats = For the Jobs Statuses
top10size = For the last 10 backup Job Sizes
top10time = For the last 10 Backup Job Ages
-db:[DatabaseName]
Name of the Backup Exec Database. Default BEDB is used if parameter omitted.
-ts:<TimeSpan>
is the time frame that is included in the queries in hours. By default 24 hrs is used if omitted as a parameter.
–s:[SType]
Defines the target Backup Server version where options are:
•[BE2010] – for Backupexec 2010 and 2012

•[BE10] – for BackuExec 10, 11
•[BE9] – for Backupexec 9 and below
EXAMPLES:
Backup Jobs by size since 96 hours on Backup Exec 2010 default server installation:
-t:%host -u:%windowsuser -p:%windowspassword -d:%windowsdomain -i:top10time -s:BE10 -
db:bedb -ts:96 –n:BKUEXEC
-t:%host -u:%windowsuser -p:%windowspassword -d:%windowsdomain -i:top10time -s:BE10 -

db:bedb -n:bkupexec -ts:96
All statuses in Last 96 Hours: ….. -i:stat –ts:96
146 | P a g e
Backup Exec Plugin Monitoring Reference Example

In this reference example we monitor the Backup Exec Services, Statuses and Jobs. This can be regarded as
the recommended set of sensors for ensuring a proper functionality of a Backup Exec installation.
NOTE: This example has an exclusion of basic windows server monitoring properties of PRTG like
services, memory, disk and processor. These you should setup according your PRTG documentation.
Installation Overview
In this example we monitor want to the following:
o Backup Server Base Sensor (Server Running and basic information)

o Backup Events (No triggering)
o Job status (During last 24 hrs.)
o Last 10 Jobs by size (since last 48 hrs.)
o Last 10 Jobs by Age (since last 48 hrs.)
o “Hanging Jobs” (=Jobs running over 12 hrs.)
The above sensors table results view:
147 | P a g e
Sensors and options installed in detail
MONITORING AREA Sensor Type/ Description Special/Optional Options

Method Parameters
STEP 3: EXEXML Ensuring that Backup
Backup Server WMI Exec executable is
Running and Base running. and
information monitoring jobs and
(With triggering) performance data.
STEP 4: EXEXML Monitoring and Trigger alerts on
Backup Events WMI triggering alerts on all channels of your
(No triggering) major events of choice. In this example
Backup Exec. we do not trigger
alerts.
STEP 5: EXEXML This shows static -ts:24 Use –ALL switch to see
Job status SQL information of all <Time span> Relates statuses for all Job
(During last 24 hrs.) statuses of backup to time frame we types.
jobs within the given want to monitor, in
time span. Any errors this case we want to
set the sensor to see the statuses since
warning state the last 24 hrs.
indicating the failed
job name in the sensor
info text.
STEP 6: EXE Indicates Job(s) -ts:48 Triggering an alert if
Jobs Failed in 24h SQL failures (as above) Same as “Job status” channel value is above
which have not been above. zero.
responded in BE
Console within the
time frame. Responses
in the console affect
the sensor values.
STEP 7: EXEXML This is very -ts:48 Use –ALL switch to see
Last 10 Jobs by size SQL informational If Same as “Job status” statuses for all Job
(since last 48 hrs.) checked periodically above. types.
and gives you a good
visual view on backup
your beckup jobs sizes
and how those are
evolving.
STEP 8: EXEXML Same as above but -ts:48 Use –ALL switch to see
Last 10 Jobs by Age SQL from jobs age point of Same as “Job status” statuses for all Job
(since last 48 hrs.) view. above. types.
STEP 9: EXEXML Alerting on Jobs that

“Hanging Jobs” SQL are performing slow or
(Jobs running over 12 have stopped. In this
hrs.) example we assume
that any job should be
finished within 12 hrs.
STEP ONE: Check the prerequisites

Check that you have the following installed on the Probe Machine:
1 Required .NET environment is installed.

2 Latest PRTGPlugins.msi setup file with plugins option only is installed.
3 A valid PRTG Plugins License file(s) existing in both EXE and EXEXML-directories.
148 | P a g e
4 Latest version of bemonitor.exe from sites downloads area exists in EXEXML-directory.
STEP TWO: Create a new device for your Backup Exec Monitoring
In PRTG interface:

13 Enter values for device name and IP Address/DNS Name of your Backup Exec server
your own values
STEP THREE: Create sensor for Backup Server Running and base information
If not created earlier…
Create the sensor in PRTG interface:

18 Enter Sensor name: Backup Exec Basic Information
19 Enter tags: BE_BASE
-d:%windowsdomain –i:base –s:BE10
149 | P a g e
STEP FOUR: Create sensor for Backup Events

Create the sensor in PRTG interface in device view:

3 Enter Sensor name: Backup Events Monitoring
4 Enter tag: BE_EVENT
-d:%windowsdomain -n:BKUPEXEC -i:EVENTS -s:BE10
Set Sensor triggering in PRTG (after one successful monitoring cycle->Channels available):
9 Edit the sensor and choose Channels Alerts of Your choice
150 | P a g e
STEP FIVE: Create sensor for Job status (During last 24 hrs.)

3 Enter Sensor name: Job Status in 24h
4 Enter tag: BE_JOBS
-d:%windowsdomain -i:stats -s:BE10 -ts:24 -n:BKUPEXEC
To see statuses of all job types use –ALL switch:

-d:%windowsdomain -i:stats -s:BE10 -ts:24 -n:BKUPEXEC –ALL
This option is available in version 1.2.5 onwards.
151 | P a g e
STEP SIX: Create sensor for Jobs Failed in 24h


2 Choose EXE/Script type of sensor
3 Enter Sensor name: Jobs Failed in 24h
4 Enter tag: BE_JOBS
d:%windowsdomain -n:BKUPEXEC -i:710 -s:BE10 -ts:24
STEP SEVEN: Create sensor for Last 10 Jobs by size (since last 48 hrs.)

3 Enter Sensor name: Last 10 Jobs by Size
4 Enter tag: BE_TOP10SIZE
d:%windowsdomain -n:BKUPEXEC -i:top10size -s:BE10 -ts:48
To see statuses of all job types use –ALL switch
152 | P a g e
STEP EIGHT: Create sensor for Last 10 Jobs by Age (since last 48 hrs.)

3 Enter Sensor name: Last 10 Jobs by Age
4 Enter tag: BE_TOP10TIME
-d:%windowsdomain -n:BKUPEXEC -i:top10time -s:BE10 -ts:48
To see statuses of all job types use –ALL switch
STEP NINE: Create sensor for “Hanging Jobs” (Jobs running over 12 hrs.)

3 Enter Sensor name: Hanging Jobs
4 Enter tag: BE_HANG
-d:%windowsdomain -n:BKUPEXEC -i:jobrun -s:BE10 -mt:12
153 | P a g e
STEP TEN: Monitor Backup Exec Core Services via native PRTG sensors
We suggest you to create a new device where the services are being monitored. The following
demonstrates a monitoring example of basic Backup Exec installation related Services set up via WMI
sensors of PRTG.
154 | P a g e
Some additional Backup Exec sensors recommended for monitoring

With these sensor values you get an informative view of all your jobs by size and including execution times.
Monitoring performance data enables you to avoid any interference any performance degrade of network,
software or equipment.
1 Create a new device targeted on your Backup Exec Server: Add device
2 Enter Device Name: Backup Exec Performance Data
3 For sensor management choose:
Automatic sensor creation using specific device template(s)
4 In the templates list choose:
PRTGPlugins Backup Exec 2010 Performance
155 | P a g e
How to monitor Multiple Backup Exec Servers in one single view

There is a built in function in PRTG to present data from multiple sensors in a single view called ‘Filter by
Tag’. It is most informative to see all your important Backup Exec Sensors in one single view.
You can select the sensors of your choice by the sensor tag entered in creation phase:
URL/sensors.htm?filter_tags=@tag(BE_RUNNING,BE_ERRORS,BE_JOBS,BE_EVEN
T,BE_TOP10SIZE,BE_TOP10TIME,BE_HANG)
156 | P a g e
HP HARDWARE INFORMATION PLUGIN V2

Supports monitoring of the HP/Compaq server hardware running on Windows operating system. The plugin
offers alerting on most common hardware failures, important environmental information and capability of
anticipating disk failures by reporting the different disk operating hours.
Full monitoring requires HP WBEM providers to be installed in operating system.
The following Information is being monitored by the plugin:
Sensor Channel Description of data

Average Temperature Average of Temperature of all
sensors available
Max Temperature Maximum temperature

reported by sensors.
Min Temperature Minimum temperature

reported by sensors
Fans Failing Number of failed fans
Fans Ok Number of operational fans
Power Consumption Power Consumption in Watts

reported by hardware.
157 | P a g e
Power Supplies Failing Number of power supplies

failing
Power Supplies Ok Number of power supplies

operational
All Logical Drives with status All Logical Drives are listed as
separate channels in the sensor
with their statuses listed.
Normal operational status is 2
Storage in Error Consolidated value of any
Logical Drive or Disk falling
outside normal operational
state.
Disks Count Total number of Disks attached
to the device including Spares.
Disks in Error State Count Number of Disks not in Default

State.
Disk Hours Minimum Number of hours the newest

disk has been online
Disk Hours Maximum Number of hours the oldest

disk has been online
158 | P a g e
Operational requirements
In order to enable all statuses in the sensor to be monitored the HP Insight WBEM providers package needs
to be installed. Please also note that the statuses reported by the sensors is dependent on the hardware
and WBEM capabilities.
Installing the correct WBEM providers on the target server please refer to:
http://h18004.www1.hp.com/products/servers/management/wbem/providerdownloads.html
You can verify that the Server hardware is reported correctly via WBEM in HP Insight Manager via the
local homepage.
159 | P a g e

3 Enter Sensor name: HP Hardware Monitoring Server Name
4 Enter tag: HP_HWMON
5 Choose hwmonitor.exe from the Exe/Script drop down box
-t:%host –u:%windowsuser –p:%windowspassword –

d:%windowsdomain –i:HP2
Set Sensor channels triggering in PRTG (after one successful monitoring cycle->Channels available)
Presenting the results

You can create a single device in PRTG to enable a consolidated view on your hardware statuses. If you
choose to enable the sensor under individual server devices you can still create a consolidated view on all
sensors by the sensor tag:
…../sensors.htm?filter_tags=@tag(HP_HWMON)
Example of “Single Device Monitoring” monitoring and a screen shot of single sensor output.
160 | P a g e
VEEAM BACKUP & REPLICATION SERVER PLUGIN

The plugins is Capable of Monitoring the following areas of Veeam Backup & Replication software.
 Backup Performance Monitoring

 Backup Jobs and Statuses
 Job Logs Views
 Statuses of Proxy Servers
 Statuses of Backup Repositories
 Oldest Backups by Age
 Hanging Jobs
Monitoring a Default Veeam Backup installation (v8 and v9)

As Veeam Backup Monitoring plugin utilizes the SQL Database information for monitoring there are some
considerations to take into account while configuring the plugin for PRTG. In general the most important
thing to know before configuration is the location and setup of the SQL Database for Veeam Backup.
Basic Setup in Veeam is a local SQL database running in instance of VEEAMSQL2012 and the default
database name is veeambackup. This results in parameters:
-n:VEEAMSQL2012 and –db:veeambackup that should be used in all sensor options:
Example for Backup Performance Monitoring parameters line in PRTG:
-t:%host -u:%windowsuser -p:%windowspassword -d:%windowsdomain -i:jobperf -n:VEEAMSQL2012

-db:veeambackup
Another important thing is the SQL Connectivity from a remote PRTG probe: By default the plugin uses
NT-authentication to make the connection and requires that the PRTG Probe can authenticate to the target
server directly. If this method the plugin can be instructed to use SQL authentication instead by omitting
the –d:%windowsdomain parameter. Naturally the SQL-authentication must be enabled on the SQL
installation for which there is a simple video on the front page of www.prtgplugins.com.
Example of using SQL-Authentication in PRTG:
-t:%host -u:%windowsuser -p:%windowspassword -i:jobperf -n:VEEAMSQL2012 -db:veeambackup
Using Exclusions in Jobs

For sensor options Jobperf and Minstat there is a possibility exclude maximum of three jobs names from
the monitoring. These jobs can be stated by using parameters –ex1:, –ex2: and –ex3: and the job’s
corresponding name. The names are Case sensitive.
161 | P a g e
Backup Performance Monitoring

3 Enter Sensor name: Veeam Backups Performance
4 Enter tag: VEEAMPERF
5 Choose veeambmon.exe from the Exe/Script drop down box

-d:%windowsdomain -i:jobperf -n:VEEAMSQL2012
If using default Veeam Backup installation the database name

can be omitted (veeambackup database name is used
automatically).
162 | P a g e
Job Statuses Monitoring

3 Enter Sensor name: Veeam Jobs Status
4 Enter tag: VEEAMSTAT

-d:%windowsdomain -i:minstat -n:VEEAMSQL2012

automatically).
163 | P a g e
Joblogs in Last X hrs

3 Enter Sensor name: Veeam Logs Status
4 Enter tag: VEEAMLOGS

-d:%windowsdomain -i:logs –ts:5 -n:VEEAMSQL2012

automatically).
-ts:5 instructs the sensor show statuses for the last 5

Hours
164 | P a g e
Proxy Status

3 Enter Sensor name: Veeam Proxy Status
4 Enter tag: VEEAMPROXY

-d:%windowsdomain -i:proxy -n:VEEAMSQL2012

can be omitted (veeambackup name used automatically).
165 | P a g e
Repositories Status

3 Enter Sensor name: Veeam Repositories Status
4 Enter tag: VEEAMREPO

-d:%windowsdomain -i:repo -n:VEEAMSQL2012

166 | P a g e
Last Backups Ages
167 | P a g e

3 Enter Sensor name: Veeam Last Backup Ages
4 Enter tag: VEEAMSINCE

-d:%windowsdomain -i:since -n:VEEAMSQL2012 –mt:24 [-verbose]

-mt:Hours is the limit for sensor warning level -> All Jobs
older than this are listed in the header information. The
default value is 24 hours.
Option –verbose instructs the sensor to list the actual
Veeam Job Names as channels (Optional).
168 | P a g e
Hanging Jobs
169 | P a g e

3 Enter Sensor name: Veeam Hanging Jobs
4 Enter tag: VEEAMHANGING

-d:%windowsdomain -i:jobrun -n:VEEAMSQL2012 –mt:24 [-
verbose]

-mt:Hours is the limit for sensor warning level -> All Jobs
running more than this are listed in the header information.
The default value is 24 hours.
Option –verbose instructs the sensor to list the actual
Veeam Job Names as channels (Optional).
170 | P a g e
ARCSERVE BACKUP MONITORING PLUGIN

The plugin monitors ArcServe backup individual jobs statuses and their execution times for identifying
Hanging Jobs and last backup job execution times.
Monitoring ArcServe Job Statuses

The following consolidated information is received from the sensor:
1. Total Active Jobs

2. Total Jobs
3. Total Jobs in Error
4. Total Jobs on Warning
Also a current status of each job is shown:
171 | P a g e
Creating an ArcServe Monitoring Sensor

The example uses Windows authentication for connecting to SQL. If the target and probe are not in the
same domain structure, please use SQL (Mixed) authentication instead and omit the –d: parameter.

3 Enter Sensor name: ArcServe Backup Monitoring
4 Enter tag: ARC_MON
5 Choose arcmonitor.exe from the Exe/Script drop down box
-t:%host\ARCSERVE_DB –u:%windowsuser –p:%windowspassword

-d:%windowsdomain -i:jobperf
If using default Arcserve Backup installation the database

name can be omitted (asdb name used automatically).
The addition \ARCSERVE_DB instructs the sensor to use the

default instance on the sql installation.
Using Mixed authentication:
-t:%host\ARCSERVE_DB –u:%windowsuser –p:%windowspassword

-i:jobperf
If the database name is different from the default use

additional parameter –db:MyName in either connection
options.
For enabling SQL/Mixed authentication on default installation, please see the following link:
http://new.prtgplugins.com/members/wmiconn/109-sqlinstances
172 | P a g e
ESX SERVER PLUGIN V2

PRTG by default offers ways to monitor ESX Server Host and Clients performance but proper managing of
ESX environment requires different approach. ESX Plugin has been designed to help ESX administrators to
maintain and monitor the environment.
Environment Status (VMSTAT)

Reports the following of VMWare environment:
 Total VMs
 Number of VMs with CD Attached
(Important in Clusters)
 Powered On VMs
 Powered Off VMs
 VMs Status OK
 VMs Status Failed
 VMs Heartbeat Ok
 VMs Heartbeat Failed
 Data Committed Bytes
 Data Uncommitted Bytes
 Data Committed rate percent
173 | P a g e

3 Enter Sensor name: VMWare Status Monitoring
4 Enter tag: ESX_STAT
5 Choose esxmonitor.exe from the Exe/Script drop down box
%host %windowsuser %windowspassword vmstat
174 | P a g e
VMTOOLS

3 Enter Sensor name: VMWare Tools
4 Enter tag: ESX_TOOLS
%host %windowsuser %windowspassword vmtools
175 | P a g e
VMTOOLS_VERSIONS

3 Enter Sensor name: VMWare Tools Versions
4 Enter tag: ESX_TOOLVER
%host %windowsuser %windowspassword vmtoolsver
176 | P a g e
VMDATASTORE_INFO

3 Enter Sensor name: VMWare Datastore
4 Enter tag: ESX_DS
%host %windowsuser %windowspassword hostinfo_ds
177 | P a g e
VMSTAT_VMOS

3 Enter Sensor name: File Services Monitoring
4 Enter tag: ESX_STAT
%host %windowsuser %windowspassword vmos
178 | P a g e
SYSTEM CENTER CONFIGURATION MANAGER / WSUS PLUGIN 1.0
A view of WSUS Contacted Clients:
Command line options:
Index 100: # of clients where WSUS updates succeeded
WSUSMonitor.exe %host %windowsuser %windowspassword %windowsdomain WSUS_DB Index
TargetComp is the server holding the SQL database of the WSUS.
WSUS_DB is the name of the database.
Parameters apply to Indexes 100, 200, 300 as well
Index 500: # of items in ANY SCCM collection count.
WSUSMonitor.exe %host %windowsuser %windowspassword NTLMDOMAIN:%windowsdomain

SCCM_DB_NAME 500 CollID
TargetComp is the server holding the SQL database of the SCCM.
SCCM_DB_NAME is the SCCM Database name.
CollID is the SCCM collection Internal Name.
Index 570:# of clients with Heartbeat between x and y Days.
The following gives you number of clients with heartbeat between 14 and 30 days e.g. suspected clients.
You can use your own preferences as you like.

SCCM_DB_NAME 570 14 30
14 is the lower date limit and 30 upper
UPDATED:
Indexes above 600:

SCCM_DB_NAME 570 14 30
179 | P a g e
For the moment the support is ONLY for SINGLE site reporting.
Monitoring Package Distributions
180 | P a g e
TAG Cval Index Value Desc

# of clients where WSUS updates
WSUS_SUC pcs 100 succeeded
# of clients where WSUS updates
WSUS_FLD pcs 200 failed
# of clients where WSUS updates have

WSUS_UKN pcs 300 other status than succeeded or failed
WSUS_ALL pcs 400 Total WSUS client count
Any SCCM collection count. Collection
SCCM_GEN pcs 500 stated as 7th parameter.
# of clients with HeartBeat within x
SYS_ALL pcs 550 Days. By default 30 days if not stated.
# of clients with HeartBeat OVER x
SYS_UKN pcs 560 Days. By default 30 days if not stated.
# of clients with HeartBeat between x
SYS_SUS pcs 570 and y Days.
"Patch management level": # of SCCM

Agent discoveries within x days/#
percent 600 clients connected to WSUS = x.x %
SCCM Patch Management

pcs 610 # of patches requested
pcs 620 # of patches installed
% 630 Patching Level
SCCM Installed base Health: Active and Obselete Clients

pcs 700 Clients Total Count
pcs 710 Clients Active Count
pcs 720 Clients Inactive Count
pcs 730 Clients Obsolete Count
% 740 Clients Inactive percent
% 750 Clients obsolete percent
SCCM Client Scanning Status (within last 24 hrs)

pcs 800 ClientScan Total Count Within last 24 hrs
pcs 810 ClientScan Successful count see above
% 820 ClientScan Successful percent see above
pcs 830 ClientScan Heartbeat count see above
% 840 ClientScan Heartbeat percent see above
pcs 850 MP Comm Successful count see above
pcs 860 MP Comm Failed count see above
pcs 870 MP Comms Total count see above
% 880 MP Comms Successful Percent see above
SCCM Hardware and Software Scanning (within last 5 days)

pcs 900 Active Clients Within 5 days
Number of clients
successfully reported
181 | P a g e
HW Scanning results
pcs 910 HW Scanning Success within 5 days
Number of clients
successfully reported
MICROSOFT CLUSTER MONITORING PLUGIN

Adds support for monitoring Microsoft Failover Clusters on 2008R2 Platforms.
Enables Complete visibility to Cluster HA status:
 Cluster nodes Up or Down

 Cluster Network Status
 Cluster Resources Status
 Cluster Disks Usage per Disk with Custom alert level
 Identifies and Logs to PRTG switching of nodes
Alerting can be consolidated based on any error or any individual HA component.
Sensor supports Cluster OS versions of 2008 R2 and above.
Sensor Channel Statuses for Resources (“2RS-“)

Value Status Meaning
-1 State Unknown The operation was not successful.

0 Inherited TBD
1 Initializing The resource is performing initialization.
2 Online The resource is operational and functioning normally.
3 Offline The resource is not operational. This value will be returned if the
resource reported a state of ClusterResourceOffline (3) or
ClusterResourceCannotComeOnlineOnThisNode (127).
4 Failed The resource has failed. This value will be returned if the resource
reported a state of ClusterResourceFailed (4) or
ClusterResourceCannotComeOnlineOnAnyNode (126).
128 Pending The resource is coming online or going offline.
129 Online Pending The resource is coming online.
130 Offline Pending The resource is going offline.
182 | P a g e

3 Enter tag: CLUS_MON
4 Choose clusmonitor.exe from the Exe/Script drop down box

d:%windowsdomain –i:stat –ul:80
Where
–ul:80 is to alert on disks usage over 80%
Please note that this sensor uses Custom Lookups which need to be installed on the main PRTG Server
and if needed a ‘Load Lookups’ needs to be applied in PRTG System Administration.
Monitoring Options for very Large Clusters to overcome PRTG Limitations

In larger Cluster environments the total channels reported may be over 50 pcs in case the PRTG interface
may not show all information.
In these cases you can divide the sensor’s channels to groups by the following areas:
1. Nodes (NET)
2. Network Interfaces (NODE)
3. Resources (RES)
4. Disks (DISK)
(Add the parameter: –o:node,disk,net,res)
Or any combination of the above, like:
-o:res,node
Displays only the Resource and Node statuses of the sensor.
183 | P a g e
Special option for Passive only Clusters

The default logic of the sensor expects at least one active partner and normally shows a sensor warning if
no active if found. To overcome this functionality you can use an extra option –noact on the parameters
section to show the sensor as Ok in these cases.
184 | P a g e
MICROSOFT FILE SERVICES MONITORING PLUGIN
Statuses and Volumes monitored

Logons
Number of all server logons
Sessions
Number of sessions currently active in the server. Indicates current server activity
Files Open
Number of files currently opened in the server. Indicates current server activity.
Dir Searches
Number of searches for files currently active in the server. Indicates current server activity.
Failures and Errors monitored

Pool Paged Failures
Number of times allocations from paged pool have failed. Indicates that the computer's physical memory or
paging file are too small.
Non Paged Failures

Number of times allocations from non-paged pool have failed. Indicates that the computer's physical
memory is too small.
Sessions Errored
Number of sessions that have been closed due to unexpected error conditions or sessions that have
reached the autodisconnect time out and have been disconnected normally.
185 | P a g e
Sessions Forced Out

Number of sessions that have been forced to log off. This value can indicate how many sessions were
forced to log off due to logon time constraints.
Sessions Logged Out

Number of sessions that have terminated normally.
Sessions Timed Out

Number of sessions that have been closed because the idle time exceeded the AutoDisconnect parameter
for the server. This property shows whether the AutoDisconnect setting helps to conserve resources.
Work Items Shortages

Number of times STATUS_DATA_NOT_ACCEPTED was returned at receive indication time. This occurs when
no work item is available or can be allocated to service the incoming request. Indicates whether the
InitWorkItems or MaxWorkItems registry values might require to be adjusted.
Requests Rejected
Number of times the server has rejected blocking packets (SMBs) due to insufficient count of free work
items. Indicates that the MaxWorkItems or MinFreeWorkItems registry values may require adjustment.
Failures and Errors of Security related monitoring

Errors Logon
Number of failed logon attempts to a server. A large number can indicate that password guessing programs
are being run to break the security on the server.
Errors Access
Number of times accesses to files opened successfully were denied. A high number can indicate attempts
to access files without proper authorization.
Errors Perm
Number of times open requests on behalf of clients have failed with the STATUS_ACCESS_DENIED error. A
high number can indicate attempts to randomly locate unprotected files.
Errors System
Number of times an internal server error was detected. Unexpected errors usually indicate a problem with
the server.
186 | P a g e

4 Enter tag: FS_MON
5 Choose smbmonitor.exe from the Exe/Script drop down box

d:%windowsdomain –i:stats
187 | P a g e
PLUGIN TYPES AND EXECUTABLES NAMES LIST
Placed in PRTG to
Plugin Name Executable Name EXE EXEXML
ACTIVE DIRECTORY PLUGIN ad2008monitor.exe (X) X
AMAZON EC2 VOLUME PERFORMANCE amamonitor.exe X
DYNAMICS AX/AOS COMMUNICATIONS axmonitor.exe (X) X
NETAPP ONTAP7 SERVER V2 ontapmon.exe X
SHAREPOINT/MOSS SERVER V2 PLUGIN mossmonitor.exe X
CITRIX LICENSING AND REMOTE DESKTOP PLUGIN V2 rdpmonitor.exe X
CITRIX/XENAPP APPLICATION SIMULATION icamonitor.exe X
NETSCALER VPX MONITORING vpxmonitor.exe X
REMOTE PING V2 PLUGIN rempingv2.exe X
IIS/BITS SERVER V2 PLUGIN iismonitor.exe X
ADVANCED MICROSOFT SQL SERVER V2 (AMSS) PLUGIN sqlmonitor.exe X
LYNC 2010 SERVER PLUGIN ocsmonitor.exe (X) X
BACKUPEXEC MONITORING PLUGIN bemonitor.exe (X) X
HP HARDWARE INFORMATION PLUGIN V2 hwmonitor.exe X
VEEAM BACKUP & REPLICATION SERVER PLUGIN V2 veembmon.exe X
ESX SERVER PLUGIN V2 esxmonitor.exe X
WSUS/SCCMPLUGIN wsusmonitor.exe (X) X
MS CLUSTER MONITORING clusmonitor.exe X
SYMANTEC ENTERPRISE VAULT MONITOR sevmonitor.exe X
MICROSOFT WINDOWS SERVER SMB MONITOR smbmonitor.exe X
(X) Only in rare downwards support cases, not new use cases.
188 | P a g e
KNOWN GENERIC LIMITATIONS AND BUGS

Decimal Separator
EXAMPLES
CASE ONE: SharePoint 2010 Foundation Server on Ontap iSCSI Volume Based database
Service Activity Monitoring
Internet Information Server (IISMonitor.exe)

%host %windowsuser %windowspassword NTLMDOMAIN:%windowsdomain 10 IIS8
Sharepoint Content Usage (MOSSMonitor.exe)

%host\sharepoint %windowsuser %windowspassword %windowsdomain WSS_Content 100 SP2010
Sharepoint_Auditing (MOSSMonitor.exe)
%host\sharepoint %windowsuser %windowspassword %windowsdomain WSS_Content audit SP2010
Sharepoint_SecurityAudit (MOSSMonitor.exe)
%host\sharepoint %windowsuser %windowspassword %windowsdomain WSS_Content secaudit SP2010
Front End Monitoring
Back End Monitoring
Servers Monitoring
189 | P a g e

PRTG Plugins Admin Guide 1.4.506

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PRTG Plugins Admin Guide 1.4.506

Caricato da

Copyright:

Formati disponibili

-i[

PRTG PLUGINS ADMIN GUIDE

PRTG Plugins Version: 1.4.506

Predefined Performance Views ................................................................................................................... 36

SharePoint Content Sensor Command line ............................................................................................. 56

CITRIX/XENAPP APPLICATION SIMULATION AND MONITORING ................................................................ 84

RD Connection Broker Monitoring ........................................................................................................ 110

Hanging Jobs .............................................................................................................................................. 169

Errors Access.......................................................................................................................................... 186

PRTG PLUGINS ADMIN GUIDE

PRTG PLUGINS MONITORING SUPPORTED ENVIRONMENTS

Picture 1: Schematics of different PRTG Installation options

List of Plugins that support monitoring in heterogeneous environments

List of Plugins that require monitoring in homogeneous environments

What needs to be installed where?

PRTG Main server

PRTG Remote Probes

 .NET 3.5 environment

After the PRTG Plugins Setup you must install:

 Copy your license key(s) to both EXE and EXEXML directories

PRTG PLUGINS INSTALLATION ENVIRONMENT REQUIREMENTS

PRTG PLUGINS INSTALLATION PROCEDURE

ABOVE: Choose to install the Plugins only if installing to a probe device

ABOVE: Choose templates only if installing these to a main PRTG server

PRTG PLUGINS CONFIGURATION PROCEDURE

Why are the templates important?

How plugins authenticate to services

ALWAYS AVOID ‘HARDCODING’ THE CREDENTIALS TO SENSOR PARAMETERS!

Some special configurations considerations

DISK FRAGMENTATION MONITORING

Create Disk Fragmentation monitoring In PRTG interface:

1 Create a new device

Create the sensor for Disk Fragmentation Monitoring in PRTG interface:

1 Create a new sensor by Add Sensor

ACTIVE DIRECTORY PLUGIN (STANDARD AND ADVANCED EXE MODE)

Active directory plugin consists of three main areas:

 [10] Active Directory Key performance data

Key Performance data

Channel data explained:

 Address book Client Sessions

 DRA Outbound Bytes per Second

Administrative content data

 LDAP Disabled Accounts

Activity and Security related data

Table of respective Event codes for Active Directory Servers

Creating a user account 624 4720

Usage and parameters

%host %windowsuser %windowspassword %windowsdomain [Index] [AD/Server Type]

Possible values are:

Getting Performance Data of a 2008 level Domain Controller.

Active Directory Group Members Monitoring

Create content monitoring In PRTG interface:

1 Create a new device

Create the sensor for Content Monitoring in PRTG interface:

5 Create a new sensor by Add Sensor

where subgroup1 is the name of the group to monitor.

Scanning Interval and Performance [Timeout]

NETAPP ONTAP7 SERVER V2 PLUGIN

Hardware and environment Monitoring

NetApp Device Basic Hardware Status: HWMINISTAT

%host %windowsuser %windowspassword HWMINISTAT

NetApp Device Hardware Status: HWSTAT1