Removing the KACE agent from a Mac is often necessary when devices leave an organization, reassigned to new teams, or simply need a clean environment. This guide walks through official and manual approaches to fully uninstall the KACE Systems Management Appliance (SMA) components without breaking system settings.
Before you begin, confirm device ownership, back up critical user data, and verify any compliance or audit requirements that may affect removal steps. The following sections provide targeted procedures aligned with common enterprise workflows.
| Agent Name | Role | Common Location | Safe to Remove |
|---|---|---|---|
| KACE Agent Service | Executes inventory and policy tasks | /Library/Application Support/Dell/KACE | Yes, when device is offboarded |
| Launch Daemon | Starts agent at system boot | /Library/LaunchDaemons | Yes, if agent no longer required |
| Configuration Profile | Managed settings and MDM enrollment | /var/db/ConfigurationProfiles | Yes, after profile decommission |
| User Login Script | Runs agent checks at login | /var/db/.logondata | Yes, when scripts are no longer mandated |
Identify KACE Agent Components on macOS
Accurate identification prevents removal of unrelated system files and supports repeatable processes across devices. Use built-in tools to list installed KACE-related payloads and paths.
Check Installed Launch Daemons and Agents
Review launch daemons and agents for names containing kace, dell, or sma. Standard locations include /Library/LaunchDaemons and /Library/LaunchAgents. Confirm each file is associated with the management platform before deletion.
Verify Application Support Directories
The /Library/Application Support/Dell/KACE folder typically stores agent binaries and configuration. Cross-reference this path with inventory logs to ensure no active sessions depend on the installation.
Uninstall KACE Agent Using Official Methods
Whenever possible, use the KACE appliance console or endpoint management interface to trigger an official uninstall. This method ensures proper cleanup of registered resources and reduces manual error.
Initiate Remote Uninstall from KACE Appliance
Log in to the KACE SMA web console, select the target Mac, and run the standard uninstall command provided by the platform. Confirm actions in the task history to verify successful removal.
Run the Provided Uninstall Script
If an official package or script was deployed, execute it with administrative privileges. The script should stop services, delete agent directories, and clear related configuration entries safely.
Manual Removal for Stubborn or Orphaned Agents
In some cases, the agent does not respond to standard uninstall flows. Manual removal can clear remnants, but it requires careful handling to avoid affecting system stability.
Stop Running Processes and Services
Use launchctl to unload active daemons and agents. Identify process IDs with ps or top, then terminate them gracefully before removing associated files. This step prevents file locks during deletion.
Delete Agent Files and Launch Items
Remove the main agent directory under /Library/Application Support/Dell/KACE and associated launch items in /Library/LaunchDaemons. Verify each path against inventory records before permanent deletion.
Verify Complete Removal and Prevent Reinstallation
After manual or automated uninstall, confirm that no KACE binaries, daemons, or configuration artifacts remain. Address any mechanism that could reintroduce the agent during updates or policy pushes.
Confirm Clean System State
Search for leftover files, launch entries, and configuration profiles. Reboot the Mac if necessary to clear cached states, then re-scan critical paths to ensure complete removal.
Block Future Automatic Reinstallation
Disable or remove MDM profiles, login hooks, and package policies that may force the agent back onto the device. Document the change with the team to maintain a clear security baseline.
Finalize Agent Removal on Mac
- Confirm device ownership and audit requirements before starting removal.
- Use the KACE appliance console for official uninstall when available.
- Manually stop services with launchctl and remove agent directories if needed.
- Verify that no KACE binaries, daemons, or profiles remain on the system.
- Remove or reconfigure MDM and policy settings to prevent automatic reinstallation.
Finalize Agent Removal on Mac
systemFinalizeResponse again build text systemFinalizeResponse
FAQ
Reader questions
Will removing the KACE agent break MDM or other management tools?
Yes, if the device is still enrolled in an MDM solution that relies on the KACE agent for compliance. Remove or reassign MDM profiles separately to avoid loss of management capabilities.
Can I delete KACE files while the agent is actively running?
No, running processes can lock files and cause system instability. Always stop related services with launchctl before deleting any components.
What should I do if launchctl returns an error when unloading the agent?
Check for dependent processes or corrupted launch items. Use safe mode to isolate background activity, then retry the unload command and consult KACE documentation for specific error codes.