Skip to main content

How can we help you?

Search

help Knowledge Base
forum Community
checklist Release Notes
event Events

Uninstall macOS Roaming Client v2.2.0 or higher

Minetta Gould
  • Updated

    In this article

Network environment admins follow this article to uninstall the macOS Roaming Client version 2.2.0+ when deployed via MDM. If the mobileconfig files were not pushed to the device, follow the standard uninstall method. 

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 Process

  1. Uninstall the agent installer package following the standard uninstall method
  2. Following your MDM's processes, remove the two mobileconfig files in this order:
    1. Proxy.mobileconfig 
    2. Extension.mobileconfig 

The macOS Roaming Client is now uninstalled and will no longer receive DNS traffic. 

If offboarding from DNSFilter, remove the DNSFilter_Certificates.mobileconfig file as well (if deployed) to revoke those permissions. 

Related Content

Comments

4 comments

Date Votes
  • Mike South

    Can you post more detailed instructions on how to remove the .mobileconfig files?   We have ran the terminal command ( sudo sh /Applications/DNS\ Agent.app/Contents/Resources/uninstall.sh ) and then restarted yet DNS Filter is still installed on MacOS 15.6.1.    We do not use MDM profiles.

    0
  • Minetta Gould Community Team DNSFilter Staff

    Thanks for the details, Mike South—a couple things here are worth clarifying so we can help you get this fully removed.

    First, .mobileconfig profiles are only deployed through an MDM, and macOS doesn’t provide a native way to install or manage them outside an MDM workflow. Since you mentioned you don’t use one, can you share why you believe mobileconfig files are present? That will help us narrow down whether we’re actually dealing with a profile or something else on the device.

    Second, the uninstall command you posted is specifically for whitelabeled versions of the agent. Can you confirm whether the agent installed on your mac is a branded/whitelabeled build (DNSFilter\ Agent vs DNS\ Agent)? If so, that would explain why the standard removal isn’t taking effect. 

    0
  • Mike South

    Hi Minetta,

    Step #2 in the above uninstall process states the .mobileconfig profiles need to be removed, that is why I'm confused.   We are using the whitelabeled version.

    The instructions below worked for us after running the Terminal script.

    • Navigate to the following directories and delete any DNSFilter-related files:
         /Library/Application Support/
         /Library/Preferences/
         /Library/LaunchAgents/
         /Library/LaunchDaemons/

    • Empty Trash:
         Right-click on the Trash and select Empty Trash.

    • Restart the Device:
         Restart the Mac to complete the uninstallation.

     

    Thanks.

    0
  • Minetta Gould Community Team DNSFilter Staff

    Thanks for the follow-up, and I’m glad the cleanup steps you listed worked on your end. 🙌

    Just to clarify the confusion around .mobileconfig profiles: that section of the article only applies to MDM-managed deployments. The article introduction notes this, but I can see how it could be overlooked if you're not using an MDM. Without an MDM, those profiles wouldn’t be present on the device at all.

    Given that the manual directory cleanup solved the uninstall, the most likely causes were either:

    • the uninstall command potentially wasn’t run with sudo, or
    • the agent app may have been dragged to the trash before running the script, which changes the file path and causes the scripted uninstall to fail.

    In any case, I’m glad you were able to get the system cleaned up. If you run into anything else feel free to reach out!

    0

Please sign in to leave a comment.