Got a Question?
Have a product question? Start here!
- 520 Topics
- 2,143 Replies
[b]Important update on new release for customers operating Webroot Secure Anywhere on Terminal Servers in a virtualized environment[/b] Issued: 22nd November 2016 [b]Overview of known issue:[/b] Webroot has been actively tracking and monitoring an issue that affects some customers operating Terminal Servers in a virtualized environment. During a fault condition, a Winlogin 4005 error occurs where an RDS user is unable to connect to the RDS server, and the event logs display a message indicating that Winlogin has stopped responding. Interim advice issued by Webroot engineering teams recommended setting the WSAB Self-Protection function to ‘Minimum’ on all Server Policies as this significantly reduced the frequency of Winlogin 4005 errors in most cases. [b]Update:[/b] Further to that advice, Webroot engineering teams developed a new, stabilizing agent release to address causes of the 4005 error and made this agent available to a select group of customers to t
[b]Important update message for customers operating Webroot Secure Anywhere on Terminal Servers in a virtualized environment[/b] Issued: 17th November 2016 [b]Overview of known issue:[/b] Webroot has been actively tracking and monitoring an issue that affects some customers operating Terminal Servers in a virtualized environment. During a fault condition, a Winlogin 4005 error occurs where an RDS user is unable to connect to the RDS server, and the event logs display a message indicating that Winlogin has stopped responding. [b]Update: [/b] Interim advice issued by Webroot engineering teams recommended setting the WSAB Self-Protection function to ‘Minimum’ on all Server Policies as this significantly reduced the frequency of Winlogin 4005 errors in most cases. Webroot engineering teams have developed a [b]fix[/b] which is currently undergoing regression and environment testing. The engineering and QA teams continue to treat this as their highest priority and are predicting thi
Hi, Has Webroot found a resolution to the problem of duplicate entries in the GSM console when agent systems upgrade to Windows 10? We're constantly having to deal with going into the GSM and look for and deactivate the older duplicate (the windows 7/8 system) when they are upgraded to 10 in order to prevent being billed extra for endpoint usage. Tsk Tsk... John
All I see is a list of MD5 hashes and unless I drill down I cannot see the file name. If I look at my global overrides, there are about 900 entries of files that I have labelled as good. A large number of these were probably considered unknown in the cloud when I added them. Presumably, some of them have become "known good" since then. It seems like I should be able to look at the list of file namess and what their current cloud status. Then I could remove unneccessary override from my whitelist. Better yet, maybe pruning of the override list could be automatic. It also seems confusing that override can be global or attached to a site or policy. Many things I whitelist are at the global level, but it does not seem that I can tell if there are policy-level overrides for the same file. Am I missing something that would allow me to effectively manage these lists?
Hi, I am sure I've read about Webroot being the only one AV which has the possibility to revert files to previous versions (especially in case of *crypt* ransomware infection). But I have never seen such an option anywhere inside WRSA. I know exactly what Previous Versions under Windows OS are. And I know how Windows works. But I was hoping Webroot has some ADDITIONAL MECHANISM to be able to revert to previous version, regardless of Windows native file history. Did I get it wrong about Webroot possibilites? Or am I missing something? Thanks!
Hello All, We have been using webroot now for a few months and I have been exploring some of the features that webroot has and I stumbled across the download and run file feature and I was testing it but for some reason I am not able to get it to work. Basically I am trying to run a .msi installer and its not working. Does anyone know which directory the file gets stored when its downloaded? What is the correct syntax that should be used? Any help is greatly appreciated
We are deploying Webroot to our clients and have been running into an issue with users unable to login at a certain point. After testing we found it has to do with Webroot being installed on there but we cant figure out what is causing the issue and we've had to remove Webroot. This seems to only be affecting Server 2008 R2 environments.
The printers connect successfully, however when they try to print to them the jobs seem to disappear. Attempting to print again, the printer shows offline in the session even though the Windows 7 OS can communicate with the printer fine. We disabled all functionality with Webroot and the issue persists, however when we flat out uninstall it printing from Citrix works as expected. We have added exclusions for the spooler folder and the Citrix installation folder with no luck. Any advice or feedback is appreciated as this is holding up a deployment of 2000 seats. Edited update: The printers are connected via network using a mixture of both TCP/IP ports and HP Proprietary ports.
I was looking into the reports and was wondering a couple things: 1. Can we generate non-graph reports? Something with text detailing type of threat discovered, when it was identified and when it was removed? 2. Adding a company logo to the title screen. 3. Modifying the format displayed for current reports. ie: instead of showing 1 report per page possibly show 4 reports per page? Regards, Matt
How to have Webroot to do a FULL scan on all endpoints in the Management Console? (Sality infection)
We have Sality infections spreaded over 350+ endpoints. Webroot support simply suggested to re-image endpoints - which is obviously the latest thing we want to do. Some endpoints (the file servers and some clients) we cleaned with ESET/Kaspersky boot CDs. ESET/Kaspersky found 100-600 infected files per endpoint, one files server had 68.000+ infected files that Webroot did not find! but still the company cannot work as infected endpoints reinfect file shares, and then from file shares even cleaned PCs got reinfected again. We use Webroot on the servers, too, and it does not stop reinfection of shared folders! We think maybe we should do a full scan with Webroot on all endpoints, but we cannot see any agent commandfor that in the console. How could we command Webroot to do a FULL scan on all endpoints in the Management Console? Any other idea how to get rid of Sality?
As an MSP I need to send a monthly report of all the cool stuff we do for clients each month that would otherwise go unseen. After all if we do our job right, the client never hears from us, except when we send the bill or otherwise proactively communicate with them. So the threat history report is great because it will show everything we protected them from each month when we send it with the bill. But obviously it defeats the purpose when an MSP tool requires manual intervention every billing cycle. Is there a way to schedule the report to go out to a client at a specified day each month? Thanks for any help and ideas! Regards, Jason Wintensive Technologies
Topic says it all. I've got about $50,000 in software here that I can't update because your AV software blocks it. This started about 2 or 3 weeks ago, maybe a little more. It's also deleting the plugins that I have for Autodesk Inventor. Now, if I could get the IT people to let me turn it off temporarily, that'd solve the problem with the software updates ... but it wouldn't help with stopping your software from killing off my plugins. This is a pretty massive fail, Webroot. Are you guys partnered up with the makers of Solidworks or something?
Hi all, I may have overlooked somethign basic.... I want to email a list of hosts protected by Webroot to my client (he doesn't want to log into the console). Is it possible to generate a report of hosts with webroot installed, and export it to pdf of csv or somethign similar? I had a look in the reports tab but couldn't find a way of doing it. Cheers, Simon
Can i create a MSI installation file with both productkey and group name? i know about the command lines but i want one file easy to install for clients that puts them in the right group at ounce. thanks in advance Mattias
We have a potential customer who would like to know what other customers' experiences have been when deploying Webroot SecureAnywhere Endpoint protection in a Windows Server 2012 environment. If anyone has done so, we would love to hear from you. Thanks!
Hi As everyone knows Microsoft dscontinues support for Win XP in April 2014. Is Windows XP going to be listed in Platforms Supported by Webroot after April 2014? I also wonder what will be the reaction of other AV vendors. It seems to me that's extremely risky for AV product to officialy support OS which is no longer patched.
Hey guys I was hoping someone could possibly help me out. Now I wont lie when I say I'm really liking this stuff, but the only problem IM having is deploying with GPO. It shouldn't be this hard but for some reason its not working at all. I even did a little test and it went like this I put the folder on the root of C of a test server, shared it out like I was supposed to in the youtube vid they have. I put both firefox, AND webroot in there, so both would have the same permissions. I then set the GPOs up the exact same, nothing was different. Then I moved it to the OU where it is going to end up, i did a gpupdate on the server, then on my computer, then logged off and back on. when i logged back on, firefox was there, webroot was not? Why is webroot not installing at all i keep getting the same thing when i do gpresult -r. The following GPOs were not applied because they were filtered out Local Group Policy Filtering: Not Applied (Empty) and like I said b
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.