See what you’re importing.
Read-only preview
| Monitor name | Monitor type |
|---|---|
| Windows - Webroot WRSkyClient (Service monitor) | Windows - Webroot WRSkyClient (Service monitor) |
| Webroot Installation Check (Application monitor) | Webroot Installation Check (Application monitor) |
| Windows - Webroot WRSVC (Service monitor) | Windows - Webroot WRSVC (Service monitor) |
| Windows - Webroot WRCoreService (Service monitor) | Windows - Webroot WRCoreService (Service monitor) |
Included with this resource.
Everything added when you import.
Tags
- WEBROOT
Before you enable it.
Scope the policy to the groups that are supposed to run Webroot. Applying it fleet-wide will flag every device that legitimately uses a different endpoint product.
Confirm the operating-system scoping matches your intent before rolling out. The installation check in this policy is scoped to Windows and macOS.
Treat the warning severity as a starting point. If missing endpoint protection is a hard failure in your environment, raise the severity so it escalates the way your alert routing expects.
Add your own automation if you want remediation. The policy itself only reports, so decide deliberately whether a stopped service should be restarted automatically or should page a technician.
Watch for devices that alert on one service but not the others. A single stopped service usually points at a different root cause than a full uninstall and is worth investigating separately.
Review alerts during maintenance windows and reimaging work, where short-lived service stops are expected and should not be treated as drift.
More about this resource.
What it does
The Webroot Services Monitor bundles four monitors into a single policy you can apply to the device groups that should be running Webroot.
One application monitor, Webroot Installation Check, verifies that Webroot is installed. This monitor works for macOS and Windows.
Three service monitors cover the Windows side of the agent and check that each of these services is active:
WRSkyClient(Windows - Webroot WRSkyClient)WRSVC(Windows - Webroot WRSVC)WRCoreService(Windows - Webroot WRCoreService)
All four monitors are set to warning severity. The policy ships with no triggers and no actions attached, so it reports state rather than remediating it. If you want reinstall or service-restart behavior, you build that separately with automations and scripting and decide for yourself what should run unattended.
Because the monitors are scoped per operating system, applying the policy to a mixed fleet does not generate noise on devices where a given check does not apply. The Windows service checks only evaluate on Windows; the installation check evaluates on the operating systems it is scoped to. See remote monitoring for how monitor state surfaces across devices.
When to use it
- Confirming that every device in a managed group actually has Webroot installed, instead of inferring coverage from the vendor console or a license count
- Catching Windows endpoints where Webroot is installed but WRSVC, WRCoreService, or WRSkyClient has stopped, so the agent is present but not fully functional
- Validating new device builds and onboarding before a machine is handed to a user, by applying the policy and checking that all four monitors report healthy
- Spotting removal of the agent after a user with local admin rights uninstalls it or a reimage drops it
- Producing a per-device view of endpoint protection state for client reporting or an internal audit conversation
The problem it solves
Endpoint protection only counts when the agent is actually present and its services are running. Webroot can be uninstalled during a device rebuild, skipped in a hurried onboarding, or left in a half-working state after its Windows services stop or fail to start. None of that shows up in a dashboard that only tracks license counts, and the gap is usually discovered during an audit or after an incident. Checking installation and service state continuously on every endpoint is the difference between assuming coverage and knowing it.