Configuring the Nodinite Windows Server Monitoring Agent

Unlock the full power of Nodinite by configuring the Windows Server Monitoring Agent for tailored, real-time monitoring. This guide walks you through remote configuration, group management, and advanced settings to ensure your Windows Server landscape is always under control using the Nodinite Web Client.

• ✅ Centralized remote configuration for all monitored servers
• ✅ Flexible grouping and threshold management for business needs
• ✅ Fine-tune monitoring with advanced tabs and settings

Understanding Remote Configuration Architecture

The Nodinite Windows Server Monitoring Agent uses a centralized configuration model that eliminates the need to manually configure each server individually. Instead of logging into dozens of servers to adjust monitoring thresholds, you manage everything from the Web Client.

How it works:

1. Central Configuration Storage - All monitoring settings are stored in the Nodinite Configuration Database
2. Agent Synchronization - Agents periodically sync with the Monitoring Service to retrieve their configuration
3. Group-Based Management - Organize servers into logical groups with shared monitoring thresholds
4. WMI-Based Monitoring - Agents use Windows Management Instrumentation (WMI) to collect server health metrics

Why this matters:

• Scalability - Manage 100+ servers from a single interface
• Consistency - Apply identical monitoring thresholds across server groups
• Agility - Update monitoring thresholds without touching individual servers
• Auditability - Track all configuration changes from the central system

Note

Monitoring and remote configuration are available after you install and create the initial Monitoring Agent Configuration for the Windows Server Monitoring Agent. First-time users start here.

The Nodinite Windows Server Monitoring Agent account must be a local administrator on the target server to monitor. Make sure to review the Prerequisites.

The agent performs monitoring according to your user-defined configuration per Group.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open a modal and configure the agent:

Example of the Remote Configuration button for managing Windows Server Monitoring Agent settings.

You can also make many specific configurations directly on the Resource using the Action button if the Monitor View uses the Remote Actions feature.

You must be a Nodinite Administrator to Manage the collection of Windows Servers.

Add Group

The Windows Server Groups tab holds an array with zero or more Group configurations.

Example of the Windows Server Groups tab before adding any server groups.

• Press the Add button to add one (or more) Group(s):

  
  Example of a new Group configuration accordion ready for server assignment.

  Repeat this step for each unique Group of Windows Servers to monitor with Nodinite.

To manage the configuration, click the caret down icon to expand the Group accordion. There are a number of features with monitoring thresholds and settings within the Tabs:

Tabs

• General tab
• Servers
• Certificate tab
• CPU tab
• Disk tab
• Event Log tab
• IIS Tab
• Memory tab
• Network Tab
• Ping tab
• PowerShell tab
• Scheduled Tasks tab
• Windows Services tab

General Tab

Click the General tab to manage essential information about the Group with Windows Servers to include in the monitoring.

Example of the General tab with Group name and description fields.

• Enabled - When checked, enable the monitoring of Windows Servers in this Group.

  
  Example of an enabled Group configuration showing active monitoring state.

  
  Example of a disabled Group configuration showing inactive monitoring state.

• Name - The name of this Group configuration.

• Description - Specify a user-friendly short description of this Group configuration.

Servers Tab

You can include zero or more Windows Servers in the Group. A Windows Server can only exist in one group. Duplicates are not allowed.

Click the Add button to add a new Windows Server to include in the monitoring.

• Enabled - When checked, enable the monitoring of this Windows Server.

  
  Example of an enabled Windows Server configuration showing active monitoring.

  
  Example of a disabled Windows Server configuration showing inactive state.

• Display Name - The display name to use for this Resource.

  Resources group per entry using the Application naming concept.

  
  Example of the Application filter displaying servers grouped by Display Name.

  Note

  Changing the name may require reconfiguration of affected Monitor Views.

• Description - Specify a user-friendly short description of this Group configuration.

• Host-name or IP address - The host-name or IP address of the Windows Server to include in the monitoring.

Settings tab

From within the Settings tab, you provide some details that determine the operation behaviour of the Windows Server Monitoring Agent.

Example of the Settings tab showing environment, debug, and diagnostics monitoring options.

Environment

The name for the type of Environment (e.g., Test/Prod/QA). Part of the common features shared with all Monitoring Agents.

Debug

When checked, the monitor agent writes detailed debug information to the diagnostics file. This option is disabled by default.

Enable Diagnostics Monitoring

^{New 6.3.2} When checked, diagnostics monitoring is enabled and will check for errors in the diagnostic log files. When unchecked, the diagnostics resource will always show OK status.

Culture Information

This setting existed in previous versions of the Windows Server Monitoring Agent. Any datetime now renders in the local date/time format in your browser using the device's locale settings. UTC information is usually in the tooltip.

Save

You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.

Example of the Save and Save and Close buttons for persisting configuration changes.

Note

The delay in presenting the new evaluated state depends on the synchronization interval set for the monitoring agent. Click the Sync Now button to force an immediate synchronization.

Save and close saves and closes the dialogue.
Cancel closes the dialogue without saving any changes.

Add Windows Server Monitoring Agent Configuration

After the successful installation of the Windows Server Monitoring Agent you must provide Nodinite with connection details, so the Monitoring Service knows there's a new guy in town.

No monitoring or other configuration of the Windows Server Monitoring Agent can be performed before the steps outlined below have been executed.

Configuration Steps

1. Add and configure a new Monitoring Agent Configuration

   Connection information is available in the README.txt file in the installation folder

2. Use the Remote Configuration feature to configure the agent. Detailed at the beginning of this user guide.

3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Windows Server Monitoring Agent according to business needs.

   Add or manage Monitor View

4. Fine-tune specific settings directly on Resources using Remote Actions.

Next Step

• Add or manage a Monitoring Agent Configuration
• Add or manage Monitor View
• Update

Related Topics

• Install Windows Server Monitoring Agent
• Monitoring Agents
• Applications