Problem overview.
The challenge this resource is designed to solve.
Rolling out an endpoint security agent across a mixed Windows and macOS fleet usually turns into a manual checklist: figure out which machines already have the agent, pull the right installer for each platform, pass the site key so the device lands in the correct portal tenant, then come back later to confirm the services actually started. Doing that by hand across sites means duplicate installs on machines that were already covered, silent failures nobody notices until an audit, and devices that never get associated with the right Webroot portal. The gap that costs the most time is the verification step, because an installer exiting cleanly is not the same thing as the agent running.
About this resource.
What it does and how it fits into your workflow.
This automation handles Webroot deployment on Windows and macOS endpoints from a single workflow. It checks for an existing installation first, installs only where Webroot is missing, waits for the agent to come up, re-checks, and creates an alert if the final check does not report success.
Triggers. The automation can be run manually, or triggered when the WEBROOT tag is applied to a device. The tag trigger ships disabled on import, so re-enable it if you intend to deploy by tagging devices.
Before you deploy. Populate the WebrootSiteKey custom field with your Webroot site key. The automation uses that value to associate devices with your Webroot portal.
Windows path. A script checks whether Webroot services are running. If Webroot is detected, the automation exits for that device. If it is not detected, the automation downloads the Webroot MSI, starts the installer silently, waits five minutes for services to come up, then runs the same check script again.
macOS path. A script checks whether Webroot is present in /Applications. If it is detected, the automation exits. If not, it downloads the Webroot installer script and package, runs the installer with the site key, waits five minutes, then re-checks.
Platform conditions. Both branches live in the same automation and use platform conditions, so a Windows device only executes Windows steps and a Mac only executes macOS steps. You do not need separate automations or separate device groups per operating system.
Failure handling. If the final check does not report a successful installation, the automation raises an alert that includes the installation status and details, so the failure surfaces in monitoring instead of being discovered weeks later.
macOS permissions caveat. Full Disk Access and the system network extension must be enabled manually on each Mac. The automation cannot grant these permissions. Plan for an MDM profile or a hands-on step on Macs, and treat the install as incomplete until those are in place.
The workflow is built from standard Level automation actions and scripts, so you can open each step, review the check logic, and adjust download sources or wait times to match your environment.
Use cases.
Common ways to put this resource to work.
- Onboarding a new client or site where every Windows and Mac endpoint needs Webroot installed and associated with the correct portal via site key.
- Backfilling coverage across an existing fleet, where the already-installed check prevents reinstalling on devices that are already protected.
- Tag-driven deployment: apply the WEBROOT tag to a device or group and let the trigger handle installation without an operator running anything manually.
- Remediating agent gaps found during a security review, with alerts flagging the specific devices where the post-install check did not report success.
- Standardizing deployment across a mixed Windows and macOS environment without maintaining two separate installation workflows.
Recommendations.
Practical guidance for a reliable rollout.
- Fill in the WebrootSiteKey custom field before the first run. Without it, macOS installs cannot pass the site key to the installer.
- Leave the tag trigger disabled until you have tested a manual run on one Windows device and one Mac, then enable it for broader rollout.
- Pair the rollout with an MDM profile that pre-approves Full Disk Access and the system network extension on macOS, since the automation cannot set those permissions.
- Treat the Webroot Installation Issue alert as the source of truth rather than assuming a clean installer exit means success. Route it to whoever owns endpoint security.
- Review the five minute delay against your slowest machines. If agents on older hardware routinely need longer to start services, extend the wait before the final check.
- Verify the download URLs used by the download actions still point to the installer build you intend to deploy before a large rollout.