Webroot® Business Endpoint Protection
Welcome to the Endpoint Protection and management console Discussion Forum!
- 1,134 Topics
- 3,606 Replies
I’m running Webroot SecureAnywhere EndPoint Protection v126.96.36.199 I’ve been battling a strange issue where my whole OS becomes unresponsive. I get the “(Unresponsive)” message on all windows. Sometimes the screen goes black with only a mouse cursor movable. When it begins, the start menu stops working and I can’t start new applications. Task manager won’t open and CTRL+ALT+DEL doesn’t do anything. Any applications that were running before have a random chance to continue working or freeze. I can’t reboot. If I am able to issue the reboot command it never happens, likely because Windows can’t close all the hung windows. I thought it might be a hardware issue, maybe a failing HDD but I’ve ran numerous tests. All the tests tell me that nothing is wrong. I have been keeping Task Manager open all the time just to see what is going on. I’ve finally noticed a pattern. Webroot kicks up to 10% CPU usage when the event begins. After that, Webroot remains steady
Where did the Business Endpoint Protection forum go? Is this the beginning of the end? The product was absolutely filled with bugs and errors. It was obvious support wasn’t doing anything about the problem. Does anyone have any idea if OpenText was going to fix things or should we all start looking for something new (and a whole lot better)?
So I’m trying to set up 2FA for my Webroot console login. I plan on using an authenticator app, but I haven’t gotten far enough to actually make that happen because I can’t get that far in the process. I would like to know if I’m the only one who finds the “Security Question” portion of setting up 2FA on Webroot to be foolish and insecure. The problem is that before I can get to setting up my authenticator with Webroot, I have to choose answers to two “Security Questions”. Nothing new about security questions, right? You choose a question from those provided and put in your answer (usually something unique to the user’s life history). It’s a good way to avoid stolen passwords from allowing access to an account. It’s not foolproof - some bad actor could possibly know a user well enough to guess the answers - but it’s a fairly secure second-string method of verifying the users identity in the case of something like a lost password or other sensitive operation. However, Webroot’s executio
Just an FYI, A Business SecureAnywhere client had a noticeable increase in DNS requests coming from their network with no apparent cause. As a precaution I temporarily installed and ran MalwareBytes which detected Adware.FusionCore on one of the systems. This had gone undetected by WebRoot and Windows Defender.
I have an interesting issue, Our Point of Sale stations that utilize bar code scanners are returning skewed results that are running Webroot. The issue occurs in IE, Firefox and Chrome. I have disabled the plugin for webroot for all 3 browsers with the same result. Conversely POS stations running kaspersky do not have the same issue. The condition can reproduced readily on any POS station. Scanning to wordpad or note pad works fine so I know the hardware is ok. Our POS software is cloud based, but I am able to replicate the issue when scanning to google translate. I believe the issue is regarding mixed content. Any suggestions would be greatly appreciated.
Hi Webroot, For nearly 4 years you've been saying that 2FA is in the works, but it still hasn't been implemented (The security code isn't 2FA, it's just a second password). Have you released a timeline where your customers can expect to have 2FA security available?
I have webroot installed on my home computer and when I type in a word to search for my own web site (checking if it's above the fold) and when it comes up on the search results page there is a red exclamation icon beside my site's search results ... how can I assure you that my website is safe an make that icon disappear?
As of lately a majority of my endpoints don't accept agent commands, it says they either elapsed, executed (but is never executed on the endpoints) or not received. Sometimes it can take days or weeks for the endpoints to show executed even though they check in every day. Changing policy is instant. After a remote session and submit logs to Webroot, Webroot says there is no fix for this at this time. Does anyone else experience this issue?
Hello everyone, I recently noticed that running an agent command like 'Scan' or 'System Optimizer' from the GSM console ends up with a 'Not received yet' status forever. I tried on different devices, some having a firewall and proxy protecting them and some not secured. The commands are executed after a manual 'Refresh configuration' only on few of the devices I tested on. I think this has something to do with the latest version updates, since I did not have any issues before. Has someone experienced something similar? Thank you.
One of our computers has lost the ability to right-click on a file/folder and scan it. This option is no longer in the right-click menu options. It was there originally when the software was installed on the computer. It just vanished?! The scan settings policy enables right-click scanning in Windows explorer. And opening up the endpoint software settings does show this option as ticked. This is only happening on 1 of our computers. All the others are fine. The Win7 PC has been rebooted plenty of times, but has not fixed it. I have even tried uninstalled the software, and reinstalled, but this right-click scan option is still missing. Has anyone else seen this? And if so, how did you over-come it? It's not the end of the world, as we can still initiate a custom scan in the endpoint software itself. It's just annoying. Thanks.
I have a lot of "orphan" endpoints I need to change the keycode on. I have access to then via a RMM package but need the WRSA commandline parameter to change the keycode. For that matter it would be really nice to have a list of all wrsa command line options.....
Looking through the updates to the GSM this morning and I noticed that the Primary Browser report has basically no clue what browser is the primary one on my endpoints. All, but two of my endpoints are using IE as their primary browser based on the report. I know this to be incorrect because I set the primary browser to Firefox on almost all my endpoints. There's one that requires IE as the primary, but this is due to a software on it and it's a server that only I use. I even have Firefox installed on it and use it for anything other than that software and it can't be set as the primary due to the software. OS doesn't appear to matter. I've got Windows XP through Windows 10 desktops and Windows Server 2003 through Windows Server 2012 R2 servers. The reporting is reading incorrectly on all these OSs. Apparently there is a bug in the software that is misreading this information from the endpoints. Just thought you might want to fix the issue.
A customer has requested Webroot access in order to view the devices for their site. We have created access, and they can only see the devices for their site but they can see all the global policies for our other customers. How do we restrict which policies they can see? Below are detail description of issue. -Partner has given "site only access" to one of the test user "XXXX" but user is able to see global policies of the other sites too. -Checked and found "Include global policy" is checked while creating Webroot site. -Please confirm is there any functionality by using which we can give access to the user for an only particular site and restrict global policies of the other sites.
Through testing some "unknown to Webroot (or any other AV)" malware, I feel WebRoot may be insufficient protection for my clients. By allowing untrusted code to run, it seems a lot of ransomware can get through without a lot of difficulty (the first ransomware-as-a-service a colleague tried with Webroot was successful while other well known competing AVs were able to block it with their own heuristics. Webroots heuristics were turned to max also. While it might be possible to do rollback, WebRoot doesn't do rollback on network drives and unknown applications are allowed access to these resources. Since this is often deployed as a business AV solution, this is unacceptable. Is there functionality in WebRoot currently, or that could be easily added to straight up block execution of unknown executables (as a configurable option of course) -- ideally whitelisting anything SIGNED by a trusted entity (eg. Microsoft)? Or is there a way I can already do this? I know that I could u
[b]Questions:[/b] [list] [*]How long should an Endpoint continue to show in a Site once the 'Command Log' shows the [i]Change Keycode[/i] command as "Executed"? [*]Should a [i]Change Keycode[/i] across GSMs (instead of between Sites in the same GSM) be expected to take notably longer? [*]Does the Endpoint's host computer need to be restarted for the Change Keycode command to finish? [/list] [b][u]Background[/u][/b][spoiler]In the past I've had problems using the [i]Change Keycode[/i] command to move WRSA Endpoints between Sites within the same GSM. Just didn't seem reliable. It's been a while since I've last used that command as it is, but now we're attempting to transfer a customer's WRSA Endpoints to their new MSP's GSM (at their request). Webroot Support confirmed that doing this is possible and officially recommended using the [i]Change Keycode[/i] command over a uninstall-reboot-reinstall of the Endpoint. That Site's 'Command Log' shows the command as "Executed" for many of tho
Hi, in the scheduled report of the installation report, in my opinion the management fails to list the name of the hosts belonging to the sites that are installed. The installation display is there and the host / site name is displayed. This feature is missing from the scheduled report. What do you think? for me it's an urgent change to do! The same list is also missing for all deactivated host sites, so they can be deleted.
The Sonicwall Antivirus is suddenly identiifying Webroot dowloads as Trojans. Can someone from Webroot please contact Sonicwall to correct this? From what I have read, Java updates and Sophos are also being flagged as Trojans. They are both working with Sonicwall to correct the situation. Can someone from Webroot do the same since it may not be the same signature that is blocking webroot. It does not seem to prevent webroot from working, but it does prevent version updates and fresh installs. Thanks for looking into this.
Already have an account? Login
Login to the community
No account yet? Create an account