- OpManager: On editing the threshold of any performance monitors from the device snapshot page, the consecutive times allowed “0” to be given as input. This has been fixed now.
- OpManager: Few build versions of HyperV2016 were not categorized under “HyperV” due to mismatch in the criteria of HyperV related WMI (Win32_OperatingSystem) class. This issue is now fixed.
- OpManager: Too many unnecessary discovery status popups were displayed while receiving VM events from vCenter environment. This led to slowness due to frequently scheduling inventory updates in OpManager. This has been fixed now.
- OpManager: While editing a process monitor from the device snapshot page, when the instance count criteria matched “=” and if the threshold value was set to “0”, the Rearm value was automatically set to “0”. This issue is now fixed.
Other recent articles in the same category
You may be interested in these other recent articles
Last Week Best ManageEngine Updates – Part 31
18 December 2023 | Nazim Nadir
Right before Christmas, ManageEngine is giving out their quality of life updates. From ServiceDesk Plus to M365 Manager Plus, you will see plenty of updates…
Read moreLast Week’s Best ManageEngine Updates – Part 30
6 December 2023 | Nazim Nadir
ManageEngine is named a strong performer for 2023 in last week updates. There are also new updates to their suite of applications and they have…
Read moreLast Week’s Best ManageEngine Updates – Part 29
27 November 2023 | Nazim Nadir
Exciting news of ManageEngine Linkedin Live webinar has been announced alongside some application updates and the release of a new E-Book. Whether you’re new to…
Read more