ConnectWise Automate Integration
Designed to discuss Webroot plugin for CW Manage features, general questions, and ideas.
- 14 Topics
- 35 Replies
I find myself answering this question regularly on the LTG forums so I thought I'd share it here too. The plugin provided script to uninstall webroot always fails. The script will download the latest MSI and attempts to uninstall webroot using that. This (almost) always fails because it was (almost) never installed with the latest version. There is a further issue showing the error message which makes troubleshooting this more difficult. Only shows "T". After much digging you'll find its short for "This command is only available for products that are installed" and it actually performs nothing. The fix? CWA runs as the SYSTEM account. If you send [b]c:program fileswebrootwrsa.exe -uninstall[/b] from CWA ([i]as shell[/i] in your script) there won't be any prompts and webroot should be gone within 5 to 10 seconds. If this still fails then webroot had further issues and will need to be ripped out manually. Be sure to clear that wrdata folder (at [b]c:programda
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?
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.
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.
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
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. 188.8.131.52Webroot SecureAnywhere with Unity v. 184.108.40.206
We are very pleased to announce public beta availability of our next integration with ConnectWise Automate! Version 3.0 brings expanded capabilities. We have focused on a new, streamlined user interface with simplified and more robust connectivity to Webroot via our Unity API. Based heavily on partner feedback, we believe these new features will significantly streamline the management of Webroot within the MSP environment. Below please find important information for your beta participation— [list] [*][b]Beta Access[/b] Please reply to this community forum if you are interested in the beta. We will follow-up right away with full details on how to access the beta materials. [/list][list] [*][b]For all beta questions, feedback, and technical support please contact: [/b][url=mailto:CWBeta@webroot.com]CWBeta@webroot.com[/url][/list] Thank you very much for your willingness to participate in our beta program!
The ConnectWise Partner community area is designed for ConnectWise Automate and Manage administrators who also use Webroot. With the integration solutions available between Automate and Manage, this community page will be a location where partners can ask Webroot experts and MSP collegues questions, collaborate on best practices and share collaborative information. Please feel free to post a new topic and get a timely response. Regards, PS... Introduce yourself on this Welcome thread and let us know if there's anything specific the Webroot team can provide help and support.
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?
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, V220.127.116.11 works fine when trying to access the plugin menu.
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.