Configuring Windows Systems for Monitoring with SNMP

Download this manual as a PDF file

Use the following menu options to navigate the SL1 user interface:

  • To view a pop-out list of menu options, click the menu icon ().
  • To view a page containing all the menu options, click the Advanced menu icon ().

The following sections describe how to configure Windows Server 2016, Windows Server 2012, and Windows Server 2008 for monitoring by SL1 using SNMP:

Configuring SNMP for Windows Server 2016 and Windows Server 2012

To configure SNMP on a Windows 2016 Server or a Windows 2012 Server, you must:

  1. Configure "ping" responses.
  2. Install the SNMP service.
  3. Configure the SNMP service.
  4. Configure the firewall to allow SNMP requests.
  5. Configure Device Classes. (Windows Server 2016 only)

Configuring Ping Responses

For SL1 to discover a device, including SNMP-enabled devices, the device must meet one of the following requirements:

  • The device must respond to an ICMP "Ping" request.
  • One of the ports selected in the Detection Method & Port field for the discovery session must be open on the device. If the Default Method option for the Detection Method & Port field is selected, SL1 scans TCP ports 21, 22, 23, 25, and 80.

The default configuration for a Windows Server does not allow ICMP "Ping" requests and does not allow connections to TCP ports 21, 22, 23, 25, or 80. Therefore, to discover a Windows Server in SL1, you must perform one of the following tasks:

  • Reconfigure the firewall on the Windows Server to allow ICMP "Ping" requests. This section describes how to perform this task.
  • Reconfigure the firewall on the Windows Server to allow connections to port 21, 22, 23, 25, or 80. If you have already configured your Windows Server to accept SSH, FTP, Telnet, SMTP, or HTTP connections, this task might have been completed already. You should perform this task only if you were already planning to allow SSH, FTP, Telnet, SMTP, or HTTP connections to your Windows Server.
  • When you create the discovery session that will discover the Windows Server, select at least one port in the Detection Method & Port field that is open on the Windows Server. For example, if your Windows Server is configured as an MSSQL Server, you could select port 1433 (the default port for MSSQL Server) in the Detection Method & Port field.

To reconfigure the firewall on a Windows Server to allow ICMP "Ping" requests, perform the following steps:

  • In the Start menu search bar, enter "firewall" to open a Windows Firewall with Advanced Security window.

  • In the left pane, select Inbound Rules.
  • If you want SL1 to discover your Windows Server using an IPv4 address, locate the File and Printer Sharing (Echo Request - ICMPv4-In) rule.
  • If you want SL1 to discover your Windows Server using an IPv6 address, locate the File and Printer Sharing (Echo Request - ICMPv6-In) rule.

  • Right click on the rule that you located, then select Enable Rule:

Installing the SNMP Service

To install the SNMP service on a Windows 2012 Server or Windows 2016 Server, perform the following steps:

  1. Open the Server Manager utility.
  2. In the upper-right of the window, select Manage > Add Roles and Features. The Add Roles and Features window is displayed.

  1. If the server does not skip the Before you begin page, click the Next > button to manually skip it. The Select installation type page is displayed:

  1. Click the Next > button to continue with Role-based or feature-based installation. The Select destination server page is displayed:

  1. Ensure the Windows 2012 server or Windows 2016 Server is selected and then click the Next > button. The Select server roles page is displayed.
  2. Click the Next > button without selecting any additional roles. The Select features page is displayed:

  1. Select the SNMP Service checkbox. The following confirmation window is displayed:

  1. Click the Add Features button.
  2. In the Select features page, expand SNMP Service and select the SNMP WMI Provider checkbox.

  1. Click the Next > button. The Confirm installation selections page is displayed:

  1. Click the Install button.
  2. After the installation is complete, click the Close button.

Configuring the SNMP Service

To configure the SNMP service on a Windows 2012 Server or Windows 2016 Server, perform the following steps:

If you recently installed the SNMP service, you must wait for the Server Manager window to refresh to allow the SNMP service snap-in to be added. You can manually refresh the Server Manager window by closing the Server Manager and then re-opening the Server Manager.

  1. In the upper-right of the Server Manager window, select Tools > Services. The Services window is displayed.

  1. In the Services window, right-click on SNMP Service, and then select Properties. The SNMP Service Properties window appears:

  1. In the Startup type: field, select Automatic.

  1. Select the Security tab. The security settings are displayed:

  1. In the Accepted community names panel, click the Add... button. The SNMP Service Configuration pop-up window is displayed:

  1. Enter a value in the following fields:
  • Community rights. Select one of the following options from the drop-down list:
  • READ ONLY. Select this option to allow SL1 to request information from this Windows 2012 Server or Windows 2016 Server using this SNMP community string. This option does not allow SL1 to perform write operations on this Windows 2012 Server or Windows 2016 Server using this SNMP community string.
  • READ WRITE. Select this option to allow SL1 to request information from this Windows 2012 Server or Windows 2016 Server and to perform write operations on this Windows 2012 Server or a Windows 2016 Serve using this SNMP community string.

  • Community name. Enter the SNMP community string that SL1 will use when making SNMP requests to this Windows 2012 Server or Windows 2016 Server. When you create a credential for this Windows 2012 Server or Windows 2016 Server in SL1, you will enter this community string in one the following fields in the Credential Editor modal page:
  • SNMP Community (Read-Only). Enter the SNMP community string in this field if you selected READ ONLY in the Community rights drop-down list.
  • SNMP Community (Read/Write). Enter the SNMP community string in this field if you selected READ WRITE in the Community rights drop-down list.

  1. Click the Add button to add the community string to the list of community strings this Windows 2012 Server or Windows 2016 Server accepts.

  1. In the Accept SNMP packets from these hosts panel, click the Add... button. The SNMP Service Configuration pop-up window is displayed:

  1. In the Host name, IP or IPX address field, enter the IP address of the All-In-One Appliance or Data Collector that will monitor this server.
  2. Click the Add button to add the appliance to the list of authorized devices.
  3. If you are using SL1 with a distributed architecture, repeat steps 8–10 for each Data Collector in the collector group that will monitor this server.
  4. Click the Apply button to apply all changes.

Configuring the Firewall to Allow SNMP Requests

To configure the Windows Firewall to allow SNMP requests on a Windows 2012 server or Windows 2016 Server, perform the following steps:

  • In the Start menu search bar, enter "firewall" to open a Windows Firewall with Advanced Security window.
  • In the left pane, click Inbound Rules.
  • Locate the two SNMP Service (UDP In) rules.

  • If one or both of the rules is not enabled, right-click on the rule and then select Enable Rule:

Configuring Device Classes for Windows Server 2016 and Windows 10

There is a known problem with the Microsoft OID that contains the version number for the operation system. This problem prevents SL1 from using SNMP to automatically align device classes to Windows 10 devices and Microsoft Server 2016 devices.

Because Microsoft has deprecated support of SNMP on Microsoft Server 2016 and Windows 10, users who want to use SNMP to monitor Windows 10 and Microsoft Server 2016 should use one of these workarounds:

  • After discovering a Microsoft Server 2016 or Windows 10 device, manually align the device class and disable nightly auto-discovery
  • Edit the registry key

Both workarounds are described in the following sections.

Manually Align the Device Class

After discovering Microsoft Server 2016 devices and Windows 10 devices, you can manually align a device class with the discovered devices. To preserve your manual changes, you must disable nightly auto-discovery for those devices. You can manually align the discovered devices with one of these device classes:

  • Windows Server 2016
  • Windows Server 2016 Domain Controller
  • Windows 10 Workstation

For details on manually assigning a device class to a device, follow the steps in the section on Manually Changing the Device Class for a Device in the Device Classes and Device Categories section. For details on disabling nightly auto-discovery for a device, see the section on Maintaining the New Device Class During Auto-Discovery in the Device Classes and Device Categories section.

Edit the Registry Key

You can log in to the device that you want to monitor and manually edit the Windows Registry Key "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion". You can define the value CurrentVersion as either "2016" or "10.0". To do this:

  1. Click the Start menu and choose Run.
  2. In the Run dialog box, type regedit and then click OK.
  3. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion
  4. In the right pane, double click on the Default key.
  5. Enter the appropriate value:
  • For Microsoft Server 2016, change the Value to 2016
  • For Windows 10, change the Value to 10.0

Configuring SNMP for Windows Server 2008

To configure SNMP on a Windows 2008 Server, you must:

  1. Configure "ping" responses.
  2. Install the SNMP service.
  3. Configure the SNMP service.
  4. Configure the firewall to allow SNMP requests.

Configuring Ping Responses

For SL1 to discover a device, including SNMP-enabled devices, the device must meet one of the following requirements:

  • The device must respond to an ICMP "Ping" request.
  • One of the ports selected in the Detection Method & Port field for the discovery session must be open on the device. If the Default Method option for the Detection Method & Port field is selected, SL1 scans TCP ports 21, 22, 23, 25, and 80.

The default configuration for a Windows Server does not allow ICMP "Ping" requests and does not allow connections to TCP ports 21, 22, 23, 25, or 80. Therefore, to discover a Windows Server in SL1, you must perform one of the following tasks:

  • Reconfigure the firewall on the Windows Server to allow ICMP "Ping" requests. This section describes how to perform this task.
  • Reconfigure the firewall on the Windows Server to allow connections to port 21, 22, 23, 25, or 80. If you have already configured your Windows Server to accept SSH, FTP, Telnet, SMTP, or HTTP connections, this task might have been completed already. You should perform this task only if you were already planning to allow SSH, FTP, Telnet, SMTP, or HTTP connections to your Windows Server.
  • When you create the discovery session that will discover the Windows Server, select at least one port in the Detection Method & Port field that is open on the Windows Server. For example, if your Windows Server is configured as an MSSQL Server, you could select port 1433 (the default port for MSSQL Server) in the Detection Method & Port field.

To reconfigure the firewall on a Windows Server to allow ICMP "Ping" requests, perform the following steps:

  • In the Start menu search bar, enter "firewall" to open a Windows Firewall with Advanced Security window.

  • In the left pane, select Inbound Rules.
  • If you want SL1 to discover your Windows Server using an IPv4 address, locate the File and Printer Sharing (Echo Request - ICMPv4-In) rule.
  • If you want SL1 to discover your Windows Server using an IPv6 address, locate the File and Printer Sharing (Echo Request - ICMPv6-In) rule.

  • Right click on the rule that you located, then select Enable Rule:

Installing the SNMP Service

To install the SNMP service on a Windows 2008 Server, perform the following steps:

  1. Open the Server Manager utility.

  1. In the left pane of the Server Manager window, select Features. The Features Summary is displayed:

  1. If the Features Summary displays "SNMP Service" and "SNMP WMI Provider" in the list of installed services (as shown above), you can skip to the section on configuring the SNMP service. If "SNMP Service" and "SNMP WMI Provider" are not included in the list of installed services, select Add Features:

  1. In the Select Features window, select SNMP Services:

  1. Click the Next > button. The Confirm Installed Selections window is displayed with "SNMP Service" and "SNMP WMI Provider" in the list of features that will be installed:

  1. Click the Install button. After the installation is completed, the Installation Results window will be displayed:

  1. Click the Close button.

Configuring the SNMP Service

To configure the SNMP service on a Windows 2008 Server, perform the following steps:

If you recently installed the SNMP service, you must wait for the Server Manager window to refresh before it will display the SNMP service snap-in. You can manually refresh the Server Manager window by closing the Server Manager and then re-opening the Server Manager.

  1. In the left pane of the Server Manager window, expand the Configuration section, and then select Services.

  1. In the list of services, right-click on SNMP Service, and then select Properties. The SNMP Service Properties window appears:

  1. In the Startup type: field, select Automatic.

  1. Select the Security tab. The security settings are displayed:

  1. In the Accepted community names panel, click the Add... button. The SNMP Service Configuration pop-up window is displayed:

  1. Enter a value in the following fields:
  • Community rights. Select one of the following options from the drop-down list:
  • READ ONLY. Select this option to allow SL1 to request information from this Windows 2008 Server using this SNMP community string. This option does not allow SL1 to perform write operations on this Windows 2008 Server using this SNMP community string.
  • READ WRITE. Select this option to allow SL1 to request information from this Windows 2008 server and to perform write operations on this Windows 2008 Server using this SNMP community string.

  • Community name. Enter the SNMP community string that SL1 will use to make SNMP requests to this Windows 2008 Server. When you create a credential for this Windows 2008 Server in SL1, you will enter this community string in one the following fields in the Credential Editor modal page:
  • SNMP Community (Read-Only). Enter the SNMP community string in this field if you selected READ ONLY in the Community rights drop-down list.
  • SNMP Community (Read/Write). Enter the SNMP community string in this field if you selected READ WRITE in the Community rights drop-down list.

  1. Click the Add button to add the community string to list of community strings this Windows 2008 Server accepts.

  1. In the Accept SNMP packets from these hosts panel, click the Add... button. The SNMP Service Configuration pop-up window is displayed:

  1. In the Host name, IP or IPX address field, enter the IP address of the All-In-One Appliance or Data Collector that will monitor this server.
  2. Click the Add button to add the appliance to the list of authorized devices.
  3. If you are using SL1 with a distributed architecture, repeat steps 8–10 for each Data Collector in the collector group that will monitor this server.
  4. Click the Apply button to apply all changes.

Configuring the Firewall to Allow SNMP Requests

To configure the Windows Firewall to allow SNMP requests on a Windows 2008 server, perform the following steps:

  1. In the Start menu search bar, enter "firewall" to open a Windows Firewall with Advanced Security window.

  1. In the left pane, click Inbound Rules.
  2. Locate the two SNMP Service (UDP In) rules.

  1. If one or both of the rules is not enabled, right-click on the rule and then select Enable Rule: