I'm requesting some help in defining what should be on the GSM Dashboard. Our current theory is that the default dashboard layout should provide Admins with a mix of information covering that you need to know now and that which is of interest but not urgent.
Need to know now
Of interest but not urgent
There's lots of way we can slice up the data and I'd like to give you a default dashboard that is immediately useful which you can modify as required.
Please let me know directly ( just message me on this forum ) what you think should be on the dashboard and why.
Thanks for your assistance.
Senior Product Manager
It might be useful to get details about "Undetermined software seen" on the network
maybe list the package/file and what endpoints it is seen on.
an alternative is to list machines with "undetermined software" on them.
this could be pretty useful especially with clients/MSPs who would like to have quick notifications about new packages for security reasons or at least this gives them a quick overview instead of going into the console and requesting a report about the same.
Not sure about the performance implication on the back-end when enabling this out of the box on the GSM consoles but thought it would be useful sharing the idea anyway
Need to be able to search all the sites for computers.
Need to be able to take all actions on any computers that need it without having to go to the site level.
On the new Groups dashboard,
Add ability to sort via the top groups.
Add export to CSV
Add ability to select the timeframe for "not seen recently" - We have a number of single use clients who often leave their computer off for longer periods of time than a business does.
Change the name displayed in the list to that as it is at the site level. We use that to help ID and filter infrequently used PCs when doing weekly checks.
Allow users to have more than one tab open at a time. We frequently get logged out if you try to open more than one site at once.
I'd love a summary of processes recently being highly-scrutinized by the Realtime Shield (ie. entries like this in WRLog.log), since 90% of the user-reported app-conflicts with Webroot we see are reflected in these:
Thu 2018-04-26 09:07:40.0775 Monitoring process C:\WINDOWS\system32\dashost.exe [66CFAA5940A06DAF10F5203BC2B1A5AB]. Type: 8 (135253)
You'd have to build functionality into the agent to report these back, and of course expand your backend schema a bit, so it's not a trivial addition. Just throwing it out there