Webroot Integration Discussions
Recently updated Webroot Solution last night in one of our Automate Servers as we have two, but our first instance now no longer displays the plugin menu popup when accessed from Tools in Automate.Has the update broken this?As on our Server 2, V184.108.40.206 works fine when trying to access the plugin menu.
The Kaseya RMM-Webroot plugin uses some Kaseya core files to function. With the latest VSA upgrade to 220.127.116.1131 and higher, these files have been modified for improved security and this may interfere with the plugin functionality. You may see a “Session Expired” error on your plugin pages.To ensure compatibility of the plugin with the latest VSA versions, you may need to perform a series of steps to replace the old dll files with the latest ones. Please refer to the attached document and follow the steps in there to resolve the issues based on your plugin version,
Hey Folks, I am in the middle of multiple Webroot issues where VSA plugin stopped working after the latest VSA upgrade. This issue started to happen on On-prem partners and surprisingly, when I asked for support from Webroot, they simply said, we don’t have any solution now. Just leave the ticket open and we will update you whenever we will have an update for you. Like really, They put us on risk and now no support. Is there anyone in community who can help me out from here ?
I enter all of the necessary API Authentication info and successfully authenticate. It shows “Good Connection”. I go to Clients and none of them show. Back to Settings and can see the API Authentication has disconnected. I had this same issue with the Sophos plugin which was fixed by adding the Automate User to the Sophos Groups (Classes) that were created when the Plugin was installed. There are no groups for the Webroot plugin. I have given my account access to the Webroot plugin within permissions. I’ve re-authenticated to Automate with the new permissions, but it continues to behave the same. What do I need to do to keep the Webroot API connected within the Plugin so that I can work with the tenants?
Hello Everyone, I work for an MSP that uses Connectwise for our RMM. We used to have tickets generated to Manage with HMN priority from Webroot whenever a threat was detected. Our last Webroot threat alert received in an automated fashion was the end of May. We had it setup with the Email connector so I’m guessing we had things set within Webroot to email our support@ email which then creates the ticket. Can any of you assist me in getting that working again? Is it part of the Plugin within Automate or within Webroot itself? Thank you for any assistance you can provide.
Hello,I work for an MSP that uses Connectwise Automate and the Webroot plugin. Recently we did some security hardening of our network and lost some functionality. Poll Management Console isn’t pulling any data, Auto Deployment isn’t working, and we can’t access the my.webrootanywhere.com site in the My Webroot Anywhere tab. Is there a list of what servers need to be whitelisted on our network to be able to allow communications between our Automate server and the Webroot SecureAnywhere servers? We’re running:Webroot Plugin for LabTech Software v. 18.104.22.168Webroot SecureAnywhere with Unity v. 22.214.171.124
Out now is the latest OnPrem VSA Webroot Integration. Highlights of new features include: Customer Support Diagnostics command - now you can send logs to support directly from the integration. Alerts - Now with advanced options to each type of alert. New abilities to customize how you often you get the alerts, when to resend an alert and much more. Navigation enhancements to keep your filters in place when switching modules. Please see all the information about what is in v2.6 at this link. To obtain the new version, please click here.
[b]New Feature[/b] [b] [/b] [list] [*]Added extensive Alert Setting features with 4 different Alerts and 4 actions, see “Integrated Alarm Parameters with Kaseya Alert Actions” in the updated manual below for more details. [/list] [b]Enhancements[/b] [list] [*]Added persistent Deployment and Status Dashboard > Machine ID, Group and View values. [*]Added persistent Deployment and Status Dashboard > Rows per page. [*]Added Webroot Settings > Rows per page. [*]Made a number of minor UI changes [/list] [b]Bug Fixes[/b] [list] [*]Resolved a number of bugs [/list] Users can get the new build through the Kaseya Automation Exchange [url=https://automationexchange.kaseya.com/products/478]here[/url]
We are aware that the ConnectWise Automate Plugin may be unavailable for some users of version 3.x. Our teams are working around the clock to understand the cause and provide a solution. I’ll share additional information here as it becomes available. Thanks for your patience. Nick G
I’m very pleased to announce the availability of the ConnectWise Automate Plugin version 126.96.36.199 via the ConnectWise Solution Center. This is primarily a maintenance release and includes important optimizations round Unity API utilization. This version has 5 enhancements and 34 bug fixes. We recommend users upgrade to this version as soon as possible. I will be at the IT Nation Explore next week. If you have any suggestions or question about the plugin come find me on the stand.
I notice the on-premise version of webroot for Kaseya has been updated twice in recent month.s however, there has been no announcement made here. How are we to know when new versions are released, if no announcement is made? I only know by occasionally searching the Kaseya Automation Exchange and noting the release date. It's really tedious to have to constantly go and search every week or so, in the hope that a new version may be released. Also, there is no changelog or release notes provided. How are we to know what has changed or been fixed in each release? Really, someone needs to be doing a better job of announcing to the Webroot community when new versions are released, and what the changes are.
We have recently onboarded a client that had Webroot prior to us on SOME of their workstations. No one seems to know where the licenses came from previously (prior IT provider or if they were a direct purchase) or how to access the console to enable us to cleanly uninstall and start from scratch. We've deployed Automate along with the latest plugin and it has correctly installed Webroot on the workstations that didn't already have it (from before we were involved). Those machines show correctly in our console. However, short of going through the computer list one by one I'm trying to find a way to determine the workstations that have the client's previous licensing installed so we can move over to our account. Is there a reg key I can use to determine which are installed using our base key or something similar? Could this redeployment functionality be added to the Plugin in the future? I'm sure the is a pretty common scenario.
Okay, I can't be sure of all monitors here, but there are several Connectwise Automate internal monitors created specifically by the Webroot plugin. They are designated "Webroot 3 <monitor name>". The Webroot 3 Stale Agents monitor, as I understand it, is supposed to monitor for out of date definitions. We do get alerts from this monitor, which is listed as running every hour. However, I have quite a few instances (I can't say all, but I've confirmed it today that it is happening) where the agents resolve (AV definitions up-to-date) and the alert itself never resolves, but stays open. This causes a lot of checking of these alerts only to find there is only a problem perhaps 20% of the time (the rest of the time, it has resolved itself), which wastes a lot of time. Is anyone else experiencing this issue with this Webroot 3 monitor, or any of the other ones?
Our initial integration into the Cloud VSA structure is now available. This release will build the foundation of more features and settings to come. Version 1.0 plugin is provided with the following major features: [b]Deployment Management[/b] Manual agent Installation Manual agent Uninstallation Webroot site keycode management [b]Combined deployment & status dashboard[/b] Powerful search Agent Installation/Uninstallation status Kaseya Live Connect support [b]Extensive agent info[/b] Protection status Scan status Detection status General agent status License status
You can get the new integration for your OnPrem VSA here: [url=https://automationexchange.kaseya.com/products/298]https://automationexchange.kaseya.com/products/298[/url] Key Feature Enhancements: Added the ability to assign keycodes, auto install and adoption to all Kaseya Group Levels Added exclusion rules to Install, Auto-Install, and Adoption Added the ability to inform a plugin user a new version is available Removal of GI dependencies Key Prerequisites: Microsoft SQL Server 2012 (SP3 Recommended)
[img]https://d1qy7qyune0vt1.cloudfront.net/webroot-en/attachment/33758i9D3C639AB6908F39.jpg[/img] Join us for the premier IT management event of 2018 - [b]Kaseya Connect 2018[/b]! Webroot is a Gold sponsor for this event, which will be packed with opportunities to gain actionable insights, learn best practices, and network with your peers. Are you going to be there? If so, we'd love to meet up with you! Date: May 8-10, 2018, 2018 | Las Vegas, Nevada Location: Mandalay Bay Resort and Casino Las Vegas, Nevada Register: [url=https://kaseyaconnect.com/]https://kaseyaconnect.com/[/url]
We get a limited data set from Webroot into BrightGauge via a Continuum API Integration. Is there plans to release a standalone that we could use for interacting with the Webroot Console directly and create gauges that would show agents with active infections? We like to use BrightGauge as we way to see any items we need to actively work on as they will get more attention then something in a portal or a ticket that may get caught by the wayside.
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.