Please share with the community what you think needs improvement with Webroot SecureAnywhere Business Endpoint Protection.
What are its weaknesses? What would you like to see changed in a future version?
I think the one bad point about this product is that we did not find a way for Webroot to generate reports or schedule automatic reports to be sent to clients. These would be reports on the status of their device, the status of their security, and information about backups. The option for providing this information is not there and we cannot run the scan from our end. It must be run from the client's end. My only other hope would be that they would still continue providing this product. But they have scheduled it for end-of-life on March 1st or April 1st. I do not know why they are removing it from the market. But it is obviously their decision to make.
There's no static analysis inside their solution. The solution should add the capability to use cloud access so that we can provide clients with an endpoint code. There needs to be more advanced analytics. It would make it a more powerful antivirus solution within the marketplace.
This product has room for improvement to display a more detailed representation of the problem when a virus is or isn't stopped. We need to know more details about how the virus interacted with the computer. That is where some of the other products are starting to look better. It needs to work without disconnecting everyone. This is very important. In SentinelOne, you can disable all ports. You can look up the machine, play with the machine, etc. Webroot can do all sorts of things on the network. It's very good. There are some cool possibilities for more control within the environment. We have a broad list of plugins to use with a high degree of confidence. Backups are another aspect that can be improved. Having a backup solution that's associated with this in the case everything fails and the machine was destroyed would help us get the files back in emergencies.
The console spins up relatively slowly, and some of the configuration items are obscure (e.g., reporting back one time per day is a default setting) and need to be tweaked.