- 6 minutes to read

Monitoring and Managing Windows Server

Nodinite empowers you to monitor, manage, and optimize your Windows Server infrastructure with confidence. Instantly discover all servers, automate health checks, and provide secure, role-based access for your team.

✅ Instantly discover and monitor all Windows Servers
✅ Set custom thresholds and receive real-time alerts for server health and uptime
✅ Share access to selected servers with end-users for secure self-service
✅ Actionable alerts and Remote Actions within role-based Monitor Views to resolve issues fast

graph TD subgraph "Nodinite" agent[" Windows Server Monitoring Agent"] web[" Web Client"] monitoring[" Monitoring Service"] end subgraph "Your Infrastructure" server1[" Windows Server 1"] server2[" Windows Server 2"] server3[" Windows Server 3"] end agent -->|WMI| server1 agent -->|WMI| server2 agent -->|WMI| server3 monitoring --> agent web --> monitoring style server1 fill:#90EE90 style server2 fill:#FFD700 style server3 fill:#FF6B6B

Diagram: Nodinite Windows Server Monitoring Agent uses WMI to discover and monitor all Windows Servers, providing real-time health status through the Web Client.

Windows Server as Resources
Example list of monitored 'Windows Servers' as resources in a Monitor View.

Monitoring Features

  • The Nodinite Windows Server Monitoring Agent uses WMI to automatically discover all Windows Servers. Sharing insights is easy with Monitor Views.
  • State Evaluation – Ensure the Windows Server is up and running with user-defined thresholds.
  • Category-based monitoring – Group monitored Resources by Categories for streamlined management.

What Does Nodinite Monitor on Windows Server?

The Windows Server Monitoring Agent can monitor many aspects of your Windows infrastructure. This page focuses on Windows Server instance monitoring (availability, uptime, reboot state).

Windows Server Feature What It Monitors Learn More
Windows Server Server availability, uptime thresholds, pending reboot state This page
Disk Free space on all volumes, disk performance Disk Monitoring
Memory RAM utilization and availability Memory Monitoring
Network Network interface status and configuration Network Monitoring
IIS Application pools, websites, bindings IIS Monitoring
Windows Services Service status, startup type, dependencies Windows Services Monitoring
Scheduled Tasks Task execution status and history Scheduled Tasks Monitoring
Event Log Windows Event Log entries and patterns Event Log Monitoring
PowerShell Custom PowerShell script execution PowerShell Monitoring
Ping Network connectivity and latency Ping Monitoring

What This Page Covers

This page documents monitoring of the Windows Server instance itself:

  • Server Availability – Is the server online and reachable?
  • Uptime Thresholds – How long has the server been running without reboot?
  • Pending Reboot State – Does the server require a restart (Windows Updates, etc.)?
graph TB subgraph "Traditional Monitoring" t1[" Manual Server Checks"] t2[" Spreadsheet Inventory"] t3[" Reactive - Issues Found by Users"] t4[" IT Admin Only Access"] end subgraph "Nodinite Windows Server Monitoring" n1[" Automatic Discovery via WMI"] n2[" Proactive Alerts on Thresholds"] n3[" Real-Time Health Dashboard"] n4[" Self-Service for Teams"] n5[" Remote Actions (Restart, Configure)"] end t1 -.->|vs| n1 t2 -.->|vs| n2 t3 -.->|vs| n3 t4 -.->|vs| n4 style n1 fill:#90EE90 style n2 fill:#90EE90 style n3 fill:#90EE90 style n4 fill:#90EE90 style n5 fill:#90EE90

Diagram: Traditional vs Nodinite Windows Server Monitoring - automatic discovery, proactive alerts, and self-service access.## State evaluation for Windows Server

Nodinite displays each monitored Windows Server as a Resources. For example, if you have 2 Windows Server configurations, you will have 2 'Windows Server' resources in Nodinite.

  • The Resources name matches the Windows Server name in the format Display Name <Service Name>.

  • The 'Windows Server' resource belongs to the following Category:

    Category Description
    Windows Server Ensure Windows Servers are up and running

    Categories
    List of the Windows Server category as a filter in a Monitor View.

  • The Application name is the Display Name from the configuration of the monitored Windows Server.

Each item (presented in Nodinite as a Resource) is evaluated with a state: OK, Warning, Error, or Unavailable.

You can reconfigure state evaluation at the Resources level using the Expected State feature.

Note

Depending on the user-defined synchronization interval for the Windows Server Monitoring Agent, there may be a delay before Nodinite Web Client/Monitor Views reflect changes. Click Sync All (or use the dropdown for individual agent selection) to force a resynchronization.

Synchronize on demand
Option to force Nodinite to request a resynchronization with the monitoring agent.

Monitoring Windows Server

For the Windows Server category, Nodinite evaluates the monitored state as described below:

stateDiagram-v2 [*] --> Checking: Agent Connects Checking --> OK: Server Reachable
Uptime Normal Checking --> Warning: Uptime Threshold Breached
or Pending Reboot Checking --> Error: Uptime Error Threshold
Exceeded Checking --> Unavailable: Network/Security Issue
or Bad Configuration OK --> Warning: Uptime Warning Warning --> Error: Uptime Error Warning --> OK: Server Rebooted Error --> OK: Server Rebooted Unavailable --> OK: Issue Resolved

Diagram: Windows Server monitoring state flow - from initial check to various health states.

State Evaluation Table

State Status Description Actions
Unavailable Service not available
  • The server can't be reached or evaluated due to network or security issues
  • Bad configuration (invalid/non-existing Windows Server)
 Review prerequisites
Error Error state raised The Windows Server should be rebooted according to the user-defined Error threshold Restart
Edit
Details
Warning Warning state raised The Windows Server has breached the Uptime Warning threshold or has a pending reboot Restart
Edit
Details
OK Online The 'Windows Server' is up and running Restart
Edit
Details

Actions for Windows Server

The following Remote Actions are available for the Windows Server Category:

graph LR server[" Windows Server"] details[" Details
(View server info)"] restart[" Restart
(Reboot server)"] edit[" Edit Configuration
(Change thresholds)"] server --> details server --> restart server --> edit details --> info[" Server Info
(Hostname, OS, Uptime)"] restart --> confirm[" Confirm Restart"] edit --> config[" Uptime Thresholds
Restart Duration"] style details fill:#87CEEB style restart fill:#FFD700 style edit fill:#90EE90

Diagram: Available remote actions for Windows Server monitoring - Details, Restart, and Edit Configuration.

Action What It Does When to Use
Details View server information including hostname, OS, uptime, pending reboot status Daily health checks, verify server state, check uptime
Restart Remotely reboot the Windows Server with configurable delay Apply updates, resolve performance issues, clear pending reboot state
Edit Configuration Modify uptime thresholds and restart duration Adjust warning/error thresholds based on maintenance schedules

Remote Actions
Available remote actions for the Windows Server category.

Details

View details for any Windows Server resource by clicking the Action button and selecting Details in the 'Control Center' section.

Details Menu Action
Open the details modal by clicking the 'Details' action menu item.

Details modal
Example of the 'Details' modal for the Windows Server.

The Server tab displays core information about the Windows Server instance, including:

  • Computer Name – The Windows Server hostname
  • Operating System – Windows version and edition
  • Last Boot Time – When the server was last restarted
  • Uptime – Current uptime duration
  • Pending Reboot – Whether a restart is required

Additional monitoring capabilities:
For detailed monitoring of disk space, memory usage, network interfaces, and CPU information, see the dedicated monitoring pages:

Restart

If the Administrator enabled the restart server feature in the Remote Configuration, the Restart button is visible on the Details page.

You can Restart the Windows Server by clicking the Restart button.

Restart Button
Restart the Windows Server using the 'Restart' action.

You will be prompted to confirm the operation:
Restart intent modal
Example of the 'Restart' prompt.

A modal will present the result of the operation:
Restart Success
Example of a successful request to restart Windows Server.

Edit Configuration

Manage the Windows Server resource by clicking the Action button and selecting Edit configuration in the 'Control Center' section.

Edit configuration Menu Action
Edit configuration using the 'Edit' action.

Next, click the option to present the modal.

Edit configuration modal
Example of the 'Edit configuration' modal.

You can edit the following fields:

  • Restart Duration – Duration in seconds until the server reboot actually starts (0-10000)
  • Description – User-friendly description
  • Uptime Warning TimeSpan – Alert with a Warning when the server uptime is more than the specified date time span (days.hours:minutes:seconds, e.g. 365.00:00:00)
  • Uptime Error TimeSpan – Alert with an Error when the server uptime is more than the specified date time span (days.hours:minutes:seconds, e.g. 1337.00:00:00)

Uptime Alert
When it is time to reboot the server according to the thresholds, the state is either a Warning or an Error.

Configuration

Use the General tab in the Remote Configuration to manage Windows Server configuration.

Next Step

Add or manage Monitor View
Monitor Disk Space
Monitor Windows Services
Monitor IIS

Windows Server Monitoring Agent
Disk Monitoring
Memory Monitoring
Network Monitoring
CPU Monitoring
Windows Services Monitoring
IIS Monitoring
Scheduled Tasks Monitoring
Event Log Monitoring
PowerShell Monitoring
Ping Monitoring
Resources
Monitoring
Monitor Views