Uninstall the Cybermatic network discovery agent

Clean removal on Linux, Windows, and macOS — and what happens to the devices it discovered.

1. 1Before you begin. This removes the network discovery agent only. If the same machine also runs the Cybermatic device agent, that one is separate — different program, different service name — and keeps running. See "Uninstall the Cybermatic device agent" for that. Start in Cybermatic: open Settings → Agents → Network discovery and Revoke the responder's token. The agent's configuration file holds that token, so revoking first guarantees nothing can report again even if a copy of the config is left behind somewhere.
2. 2Linux. Debian/Ubuntu: sudo systemctl disable --now cybermatic-discovery sudo apt remove --purge -y cybermatic-discovery sudo rm -rf /etc/cybermatic-discovery RHEL/Rocky/Amazon Linux: sudo systemctl disable --now cybermatic-discovery sudo rpm -e cybermatic-discovery sudo rm -rf /etc/cybermatic-discovery Installed manually from the tar.gz: sudo systemctl disable --now cybermatic-discovery sudo rm -f /lib/systemd/system/cybermatic-discovery.service sudo systemctl daemon-reload sudo rm -f /usr/local/bin/cybermatic-discovery sudo rm -rf /etc/cybermatic-discovery The final rm removes the enrollment configuration, which the agent wrote at enroll time rather than the package installing it — which is why package removal alone leaves it behind.
3. 3Windows. Run the bundled uninstaller from an administrator PowerShell: & "$env:ProgramFiles\CybermaticDiscovery\uninstall.exe" Then remove the configuration, which lives outside the install directory: Remove-Item -Recurse -Force "$env:ProgramData\CybermaticDiscovery" If the uninstaller is missing, do it by hand: schtasks /End /TN "CybermaticDiscovery" schtasks /Delete /F /TN "CybermaticDiscovery" Remove-Item -Recurse -Force "$env:ProgramFiles\CybermaticDiscovery" Remove-Item -Recurse -Force "$env:ProgramData\CybermaticDiscovery" Confirm it is gone: schtasks /Query /TN "CybermaticDiscovery" should report that the task does not exist.
4. 4macOS. sudo launchctl bootout system /Library/LaunchDaemons/ai.cybermatic.discovery.plist sudo rm -f /Library/LaunchDaemons/ai.cybermatic.discovery.plist sudo rm -f /usr/local/bin/cybermatic-discovery sudo rm -rf "/Library/Application Support/CybermaticDiscovery" If bootout reports the service is not loaded, that is fine — continue with the removals. On older macOS releases use sudo launchctl unload instead of bootout. Confirm: sudo launchctl list | grep cybermatic returns nothing for discovery.
5. 5Afterwards, in Cybermatic. The devices this agent discovered do not disappear. They stop being refreshed, so their last-seen time freezes and they age out of the active view over the following days. If you want them gone immediately, use the Unmanaged devices page to delete or ignore them. If you tagged any of them — display name, owner, criticality — that information stays with the device record, and is still there if you install a discovery agent on that segment again later. Discovered devices do not count against your plan's asset limit in the way agent-managed assets do; removing the agent does not free capacity you were paying for.

Tip: Revoke the token in the dashboard first, then uninstall. Revocation is the authoritative stop — the local commands are the cleanup.