I need to know which endpoints need attention. I do NOT want to have to search for trhem, or be bothered about endpoints that do not need attention.
I want to schedule a daily report for all the endpoints we manage, which lists ONLY endoints that are _currently_ showing as requiring attention. If they don't need attention, I don't want to know about them, and I don't want a report about them.
Currently I have a choice: get a report on every bloody endpoint whether it needs attention or not, or no report at all.
The single biggest problem I have with Webroot is the brain-dead reporting.
Problem: We have deployed 1800 Webroot agents. Sometimes they do not activate. This requires us to manually uninstall Webroot, enter a CAPTCHA, then re-run the executable. Fine once, annoying after 50 reinstalls.
The current "fix" is to use the following command to uninstall, followed by passing a CAPTCHA, the re-running the installer and praying it activates (90% of the time)
"C:\Program Files (x86)\Webroot\WRSA.exe -uninstall"
Image below of what an unactivated Webroot looks like, blue window with red-sliders.
I make a lot of automation scripts for my company through Kaseya Procedures. This could be done for Labtech or any other RMM tool. RMMs often give the ability to run code as a specific user, such as the logged in user or SYSTEM\NT AUTHORITY. This means the code needs to run without a GUI.
It is easy to check if Webroot is installed but unactivated, by checking the following keys:
If the following Key exists, Webroot has been installed:
If the following Value is 0, Webroot is installed but unactivated.
If this key is detected as 0, I want to run a script that uninstalls Webroot, then re-runs the installer in the background.
An idea for the developers
Please create a batch command that I can sent to an workstations that uninstalls Webroot with a verification code, for example, the site ID. An example command:
C:\Program Files (x86)\Webroot>WRSA.exe -uninstall -siteID 1234-ABCD-1A13-1A12-12A1
That verification code is only available via our web-console by our staff anyways, so it functions as an alternative to the CAPTCHA.
Detect if HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\WRData\Sta
Start %programfiles(x86)%\Webroot\WRSA.exe -uninstall -siteID 1234-ABCD-1A13-1A12-12A1
Wait 5 minutes to allow for initial scan to complete
Detect if ProtectionEnabled = 1, if true, write log entry marking successful reinstall.
An alternative request would be to inject our site ID into the registry for the unactivated agent, by overwriting some key that Webroot uses for registration, and restarting the service.
Thank you for your consideration, have an amazing day!
Under Group Management I can double click a computer name and either change the name or add a note in brackets. This is great. What isn't so great is that the override doesn't stay in place. If I update the screen or do anything then the data vanishes.
Whats the point in being abke to double click in the first place?
On a small site I can use this to add a note (MD's PC) or similar to help identify what machine is what as I have no control over PC names
I don't actually want to change the name (which I suspect on balance would be a bad thing) - but the ability to add a note in brackets would be very useful. Either add a note in brackets oor have a customisable notes field that I could use. NOt perhaps a lot of use for a large site, but very useful for small sites
The ability to assign multiple policies to an override would be a great addition to this product. Currently (if I'm not mistaken) you can only assign to one policy via a dropdown when creating an override. To work around this, you have to go in and create multiple overrides for the same file if you want to assign it to multiple policies and not globally. Something like adding checkboxes to each policy so you can select more than one for an override would be awesome.
It would be nice if I could give a user the possibility to change it's scan schedule. At this moment I can only give a user full access to the Webroot Endpoint Interface or give a user no possibility to change anything. I don't want a user to be able to change all settings in the interface.