In this article
Users with admin permissions or higher use this article to uninstall Windows Roaming Client version 2.0.1+ directly from the DNSFilter dashboard. The download and installation for this version follow standard methods.
Prerequisites
- Only available for x64 builds and requires .NET 4.8.0+
- Users must be running Windows agent version 2.0.1+
Uninstall from the DNSFilter dashboard
Follow these steps to complete the uninstall.
- Navigate to the Roaming Clients tab in the dashboard
- From the Actions menu, select the more options menu (···)
- Select Delete & Uninstall
- To uninstall multiple agents at once:
- Check the box next to the Client Name of each agent
- Select Delete
- To uninstall multiple agents at once:
- Select Delete & Uninstall
The Roaming Client(s) will move to a Pending Uninstall status, which saves the uninstall configuration to the server. The next time the agent checks in, it retrieves and executes the uninstall, which is typically within five minutes.
✍️ This process can take longer when an agent is offline: in these instances the agent stays in Pending Uninstall status until it wakes up and checks in with the dashboard.
The Roaming Client will no longer show up in the dashboard when the uninstall is complete.
What happens if I try to uninstall an older Roaming Client version?
The Roaming Client dashboard will only issue the uninstall command to supported agent versions. If supported and unsupported versions are selected, the dashboard will deliver a warning that the unsupported agents will be removed but not uninstalled and create two lists for review:
- Roaming Clients that will be deleted (remote uninstall is not supported)
- Roaming Clients that will be deleted & uninstalled (remote uninstall is supported)
Uninstall manually
Use these steps if the dashboard uninstall did not work or a scripted/GPO/RMM uninstall configuration is preferred for your environment.
✍️ The GUID unique to the Organization, not the user account.
- Copy the GUID from this registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\DNSFilter\AgentComputer\HKEY_LOCAL_MACHINE\SOFTWARE\DNSAgent\Agent
-
Insert the GUID into this prompt and run it from an administrator command prompt:
msiexec /X{GUIDHERE} REGCLEAN=true/false (to remove and cleanup registry or not)
The Roaming Client will be uninstalled once the command run finishes.
If an error occurs during the uninstall process, re-run the commands with these edits to create a log file. Our Support team can review these files to investigate the issue.
msiexec /X{GUIDHERE} REGCLEAN=true/false (to remove and cleanup registry or not) /L*vx! FOLDERANDLOGFILE (eq: C:\Temp\dns_agent_uninstall.log)
Comments
4 comments
Not sure if this was just because my test machine was in the MSP/WhiteLabel/beta track (v2.0.3 at the time of this comment), but my registry key for the GUID (manual uninstall method) was actually in
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\DNSAgent\Agentnot\SOFTWARE\DNSFilter\Agent. I got the right GUID by running the powershell commandGet-WMIObject -Classname Win32_Product | Where-Object Name -Match ‘DNS Agent’that I got from the “Uninstall Windows Roaming Client v1.15.3 and older” page :)Hi Christopher Harris , thanks for the callout! We missed adding the whitelabel registry key to this guide, but got it all fixed up. Nice work finding it in the other article, and thanks for your help in improving our content!
Is it possible to post the exact command prompt code without having to alter it? No matter what I try it's not working for the white label version. The uninstall commands from the DNS Filter dashboard leave the DNS server info behind on the network adapter settings leaving the computer blocked from accessing the network. I would rather try the manual uninstall using our RMM tool. Thanks.
Hi Mike South thanks for reaching out, and sorry you're having this issue! Our team isn't aware of a method to uninstall the agent that doesn't require the GUID listed in these commands, but there may be something else going on here that they'd like to help troubleshoot.
I'm going to start a support ticket for you: please reply to that ticket with diagnostic logs from an impacted device to help the troubleshooting process. Someone from the Support Team will connect with you to help resolve the issue!
Please sign in to leave a comment.