Place to see if the Web Threat Shield policy settings were set to Off.Įngineering and SE teams are working on remediation issues and I will chase to Should have done more to understand the potential impacts, and had a check in #Webroot chrome extension upgradeUpgrades we didn't focus enough on the issues the upgrade would raise. We were so taken with the significant security Jon - One of my Product Directors asked that I paste this response to you directly as he doesn't have a Spiceworks account (but has spoken at SpiceWorld previously and values this community). Let's just say they are getting some good feedback on what went wrong with this release communication. You're right that I'm not a developer, but thankfully I know who those people are so I can forward this stuff to them directly. It is pretty bad and makes us look incompetent when we only know about the WebShield being turned on, and the extensions installed, through the end-users. This is like Microsoft turning on the Clutter feature in O365 and then us getting a flood of calls from end-users asking where their emails went. But I agree with what Jon is saying.Ĭommunication or not (in which case there was not much of it) they should of left the web shield off by default. Not trying to make this into a rant thread - hence why I toned it down when I created this topic. I am still waiting for remediation steps from Webroot to remove the extensions, but it's pretty darn hard when Webroot refuses to acknowledge that the extensions should not have been installed for customers who had the Web Threat Shield set to OFF in the first place. #Webroot chrome extension updateMy recommendation is to have Webroot push out an update that checks for this setting, and, if OFF, removes all extensions, if they are installed. I strongly suggest that instead of deflecting bug reports and legitimate issues by championing new features that you instead attempt to provide solutions and not be afraid to acknowledge mistakes. If you're offering the option to not use the extensions, have some respect for your customer's decisions instead of treating us like children who don't know what we're doing. However, please do not patronize your customers by telling us what's good for us or what we want when you have no idea what our environment is like. I get that Webroot's Web Threat Shield has undergone some major improvements and has some nice new features. #Webroot chrome extension how toIt has been further aggravating that tech support went on to try to convince me of the merits of using the Web Threat Shield instead of addressing my issue on how to resolve the extension issue. #Webroot chrome extension softwareThe notion that software can periodically behave however it wants regardless of established administrator policies is extremely thoughtless and totally inappropriate for an enterprise environment. I don't understand why Webroot cannot own up to its mistake and instead tries to say that its software can do whatever it wants. I suggested to tech support that this was a bug, but they defensively responded that instead Webroot does not necessarily need to respect the settings we have explicitly set (such as, Web Threat Shield = OFF). The Web Threat Shield has ALWAYS been disabled in our environment, which should have prevented any aspect of the Web Threat Shield from being installed and activated in the first place. This has generated issues for us in the way of increased tech support tickets as well as a few other issues. #Webroot chrome extension installNow with the latest update, Webroot decided to clandestinely install browser extensions on multiple browsers across our network without any permission or notification to IT admins whatsoever, totally disregarding that we have always had the Web Threat Shield completely disabled. We have explicitly disabled the Web Threat Shield because it was causing major issues in the past. Could you perhaps forward this to someone who can read my rant and make a difference? Thank you kindly! I know you're the representative and not a developer, and thus know my frustration is not directed at you. Know that the team is aware and we're working on a solution as I type to make sure this doesn't happen again. As someone pointed out before, we did post on the community (as always) but unless you were subscribed to the thread, it looks like you didn't get a notification about the release. We had a discussion internally about how this update didn't get communicated via email. Hey everyone - Sorry about the lack of communication on this one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |