![]() I recently upgraded my ISP from Coax to Fiber, but I was not aware of CGNAT and it killed a lot of my stuff i had port forwarding mainly plex. Home Network Puzzle help needed Networking.With a Webroot tech a separate policy was created for servers, and that, of course was applied. Good chance I will convince the user of that extension's usefulness and put it back at some point, but it's nice to see how easily granular changes can be made at the individual machine level, or group level, if needed.Īnd the servers are now protected by Webroot as well. Webroot then removed the extension from that user's browsers. As an exercise, I copied the Webroot policy given to all workstations, removed the web threat extension, and moved their machine to that new policy. I explained that it's a feature, not a bug. ONE user decided that they were put off by this result. I hope to report back soon with continuing news.ģ days in: When doing a Google search, the Webroot web threat extension puts a green circle with white checkmark next to each search result if it passes their threat scan, with a different symbols if it doesn't pass. Other than that, I've contacted support (VERY responsive!) with some minor questions, and requested some interface changes that would make things more clear from a management POV, but nothing that would affect the client's functionality. ![]() After running just those (and no optional updates), the Webroot client installed right away on that one too.Īnd: all of this installation was done remotely via Splashtop Business access. ![]() That one was used for a single task, and had a bunch of "Important" (per Microsoft) updates pending for a couple of years. The Webroot client installed right away on every Windows 7 and 10 PC, no matter the version and update level, except for just one Windows 7 machine. Over 40 workstations are now installed with Webroot - Endpoint Protection + DNS Protection. I guess it's PFM (pure-freakin' magic).Īs I began installing the clients, I sent out a group email about the Webroot browser web threat extension, in case anyone had issues with that, and again, no issues reported. I don't know just how they do this, but definitions and signatures are all in the cloud, so they are not downloaded to the client machines. Webroot says that reboots are not required after installation (yep, that's been my experience!), and that updates are totally automatic. It's now been 3 days, and not a single user has reported any issues. What then happens is that Webroot does a scan of the boot drive, and in about 6 to 20 minutes, the client shows up in the Webroot management console. The Webroot client took between 3 and 8 seconds to install (REALLY!!). All but 2 machines on the LAN boot from SSDs, which made the removal/reboot process that much faster The longest part of this was uninstall/reboot of the old product. In under 5 mins per workstation, I was able to remove the older product, reboot, and install the Webroot client. The next day, I spent about 45 minutes on a scheduled call with a Webroot tech, going over some of the finer points of the cloud interface and configuration settings, made some tweaks, and was able to begin client deployment of my Webroot trial. I signed up for a Webroot trial, and had a Webroot client running in 5 minutes. That product is, mind you, a respected product, but its complexity and lack of user-friendliness is beyond belief, at least to me.Īfter HOURS of support and attempted support with the vendor, and living through an apparent re-organization of that product's vendor, I threw in the towel and went to Webroot. I'm in the process of shedding another AV product that I could NEVER wrap my brain around. BTW Please find and read Neil Rubenking's PC Mag review of Webroot. ![]() ![]() Thanks, Spiceworks, for just being! Here's my way of giving something to the SW community: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |