Release history
41 releases with fixes since version 11. Show everything
-
Version 16.0.0 Preview Fixes26 Features81
Highlights
- Critical[#6750] Adding nodes via script through the NC API no longer fails with `Status code` errors.
- Critical[MJ0038] Windows services excluded via a case-insensitive regex no longer trigger unwanted Service Stopped alerts.
- Critical[MP0035] The alerting script now runs correctly for the NetCrunch Status alert.
- Critical[MP0079] Alerts with time restrictions and disabled mode now close properly instead of staying open.
- Critical[MP0084] Nodes with monitoring disabled no longer generate events.
-
Version 15.4.3 Latest Fixes5
Highlights
- CriticalUpdate NodeJs to 20.20.2 (Security Fix)
- MajorImproved stability for NetCrunch servers hosted on AWS during periods of disk inaccessibility
- MajorOverall performance and stability fixes
- MajorProbe re-connection issues
- MajorUnable to change port for TLS connections when adding an SMTP server.
-
Version 15.4.2 Fixes18
Highlights
- Critical[File Sensor] Fixed a bug where adding a second SFTP File or Folder sensor caused both sensors to stop functioning.
- Critical[Probe] Fixed an issue where cloud-connected probes could consume 300% CPU.
- Major[Alerting] Fixed a bug where custom alerts were not saved if the template was already assigned to a node.
- Major[Alerting] Fixed an issue where Windows service alerts (defined with RegExp) would only trigger once, even when multiple services matched.
- Major[Alerting] Resolved incorrect triggering of correlated Windows service alerts regarding "running" vs. "not running" states.
-
Version 15.4.1 Fixes12 Features4
Highlights
- CriticalData Storage: Fixed a bug that caused active alerts data to grow to an abnormal size in certain situations.
- CriticalRemote Probe High CPU: Fixed high CPU usage on the Remote Probe when the cloud connection is unavailable.
- Major[MP0068] Device Config: Fixed an issue where Device Config sensors failed to display saved configurations after an upgrade (restores feature visibility).
- Major[MP0069][MP0071] SNMP Trap: Fixed an issue where alerts were triggered even when the condition was not met (fixes broken alert logic).
- MajorAlerting Logic: Ensured alerting actions are not triggered when Atlas monitoring is disabled (prevents false alarms).
-
Version 15.3.0 Fixes35 Features12
Highlights
- CriticalFixed memory leak in Physical Segments when monitoring stacked switches.
- CriticalNetwork Services were monitored even when Atlas monitoring was disabled.
- Major"Report Collector Scheduling" missing for Network Traffic (SNMP) collectors. [MP0054]
- MajorAfter adding a sensor to a monitoring target, it's created without default alerts or data collectors.
- MajorAn empty file is exported from the grid when a specific column filter is applied. [MP0067]
-
Version 15.2.1 Fixes17 Features10
Highlights
- CriticalAdding a new node to an IP network causes a previously added widget to disappear. [MP0046]
- CriticalCannot complete login due to an incorrect username and password" issue displayed on ESX/VM engine with OK status. #6938
- CriticalCheck Time and RTT performance trends for PING network service show values when Failure Rate is 100%. #6792
- CriticalDisabling Physical Segment in one site disables it in all.
- CriticalHistory hangs or is very slow when querying alert by parameters.
-
Version 15.1.1 Fixes11
Highlights
- CriticalIn certain situations statusDB could grow to hundreds of megabytes due to lack of proper cleanup. This could result in high memory usage and very long startup times.[#6590]
- CriticalNon-root organization AD users can't log in to the desktop console.
- MajorEmail messages are not delivered to e-mail addresses containing certain characters (i.e. apostrophe). [MP0038]
- MajorGaps in trend data can occur when a large number of metrics are monitored by a single sensor (i.e. 1000).
- MajorHyper-V checkpoint issue when host is in a language other than English [MP0037]
-
Version 15.1.0 Fixes20 Features9
Highlights
- MajorAdded missing move operation for networks in Atlas Tree to organize networks in folders [#6362]
- MajorAfter importing Atlas to another machine $Extended.NetCrunchServer parameter has not beed updated in alerting message formats [MP0030]
- MajorAfter upgrade web server is not working properly and needs to be restarted. Sending messages doesn't work.
- MajorAfter using `Atlas Upgrade` function, some views can be missing
- MajorCan't upgrade atlas containing Printer sensor with custom SNMP profile [#6267]
-
Version 15.0.4 Fixes4
Highlights
- Critical30 day trial license registration was not possible
- CriticalUser with administrative access right couldn't open desktop console [MP0029]
- MajorReport from current view couldn't be created
- MajorRouting Map could show nodes other than routers (i.e printers) #6042
-
Version 15.0.2 Fixes3
Highlights
- MajorAfter atlas upgrade all map icons have been lost
- MajorIf atlas contains multiple sites then name of `Local - NetCrunch Server` site was overriden
- MajorUpgrade policies of old atlases was not working
-
Version 15.0.1 Fixes29 Features36
Highlights
- CriticalDefault system access profiles and users could be modified or deleted by admin
- CriticalSecurity vulnerability - allows unauthorized users to execute certain APIs
- CriticalSecurity vulnerability - It is possible to access NetCrunch from a local server machine with a hard-coded user account
- CriticalSecurity vulnerability - possible access to internal NetCrunch data by a user who is not an administrator
- CriticalSecurity vulnerability - possible elevation of access by logged in non admin user
-
Version 14.2.2 Fixes5
Highlights
- MajorError after upgrade from earlier version (11,12,13)
- MajorGeneral folder missing from left panel in SNMP views [#5734]
- MajorSNMP performance issues causing timeouts
- MajorSNMP Views - problem with converting a number from an octet string.
- MinorMisleading error message regarding SSL-based network services.