PATROL KM for Microsoft Windows Servers supports monitoring of remote hosts using the Windows Remote Management (WinRM) functionality. The same set of parameters are used to collect information for the local host as well as the remote host.
For more information about the architecture, see
Collection architecture for remote monitoring
Configuring PATROL KM for Windows for remote monitoring
To configure PATROL KM for Windows for remote monitoring, load the NT_REMOTE.kml file. For loading the .kml file, see Loading the PATROL for Microsoft Windows Servers KMs.
Application classes to configure remote monitoring
PATROL KM for Windows uses the following application classes to configure remote monitoring:
- NT_REMOTE_CONTAINER is a container KM and hosts instances of all remote hosts. This container application class provides all the menu commands and tasks required to configure remote hosts for monitoring. The NT_REMOTE_CONTAINER application class is represented by Remote Monitoring in the PATROL console.
- NT_REMOTE_HOST contains application instances for each remote host. Each remote host contains the NT_OS container. The NT_REMOTE_HOST application class is represented by Host Name in the PATROL console.
For more information about the supported application classes for remote monitoring, see Supported application classes for remote monitoring.
For information about the object hierarchy, see Object hierarchy for remote monitoring.
Parameters for remote monitoring
The following table lists the parameters that are used to discover application classes for remote monitoring.
| Collector | Consumer application |
|---|---|
RMOSDiscovery | NT_OS |
For more information about monitoring remote hosts, authentication, and the configuration tasks, see:
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks