This release brings mainly bugfixes and significant performance improvements. You might noticed there were no release notes about version 2.12 released 2 weeks ago. Let me apologise about it, the release were on time, just the release notes were not published.
What’s new
Synchronisation between management console and device is two times faster.
Added dialogue to choose new group when moving devices.
Updated a confirmation modal when deleting groups or subgroups with existing devices.
Adjusted device list to show if device’s policy is inherited.
What has been fixed
Devices list is refreshed after some policy is deleted.
Fixed malformed top banner in Settings template.
Shutdown task on Mac did the device restart and vice versa.
Some icons were not shown.
Fixed ability to edit firewall app rules in some corner cases.
Thanks for your feedback guys! In case you have some other ideas how to make our console UI better, make sure to write it here or send it to me or anyone from the Avast team
We really love to see you guys are happy with the improvements!
I actually do have a couple of suggestions, and it would help me out a TON if you could implement it.
When I open the console, all devices that have not checked in recently show up as “In Danger” so I always have an “In Danger” status bar taking up a good portion of my console. Due to the size/nature of our deployments, we will inherently always have a bunch of machines that are imaged and awaiting to be taken out to satellite locations, so they end up displaying as “In Danger” for a month or so.
Is there a way to change the status of machines that haven’t checked in or are out of date to something other than “In Danger”, and reserve “In Danger” only for infected machines? It’s misleading and makes it constantly seem like something is wrong when people see the console.
We project that we will have an additional ~17,000+ installations in the first half of the upcoming year, so a fix for this would help us out immensely.
Totally agree with DFox911 about “Danger” warning when a machine does not connect during X time to the console, in our case we also always have the “In Danger” notice too (we have 2 machines that turn on only very occasionally) and is extremely annoying. In addition, we have also received such consultation from some customers with AfB. I think this is one little problem that should be solved soon.
I kind of detailed how I’d like it to work in my original post, but I envision it working in a way where systems that have been offline/out of contact for a certain amount of time throw a different flag than “In Danger” and leave “In Danger” reserved ONLY for systems that have been infected. If I want to see how many systems have been offline, I can go filter the devices, but I would really like to only be alerted about infections (things that require immediate intervention) in the alert bar.
