Webroot® Business Endpoint Protection
Welcome to the Endpoint Protection and management console Discussion Forum!
- 1,134 Topics
- 3,648 Replies
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.
Hello guys,Is there anyone here who knows how to change policy settings via cellphone, sometimes I'm in a condition where I can't open my laptop, but I have to change the policy settings, whereas via cellphone I can only create a new policy without making changes to it, even I can't change the user endpoint policy. Thanks
How to install using GPOKnowledge Base
[b]This solution addresses Webroot SecureAnywhere Business – Endpoint Protection[/b] To install SecureAnywhere using GPO, you should have experience with Microsoft’s Active Directory and the GPO editor. You can also watch a video on how to use GPO at [url=https://www.youtube.com/watch?v=raP0jQHyFYE]How to Deploy Using Group Policy - SecureAnywhere Business[/url]. [b]To install SecureAnywhere using GPO:[/b] [list=1] [*]From the following location, download the SecureAnywhere MSI installer to a network share:[url=http://anywhere.webrootcloudav.com/zerol/wsasme.msi]http://anywhere.webrootcloudav.com/zerol/wsasme.msi[/url] Downloading the file makes it accessible to all endpoints on which you will deploy SecureAnywhere. [*]Go to the server that is the domain controller for the deployment group. [*]Open the GPO editor on the domain controller and create a policy for the deployment group. [*]Assign SecureAnywhere to all endpoints that belong to the Organizational Unit where t
Downloading and running the installerKnowledge Base
[b]This solution addresses Webroot SecureAnywhere Business – Endpoint Protection[/b] You can deploy the SecureAnywhere installer file using one of these methods: [list] [*]Install SecureAnywhere on each endpoint. [*]Send emails to end users, so they can install the software by clicking on the link provided in the email template. [*]Rename the executable file using your keycode. This method is useful if you plan to use your own deployment tool and if you prefer not to use MSI commands to run the installation in the background. [*]Use additional commands with the executable file to deploy it in the background. [*]Use command-line options with the installer to deploy to endpoints that are behind a proxy server. [/list][b]To use the SecureAnywhere installer:[/b] 1. On the endpoint, download the SecureAnywhere installer file. The installer file is available from the [b]Resources [/b]tab or by clicking this link: [url=http://anywhere.webrootcloudav.com/zerol
How to submit a ticket to Business SupportKnowledge Base
[b]This solution addresses Webroot SecureAnywhere Business – Endpoint Protection [/b] To submit a support ticket for Webroot SecureAnywhere Business Endpoint Protection, [url=https://mysupport.webrootanywhere.com/supportwelcome.aspx?SOURCE=ENTERPRISEWSA]click here[/url]. If prompted, log into your account. If you prefer to speak with a support representative by phone, [url=https://www.webroot.com/us/en/business/support/contact]click here[/url] for a list of our telephone numbers.
[b]This solution addresses Webroot SecureAnywhere Business – Endpoint Protection[/b] The first time you add endpoints to SecureAnywhere Endpoint Protection, they are assigned to the Default group. You can then move endpoints to the appropriate groups. [b]To move endpoints to another group:[/b] [list=1] [*]Click the [b]Group Management[/b] tab. [*]From the [b]Groups [/b]panel on the left, select the group that contains the endpoints you want to move.[b]Note[/b]: For this procedure you must select a specific group, not [b]All Endpoints[/b]. [*]From the [b]Endpoints[/b] panel on the right, select one or more endpoints.[b][i]Tip[/i][/b]: You can select all endpoints within the selected group by clicking the [b]Hostname [/b]checkbox at the top of the list (first column). [*]Click [b]Move endpoints to another group[/b] from the command bar.[b]Note[/b]: If the group has more than one page of endpoints, the dialog prompts you to ap
I just enabled a feature of our email service that tells me when incoming emails were not sent via TLS. It is telling me that Infection Alert messages from firstname.lastname@example.org are not utilizing TLS. This is probably minor, but it could constitute a security risk in some cases.
I just wanted to share my own recent experience with uninstalling Webroot Business Endpoint Protection which has received a number of questions over the years and hopefully help someone out. This is the process that I’ve had success with and does require that your agents are checking into the Webroot console and your RMM tool (mine is ConnectWise Automate)Adjust your policies so that agents check in as frequently as possible Tag the target agent(s) with the “unmanaged” policy. For off-boarding, etc., I use a separate group with the Unmanaged policy applied and just move the agents into that group and apply the new policy. Allow them plenty of time to check in and get the policy update. Issue the Uninstall Agent command from the console. We’ve had about a 90% or so success rate with this command. Some will report that the command has executed, but continue to check in. For instances where the console uninstall doesn’t seem to take, we then jump to our RMM tool for help. I stopped using
Hi all,I’ve ended up here as I’m not quite sure where else to go for dialog. I'm not sure if I'm correct or incorrect in my approach. I'm interested in the greater opinion!Where I work, we have a fairly sensitive IT manager, who on seeing a Webroot Alert will shout 'fire fire fire' and shut everything and everyone down until a full investigation has been undertaken. This gets fairly wearing as every alert generates a lot of work. (Usually to no benefit) He has a particular urgency for Trojan notifications.Now, while I appreciate the sentiment, I can't help be get ever frustrated at this approach. I am under the (correct/incorrect?) impression that an alert from Webroot is a GOOD thing and that nothing has been executed/infected. Although I do agree that a quiet investigation is probably necessary to ensure that an infection hasn't taken hold.So my question/discussion point is this - if Webroot highlights an 'infection', is the detection done at a safe point i.e. pre execution, or
Already have an account? Login
Login to the community
No account yet? Create an account