Webroot® Business Endpoint Protection
Welcome to the Endpoint Protection and management console Discussion Forum!
- 1,135 Topics
- 3,657 Replies
I have never, in my life, seen a bigger waster of time and money. This software is a bottomless pit of pain and frustration with no end in sight. The GSM can’t contact the endpoint. Commands expire. The endpoint can’t contact the GSM so you can’t uninstall it because it things it is managed. Excludes aren’t excluded. it won’t register as the the “on” virus in Security Center so both Windows Defender and Webroot are active. It won’t install or uninstall properly. It is hit and miss if it puts itself in Add/Remove programs. The latest update makes the WRSVC service fail to start because it is improperly digitally signed. Endpoints show up in the wrong site It thinks programs are harmful that are totally safe. Now you can’t even end the numbering system in the post! Can’t you do anything right Webroot! Do not use this program! It is total junk!
HiWorking for an MSP and I am noticing an emerging issue with the identity shield causing Chrome to hang or launch with a blank screen. The circumstances are: Windows 10 2004 January 2021 Windows 10 CU installed Webroot installed and up to date Nvidia graphics card (no specific model) Chrome installed and up to dateIf all of these are fulfilled except for the January CU, the problem does not occur. It also does not seem to occur on machines without Nvidia graphics. I have seen 10 instances of this since yesterday, and was able to replicate the issue on brand new machines.The workaround is to set the application protection for the chrome.exe to allow rather than protect.
So my friend was trying to get a webroot subscription he had showed me this “free webroot cracked” lol just another key basically but he’s afraid now because he found out that you can basically do things to people’s computer from “endpoint” as its called, what can he do to prevent his computer from being damaged?Didn’t really know where to post thisAlso I told him to try uninstalling the webroot, so they cant run anything to the computer (I think)
Hi In Programmatic Access settings within Outlook 2013's Trust Centre settings on our Terminal Servers, the Antivirus status for Webroot is showing as "Unavailable: This version of Windows does not support antivirus detection. Currently, when one of our users goes to email from MYOB they are prompted for each separate email to either allow or deny MYOB to send the email thorugh Outlook. They use RDS on Windows Server 2008 R2 to access MYOB. Is there a way to get Microsoft Outlook to detect the AV status correctly with Webroot to prevent the "Allow or deny" prompt? Kind regards
Hello I use policy for my sites. Some times technicians have to desactivate or remove Webroot in computers. But they have not access in Internet so they cannot use the administration console. But, the users must not delete or desactivate Webroot. Is it possible to have a password for the desactivation or removal of Webroot Endpoint directly on the computer ? In resume, I want to have the possibility to remove or desactivate Webroot Endpoint directly on computers (for example with the panel control or line commands), but I want that the users cannot to delete or remove the antivirus. Regards,
Per [user=12807][/user] 's suggestion in [url=https://community.webroot.com/t5/Business-Discussions/What-sort-of-bandwidth-do-you-have-at-work/m-p/88446#M150]this thread[/url], I'm breaking this out into a separate discussion. What's the worst mess you've inherited from the former IT person? For me I think it was a donor "database" that happened to just be a word document filled with the contact info of all their donors. To make matters worse, there wasn't much standardization to the layout. I spend about a week writing a Perl script to try and parse all the data and at least put it in an Excel spreadsheet.
I have a PC that I set the polling interval for 15 minutes. It updates the Last Seen every 15 minutes. I then issue an agent command (Scan). The command sits in the Recent & Outstanding Commands window with a status of "Not yet received". No matter the polling interval OR if I go to the PC and right-click the webroot icon and select "Refresh configuration". The agent command never gets run. Tech Support has not been able to help me with this. Any ideas from the community?
Hey Everybody, I've had a client wipe their system to factory defaults, thereby removing the WSA agent from her system. I've since reconfigured everything and reinstalled the agent onto the system. Problem now is that there are two systems with the identical name being reported in the console. How do I remove the old endpoint as I've hit deactivate, but there's no agent to remove. Client is concerned about being double billed for the one endpoint. Thanks John Hart Nerds On Site email@example.com
Within the console I deactivated a Server and Client PC to trouble shoot issues. Both have been reactivated and had the installer run. Both show Webroot running in the tray and services but neither have Webroot listed in "Programs and Features". I have uninstalled from the console and reinstalled. Have disabled and reenabled show in Programs and Features within the policy but haven't been successful in getting the program listed. I need the program listed for software inventory scanning. Server 2008 R2 and Win 7, WR Ver 188.8.131.52. Thanks for your help, Jetson
Hi, When we are troubleshooting or just being curious, we sometimes want to know where an infected file is/was located. In the alerts from Webroot, the locations are often described using "percentage-sign named folders", such as %restore%, %cache%, %temp%, %appdata% and ?: In most cases, it's straightforward to translate these names into real folder names (some are even known system variables in Windows), but at other times it's not easy at all to figure out. For example, is %cache% pointing to the 'Temporary Internet Files' folder used by Internet Explorer (or Edge), and/or would the name be any different if the user had been using Firefox or Chrome to download the mailicous file? And which drive is the ?: drive Is there a complete list of the abbreviated folder names available somewhere? Thanks and best regards, Erik
Hi all. I need to start remotely an application, so I figured that I could do this using the "Run a DOS Command" from the Agent commands. Well, I run the command I want but nothing happens to the endpoint I target. For testing purposes, I tried to run the command "notepad.exe". Although the command is shown as executed, the notepad never opened at the endpoint that I sent the command. Same happens even if I put the full path of the executable. What I am doing wrong? How can I start an application remotely? Thank you in advance.
Ok, fiddling a bit with a few installs on the way to rollouts of Webroot Endpoint. What I would like to know is how do I prevent an end user from uninstalling webroot? I just got off an end users machine who uninstalled the other AV bloatware because it slowed his machine down too much. Not an uncommon sentiment, but then I installed webroot on one of my machines and I was able to uninstall it from add/remove programs without a password (the type the above letters verification code was tricky though :) ), and even if I remove the Webroot item from add/remove programs the end user can still go and delete the webroot executable from the program files(x86)webroot directory. Many of my end users are local admins on their machines, so I need an uninstall password on the app. Is this built in somewhere and I am missing it? Some other way to avoid users doing this? If the executable is deleted does the web console push it back out? Am I missing something? Thanks, Wayne&nb
Check it out here: [url=https://twitter.com/LabTechSoftware/status/660095089264431104]https://twitter.com/LabTechSoftware/status/660095089264431104[/url] Who else is a Labtech users? Let us know what you think of the integration.
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?