light bulb

Did You Know?



New Idea

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.

Currently there is no way to see the size of the WRData folder on endpoints without remotely connecting to the computer.  We have over 100 endpoints and no way to know which are losing disk space due to excessive WRData folder size.

 

It would be great to have a report or a column in the portal which gave some idea as to the size of the WRData folder of each of the endpoints.

Status: Reviewed

Sure thing, I moved it for you.  What sizes are the WRData folder sizes getting to?  We are working on improving the removal of old data that is no longer needed, which might solve this issue for you.

PLEASE VOTE FOR MY IDEA!

 

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

Hi Support,

 

Could you add a feature that allows us to shutdown the agent for an optionnal amount of time?

- useful when troubleshooting.

this be also push from the MSP console oradd it to the policy per a template and we we switch an end point to use this policy, one can right click and select shutdown for 5 minutes or time intervals

 

Thanks

Andy

 

Status: Reviewed

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.  

 

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.  

As an RMM we transition a lot of people from other AV solutions to WebRoot.  As always this means uninstalling the old version of the other software.  Although we can do many of these via a command line utility using webroots AWESOME "Run a DOS command" advanced option it is still combersome to look up all the versions of software and issue multiple commands to do it.  A simple "Remove Competive AV Products" option would be Great!  Symantec for one, does NOT like to go quietly.  Just give is the option of treating it like all the other malware and "Clean" it from the PC.   This should be a fairly easy update and I'm sure a welcome one.

 

 

Status: Reviewed

While I agree this would be an awesome feature, it would require quite a bit of work on our part, and then we would also be held accountable if there was an issue arising from this.

 

As you said, some of the other programs are not uninstalled easily and I have found this to be true more often than not.

 

I have changed this to reviewed and will keep an eye on it.

Written on belhaf of customer:

Status: Reviewed
by Webroot Employee on ‎05-29-2015 04:17 AM

I tried to post a request for this feature here https://community.webroot.com/t5/Feature-Requests/idb-p/ent4, but it said I don't have sufficient privilegies to do that. I therefore post my request to you:

 

With Android 5, one gets the opportunity to create multiple user accounts in one's phone/tablet. User apps must be installed into each user account, which makes perfect sense. But this also means that each user must install Webroot mobile protection to ensure full protection for the device. This also means that one Android with two protected user accounts will use two licenses (for us who have the paid business version of Mobile protection) - and that is no good.

 

My request is that

 

a) Mobile protection detects if there are other user accounts, and prompts the user to protect the other accounts, and that this preferrably also works for temporary guest accounts; and

b) (most important) that all user accounts in one single device use the same Webroot license - this should be simple to accomplish since all user accounts in one device all use the same phone number, or Webroot could detect IMEI or something.

 

-m***.m***@b***.se

Status: Reviewed

This is an excellent idea!

 

Thank you for taking the time to write this up Kelly, you rock!

hi

 

i would like to request the option to export reports to pdf. currently csv is the only option. when preparing reports for senior management they prefer nice pretty graphical charts representing the data not lines from a spreadsheet! most other software packages that have reporting have pdf option as standard. the graphs are already there on the webroot dashboard so i don't think it should be too much of an ask to have export to pdf with graphs included as an option.

 

surely this is a simple request to implement and one that most if not all webroot users would benefit from?

 

please vote this request up to make it a reality.

 

cheers,

 

rory

Status: Reviewed

Virtural Environment Deployment

Status: Reviewed
by Moderator Moderator on ‎04-21-2015 09:08 AM

As a: Admin managing a Virtural Desktop Infastructure enviromnet.

I wish: I could deploy Webroot to the master image.

So that: I can more easily manage my endpoints. I don't have to clear out duplicate machines from my console every day/week. I have threat history for my virutial machines.

Background
Virtual Desktop Infrastructure (VDI) environments provision a machine from a master image every time it is booted. Any changes that are made to the machine are lost during this session. This produces hole in the management of Webroot. The only way to get Webroot protecting these machines is to have them install Webroot on boot of the machine be it though group policy or some other management utility.

Issue
First, every time the machine boots we are doing a learning scan of the machine. Second, we get multiple instances of the machine in the console every time the machine is booted; which causes the admin to go through the console and deactivate machines that have not been seen recently.

Workaround
Install Webroot on boot of the VM. Current deployment switches (-uniquedeivce or -clone) do not fix this. Admins can use the /group= deployment to force these machines into a group so that clearing out the extra instance is easier. More info on deployment can be found in the Deployment Document.

Actual Result
Currently installing Webroot on a VDI environment can only be done on boot of the machine. This causes a new instance of a machine in console every time a VDI machine boots.

Expected Result
Webroot should be deployable to the master image. And when booting a machine from that image Webroot should grab unique information about that machine instance in VDI to link it to a single instance in the console.

Proposed Fix
I believe the best way to tackle this is to create an install switch for VDI deployment. You would install to the master image with this switch. Then on every boot of the VM Webroot generates its Device MID and Instance MID information off of the combination of the Microsoft SID and hostname. I believe the SID is the same since the VDI loads the master image, then if we generate those MIDs based off the hostnames being booted from that image, every time it boots the MIDs will be the same. And the agent will report to the same instance in the console every time that VM boots from that master image.

Status: Reviewed

This is an excellent idea @JohnnyS!

You have my vote sir.

Idea Categories
Top Kudoed Authors