Coming from other enterprise AV products I am surprised that Webroot's console doesn't allow me to add notes or a description to a client.
I'd like to see the console have two functions added, first it would be great if the WR endpoint client would query and uploaded the endpoint's computer description to the console.
In PowerShell the info can be pulled by running - Get-ItemProperty -Path "HKLM:\system\CurrentControlSet\Services\LanmanServer\Parameters" -Name "SrvComment" so I don't think it would be a stretch for the client to pull the info. Extending the management database and adding the function to the console, that might be a different story.
Second, I'd like to be able to add to add/edit notes attached to an endpoint but have those notes only be visable in the console.
If there's already a way to make this happen in the current console please let me know.
We face the issue that Webroot client does not use its proxy settings if there is any proxy setting set in IE proxy settings (on Win 7) which is not good at all - we consider it a bug. This way the clients in our network cannot cannot communicate to the Webroot servers, because we have to use different proxy for Webroot than for Internet browsing (we have a local and a foreign country proxy server).
We think if there is any proxy set in WR it should use it even if IE has a proxy setting, too.
Please fix the proxy usage in WR so that it ALWAYS use the proxy that you set in the WR settings, not automatically use IE proxy.
Maybe want to create an new option in the 'Proxy type' drop down box to "Use IE proxy settings". Then, admins can select what they want Webroot to use.
I would like to see an agent option to make a scheduled scan for folders and or shares, for example to scan an networkshare once a day or once a week on a certain time. by this way we can also offer a scheduled solution for storage solutions.
On the GSM dashboard it would be nice to show a list of machines that have not phoned home in the past 24, 48 or other configurable timeframe. We have this information available already when in a particular site but that can be a tedious thing to check regularly.
Our experience has been that machines will randomly stop checking in and the fix is always to uninstall / reinstall which is bad enough, but to have to cycle thru all sites to find out which machines are in this state is very time consuming.
I have just been playing around with settings with a view to offering some of our cleints reporting access to their own site's consoles.
I have granted only "view" access to one site, and am actually dismayed to see that this also gives access to the resources tab.
As a managed service provider, we deploy webroot to our clients via various methods depending on the clients requirements. If we do grant access to the console, we don't want end users having the ability to download and install an .exe where we already have an .msi deployment via group policy in place.
Would it be possible to have this as a selectable feature when setting up a local access account?
Add a feature so we can permananently delete from quarantine using the console. That feature exist in the user GUI for unmanaged clients so it makes sense that it should exist in the console for managed clients
One of the biggest frustrations we have is that we cannot fully customise the endpoint clients from the portal on the server.
For example, if you enable system cleaner, it automatically wipes every endpoint's Microsoft Office Recent File list. There is nothing in the policies to be able to turn this off before enabling system cleaner. As such, if we want to use system cleaner, we have to make all 100 endpoints unmanaged, then edit the system cleaner settings manually to turn off Microsoft Office Recent File list clearing, then move the endpoints back to being managed by policy.
The best option would be to allow administrators to customise every single feature of the system cleaner from policies.
We have deployed Webroot on over 20 servers and some of these keep losing contact with the console.
The solution given by Webroot support was:
The Webroot service requires the service to restart due to a long uptime and you need to do regular reboots. We have passed the case along with the logs to our Development to see if they can come to a resolution that ensure as little maintenance to these machines as much as possible.
This is a fundamental feature of a server Antivirus solution, to be able to cope with the computer being on 24/7.