Already a NinjaOne customer? Log in to view more guides and the latest updates.

NinjaOne Integrations: Uninstalling Integrated Components

  • Last Updated April 22, 2026

Topic

This article explains how to uninstall software associated with NinjaOne's integrations, such as third-party antivirus software.

Environment

NinjaOne Integrations

Description

When uninstalling NinjaOne, you may also need to uninstall third-party components. The following sections describe uninstall procedures for third-party components that you may be using in conjunction with NinjaOne.

Select a product to learn best practices for removal:

Bitdefender

Uninstall NinjaOne and Component

If you set up password protection for the Bitdefender installation, uninstalling NinjaOne will not prompt Bitdefender to be uninstalled. You must manually remove password-protected installations of Bitdefender from the device before uninstalling NinjaOne. If Bitdefender is still on the device after you have uninstalled NinjaOne, refer to NinjaOne Integrations: Deactivate or Remove the GravityZone Integrations for instructions.

For Bitdefender Software Development Kit (SDK), when you uninstall NinjaOne by deleting a device from your NinjaOne console, Bitdefender is also uninstalled from the device. If you deactivate Bitdefender at the policy level, NinjaOne will remove it from the device.

Uninstall Component Only

For Bitdefender SDK password-protected installations: If the device still exists in NinjaOne, attempt to reactivate Bitdefender for the device as an override, with password protection turned off. This action can, in some cases, remove the password from Bitdefender and allow NinjaOne to uninstall it once the policy is inactive again. If this procedure fails, contact NinjaOne Support for assistance.

CloudBerry

You can ensure that your backup data gets properly deleted for the device from which you are uninstalling CloudBerry by performing the following steps:

  1. Delete or deactivate the backup plan for the device, either at the policy level or as a device-level policy override. To learn about device-level overrides, refer to NinjaOne Policies: Change or Override a Device Policy in NinjaOne.
  2. Delete the backup data for the device.
  3. After triggering the deletion, wait 24 hours to provide time for the backup data to be entirely deleted from the servers.
  4. Deactivate CloudBerry at the organization level for the device. This action will trigger CloudBerry to be uninstalled.
  5. Proceed to delete the device from the NinjaOne dashboard to trigger the uninstall of the NinjaOne Agent. To learn how to delete a device from a NinjaOne dashboard, refer to NinjaOne Platform: Delete or Remove a Device.

CrowdStrike

CrowdStrike does not uninstall when you change the policy in NinjaOne. If you remove a device from NinjaOne, CrowdStrike remains unaffected and installed on the endpoint. Uninstall by using CrowdStrike's uninstaller package or by using the CrowdStrike Falcon control panel.

While we recommend contacting CrowdStrike Support for uninstall assistance, you can refer to Splashtop: Integration Guidefor more information.

TeamViewer

To deactivate and remove TeamViewer from both the NinjaOne console and the endpoint, refer to the following steps:

  1. Deactivate the TeamViewer integration on the NinjaOne console. This action will prevent NinjaOne from reinstalling TeamViewer on the device.
  2. Uninstall TeamViewer from the endpoint by executing the script in our Custom Scripts: Remove TeamViewer (Windows). article. Deploy the script locally on the device or add it to your Automation Library for deployment via NinjaOne.”
  3. After you have uninstalled TeamViewer, delete the device from your NinjaOne console to uninstall the NinjaOne Agent.

You can also deactivate TeamViewer for a specific device or devices on the NinjaOne device dashboard in the Settings tab. Refer to TeamViewer: Integration Guide (Automatic) for more information.

Webroot

Uninstall NinjaOne and Component

When you uninstall NinjaOne by deleting a device from your NinjaOne console, this action also triggers a deactivation request to the Webroot Global System for Mobile Communications (GSM) console. Once Webroot receives this request, it will remove the Webroot instance from the device. This process may take up to 24 hours to complete.

If you installed Webroot manually, rather than allowing NinjaOne to push the install, deleting the device will not cause Webroot to be uninstalled. You need to uninstall Webroot from the device manually.

Uninstall Component Only

If you deactivate Webroot at the policy level for the device, the Webroot GSM console receives a deactivation request from NinjaOne. This request should cause Webroot to uninstall from the device in question. This process may take up to 24 hours to complete.

Additional Resources

The following resources provide more details about uninstalling components in NinjaOne:

FAQ

Next Steps