We’re pleased to let you know that we’re putting the finishing touches on a couple of exciting new workflows: ‘Active Issues’, to help you manage failed checks across your estate, and ‘Unmonitored Devices’, to make it easier to detect and onboard new devices across your networks. Together the two new views mark a significant step forward in terms of day-to-day technician efficiency and workflow management in RMM, along with generally evolving the UI design in RMM.
The new workflows are in addition to existing features, and will appear in the Dashboard section of the left-side navigation bar:
We’re aiming to roll these enhancements out gradually to customers over the next couple of weeks. Here are all the details:
For the first time, view failing and cleared checks across clients and their devices in a new, consolidated ‘Active Issues’ view. Filter the view by check status, device type and check type for a more efficient, streamlined workflow.
Run and clear checks, either one at a time or in bulk. Update the ‘clear’ settings of cleared checks, and keep an eye on checks that are currently in the ‘soft failure’ state, based on your account’s alerts policy.
You can also hop over to the device in the main devices section to inspect the failed check(s) for more details.
The new view will initially release in ‘beta’, and you’ll be able to click the beta icon top-right of the screen to submit a rating and share your feedback. We’d very much like to hear your views and input to help us prioritise future enhancements in this area.
Note that during the ‘beta’ release, Active Issues does not yet support the option to add check clearing ‘notes’, as indicated in the UI when you clear checks.
The second new workflow to be released in the next couple of weeks is designed to help you monitor new devices that are connecting to the networks you manage. As with Active Issues, the new ‘Unmonitored Devices’ view is in addition to existing functionality, and will also be available from the left side navigation bar.
The new workflow provides much greater visibility into unmonitored devices, by showing all new devices over the last 30 days across all your monitored networks. It includes desktops, laptops, servers, as well as network devices such as routers, switches, firewalls, printers, etc. The new view greatly enhances the visibility of new devices, so you’re able to spot and onboard new devices more quickly and efficiently. The increased visibility of what’s connecting to your customer networks may also help in terms of network security.
To help you keep track, we’ve added a new set of widgets to the at-a-glance Dashboard – these show you unmonitored devices by device type and by operating system. Click any of the widgets to jump straight to a filtered view of those devices in the new Unmonitored Devices view. Select an individual device to jump over to the relevant network in the Networks tab for more details about the device, and to bring it under management.
Of course we’re very keen for your feedback for this feature as well – feel free to use the feedback form on Active Issues to share your comments.
In addition, we’ve also just released a couple of smaller user-focused feature updates, both very much aimed at helping day-to-day users do their work a bit more efficiently:
- New ‘Clone’ option for ‘Monitoring Templates’: Now you can copy an existing monitoring template much more easily, saving you considerable time and effort when you want to add a new template:
- New client search in ‘Settings’ dialogs: Jump straight to the right client and site with a new search option in the ‘Settings’ dialogs. It means much less scrolling up and down long lists of customers trying to find the right one (available for Patch Management, Managed Antivirus, Take Control, Backup & Recovery, Web Protection and Network Discovery):
Patch Management Engine v1.2.5
There is also a Patch Management Engine update this week, with the release of PME 1.2.5. It includes an update to solve a specific case that can trigger PME to be misconfigured with error “System.OutOfMemoryException”, generally found on servers. This issue seems to be caused by not having enough continuous blocks of free memory, even if there is plenty of memory available. This is usually why PME will work for an amount of time after a reboot of the device. This solution will instead keep PME in memory rather than unloading, to ensure resources are made available to it. To trigger this feature, the value of “UnloadModuleAppDomainAfterEachRequest” must be changed from “true” to “false” in C:\ProgramData\SolarWinds MSP\SolarWinds.MSP.RpcServerService\config\RpcServerConfiguration.xml
Last but not least, we’re also shipping several customer bug fixes in this week’s update, please see release notes below for details.
Summary for Service Release
– Announcing Active Issues and Unmonitored Devices workflows, clone monitoring templates, client search box, Patch Management Engine v1.2.5
– RMM Console v2020.06.02
– No agent updates
RMM Console v2020.06.02
FEATURE: New customer and site search box on the feature ‘Settings’ dialogs
FEATURE: New Clone option for Monitoring Templates
UPDATE: Option to highlight text on the Patch’s Management Workflow dialog for copy n pasting
BUGFIX: Extend ‘client group’ support to the Agent auto-update dialog to ensure ‘All servers’ / ‘All workstations’ only covers the clients in the client group
BUGFIX: Ensure User Audit Report shows Edit User event when enabling/disabling a client’s Executive Summary Report
BUGFIX: Managed Antivirus (MAV-BD) Corrected Portuguese translation for Deep Scan
BUGFIX: Ensure user permission for Automated Tasks doesn’t interfere with ability to run checks
BUGFIX: Update to OS so it doesn’t show Server 2003 incorrectly when updating agent
Patch Management Engine v1.2.5
UPDATE: Resolve issue with Patch Status Check failing because of RPC service returning with System.OutOfMemoryException
UPDATE: Enhanced the detection of installation status for Cumulative Updates