Protection That Works!!! Well most of the time and it’s less annoying than its virus protection competitors. Just do us a favor and don’t use AVG, Symantec, McAfee or default to Microsoft Defender. Their virus support does absolutely nothing to protect you from a ransomware attack.
ProTip! Read up on what Webroot has to say about protecting your environment against Ransomware attacks.
Further down this post…
- Sites vs Groups
- NOTE: Don’t setup group sites or groups before you deploy a good default policy.
- MSP Management (Good Housekeeping of Computers)
- Policy Making
MSPs “Managed Service Provider” vs Individual Organization Setup “Business”
Many small business cannot afford the expense of a Managed Service Providers that proactively monitors your environment. The down side of a break/fix or self management of your environment is that most companies aren’t on top of their IT game 24/7. Basally, MSPs are there so you don’t wake up to a compromised network because no one is monitoring the malware & virus support; and therefore nobody can work for the next day or week. Not to mention, the accounting team loves managing the cost of outsourced IT vs having individuals that employed in-house.
The are two different keycodes that are provided during your initial setup. One that came from the webroot reseller email…
Webroot Business Endpoint Protection 1 Year Parent – The Parent Key
and another that appears in the Webroot dashboard upon setup…
This is the child key
Should the keycodes be the same? What’s the difference?
To clarify, the keycode SA8AXXXXXXXXXXX is your GSM Parent Key which holds all the billing and licensing information. The keycode C95X-ENXX-83XX-XXXX-XXXX is a child site keycode which belongs to this parent, and this is the one that you use to deploy Webroot to the endpoints.
Child Sites (clients) of the Parent Key
The key is the unique identifier for each group or site.
Not a one-off business? ie it’s just your business your team is managing the business
You will need to convert your console to the MSP version. To do so, log into the console and select the “Settings” tab > “Advanced Settings” > EditConvert to Managed Service Provider Console > Convert
Webroot Console Interface – Global Site Manager
There’s the home version for virus support and then there’s managing a business or several businesses if you are an MSP.
Head to the “Endpoint Protection Console” once you complete the initial setup of Webroot Secure Anywhere. Please perform the steps below before proceeding to the Webroot Endpoint Protection Console.
IT Specialists have the same access as the default admin if they are given permission to all sites unless they are set to “view/read-only”.
Sites (or groups for a business ie San Diego and New York) and Policies
They are custom policies you can or recycle
This is a list of all policies available. We are in the site called “networkantics”. NetworkAntics has selected “recommended defaults” policy
ProTip! It is recommended you have an “on-boarding” site or group. Then move into specific department or business. This is particularly useful in MSP mode. Not so much in an under 100 user environment. The default group should be sufficient. Then move the items to the most appropriate group. ie San Diego, New York, etc
Groups or Sites worthy of Consideration
- Un-Managed (don’t inherent policy)
- San Diego
- New York (regional offices example or choose your client business name if a MSP)
Two types of Webroot Consoles – What do I have again?
1) Management console that have multiple sites (Managed Service Provider mode)
* parent key code
* Child Key code to identify site (client)
2) Single site (can’t add more than one site. This is an individual business who are not managed by a Managed Service Provider)
* C95X (reference the example above) site key code is for deployment
The key is the unique identifier for each group or site.
Webroot Endpoint Management Deployment – We don’t have a MSP who manages our environment
Head to the Site Level Console from https://my.webrootanywhere.com/
*Go to resources tab,
“Windows download” and “email” already contains key code. Stick the “Windows Download” on the file server and or “email” the link to everyone.
Once agent is installed, it will communicate with the site level console.
New deployment under 100 users should use the above deployment methods. The machines will populate in the “default group” and then you move to New York or San Diego. Alternatively, use the following link to deploy into specific groups.
There are a slew of other options when over a 100 clients to deploy.
Notifications – How do we know when agents are deploy or a threat is happening?
Unfortunately, no notifications other emailing support are created by default.
Go to Alerts tab in “back to sites”
1) create distribution list
2) create alerts
Device Management – Who’s Computer?
Managing many sites and many computer that are all be on-boarded at the same time will ultimately beg the question, who’s computer is this? What client site should I be moving this site to?
MSP Mode – Moving device endpoint to different site will issue another keycode for the correct customer site.
ProTip! Make sure you have devices moved and accounted for in the correct sites as illustrated below.
Webroot Endpoint Protection – Policies
Create default policies for both workstation and server endpoints. Then move devices to specific site with specific policies. NOTE: This task should be done first before setting up sites when setting Webroot for the first time.
The default policy is pretty good but worthy of review.
Webroot is Flexible and Specifically Designed for MSP management
Works with many RMMs including:
RMM – (https://ninjarmm.com/).
RMM – Autotask
Autotask – API Access
No API required if using Autotask PSA
Malware & Virus Support by Webroot Summary and Resources
Don’t sit idle until your data is compromised and your computer or business is praying for valid and recent backups. . I have yet to try their cloud offering. Kapersky gives me the heebeegeebees with its Russian affiliation. ESET, Sophos and TrendMicro maybe worthy of looking at too.