In this article
DNSFilter account users with admin permissions or higher use this article to uninstall the macOS Roaming Client on individual devices or remotely by using a MDM tool.
Beginning with v2.2.0, remote (silent) installs of the macOS Roaming Client include three .mobileconfig profiles to be uninstalled alongside the agent package.
⚠️ Important: Deleting the agent from the DNSFilter dashboard does not uninstall the Roaming Client. Deleted agents will reappear in the portal upon next sync.
Standard uninstall (ran on end-user device)
Run this command from the device terminal:
sudo sh /Applications/DNSFilter\ Agent.app/Contents/Resources/uninstall.shsudo sh /Applications/DNS\ Agent.app/Contents/Resources/uninstall.sh
To confirm the agent is uninstalled:
yes | sudo sh "/Applications/DNSFilter Agent.app/Contents/Resources/uninstall.sh"yes | sudo sh "/Applications/DNS Agent.app/Contents/Resources/uninstall.sh"
Silent uninstall (ran via MDM tool)
Just like installing the Roaming Client, admins can uninstall the Roaming Client remotely with an MDM tool using the above commands. However, DNSFilter does not endorse or validate third-party software processes.
macOS agent v1.8.6 and older
Uninstalling the v1.8.6 and older agent silently only requires running the above commands from the MDM tool: mobileconfig files were not deployed, so do not require removal like the v2.2.0+ Roaming Client.
Uninstalling the v2.2.0+ agent includes removing the mobileconfig files pushed during deployment. For MDM-specific uninstall instructions, consult the vendor's documentation.
- Uninstall the agent installer package using the above commands
- Following the MDM's processes, remove the
mobileconfigfiles in this order:-
Proxy.mobileconfig -
Extension.mobileconfig DNSFilter_Certificates.mobileconfig
-
The macOS Roaming Client is now uninstalled and will no longer receive DNS traffic.
Related Content
- Install the v2.2.0+ agent with an MDM solution or manually
- Troubleshoot end-user prompts still occurring with the v2.2.0+ build deployed via MDM
- End-users report lost internet connectivity after the agent update
- Your network environment runs another DNS Proxy such as an EDR or VPN and macOS only allows 1 proxying agent per device
Comments
0 comments
Please sign in to leave a comment.