Skip to main content
Probe Installation

Learn how to install and use the Naverisk Probe to acquire and display information on SNMP and WMI devices.

Updated over 7 months ago

Introduction

The Naverisk Probe is used to acquire and display information for SNMP and WMI Devices allowing you to monitor your client’s Printers, Routers, Switches, VMWare and other SNMP enabled Devices quickly and easily. Naverisk also offers the ability to scan for WMI Devices across a subnet allowing you to populate a list, and run a script against this list to install the Naverisk Agent onto these Devices. This Guide will provide the steps to installing the Naverisk Probe.

1.0 Prerequisites

To ensure that the Naverisk Probe can discover Devices correctly, upload the following Script Pack to your Naverisk Instance and run this script against the Device that you will install the Naverisk Probe on;

This Script Pack is intended to install a Visual C++ redistributable required for the functionality of the Probe / SNMP package.

2.0 Installing the Naverisk Probe

The Naverisk Probe can be installed on any Microsoft Windows Device on the Network which the SNMP Devices such as VMWare can connect to. The Host Device (Probe) should always be on. When it is offline you will not get any Alerts raised or Tickets created for you SNMP Devices.

To install the Probe module, you will need to choose a Host Device to have the Probe package installed on. Please note you must install a probe on a device at each client location for this to work correctly.

  1. In the Devices tab, select the Host Device that you will install the Probe package on, under the client you wish to monitor.

  2. From the Device Tasks drop-down select Manage Packages:

3. Under the Available Packages drop-down, select the Probe and click install:

4. Once the Package is installed you will receive a new tab called Probe;

For more information on how to discover and deploy WMI Devices, and to get more information on SNMP Device Management please got to Help in your Naverisk console.

Did this answer your question?