|
|
|
|
Features
NSM-1128 |
The Network Monitor log directories have been moved to the |
NSM-1198 |
It is no longer necessary to select an agent/machine group when adding an asset manually. |
Bug Fixes
NSM-1161 |
Fixed an issue where email notification from Network Monitor was not sent when using an open SMTP relay. |
NSM-1205 |
Devices from standalone KNM that could not be mapped to VSA assets automatically are now placed in a group for manual assignment. |
NSM-1210 |
Fixed an issue with the Directory Property monitor monitoring a network share. |
NSM-1227 |
Fixed an issue that prevented Network Monitor users from logging into the Dashboard Map Editor (DME) utility. |
NSM-1234 |
Fixed an issue where network/assets for a new tenant were not appearing under the Network Monitor module. |
NSM-1254 |
Fixed an issue where log file monitoring was not raising an alarm on odd numbered lines. |
NSM-1256 |
Fixed an issue where the network name in Network Monitor was changed to "unnamed" after services were restarted. |
NSM-1267 |
Removing an agent now correctly updates the corresponding asset record in Network Management. |
NSM-1277 |
The documentation of the Network Monitor > Asset Template page was updated. |
NSM-1285 |
Fixed an issue where email sent from Network Monitor had an incorrect sender address. |
NSM-1291 |
Fixed an issue where the organizations within a drop-down list were not sorted correctly. |
NSM-1298 |
Fixed an issue that caused groups, in some cases, to be linked to the wrong parents on startup. |
NSM-1303 |
Fixed an issue with Network Monitor being unable to connect to SQL instances using non-standard ports. |
NSM-1312 |
Fixed an issue where assets could not be created manually via Network Monitor module. |
NSM-1320 |
Fixed an issue with installing the ODBC driver for Network Monitor module. |