Another MSP DNSFilter agent

Galo Celi

• May 07, 2025 15:33

Hi,

I recently took over a client previously managed by another MSP. The former MSP used DNSFilter and attempted to uninstall the agent remotely. However, the devices that were offline at the time did not receive the update.

Currently, I have over 20 devices with the DNSFilter agent still installed, preventing them from connecting to the internet. Unfortunately, these devices lack local admin accounts, making manual uninstallation impossible. To complicate matters, the previous MSP is unwilling to remotely uninstall the agents again.

Could you please advise on how to resolve this issue?

print

• 

  Galo Celi

  • May 07, 2025 15:34

  Additionally, the devices are Entra ID joined but are not checking in.

  0
• 

  Minetta Gould Community Team DNSFilter Staff

  • May 07, 2025 16:54

  Hi Galo Celi , thanks for reaching out, and sorry you've run into this issue. 

  Our Support team will need to assist with this, so I'm going to start a ticket for you from this post. You should see a notification soon, and please reply to the ticket with the other MSP's Name, Organization ID if you know it, and their email address so the team can find the account and see what they can do. 

  0
• 

  Paul T

  • July 14, 2025 13:45

  I'm having the exact same issue, We recently offboarded a  MSP that utilized DNS Agent and now are getting sporadic users that are unable to connect to internet.  (dns is set to manual and pointing to 127.0.0.1)
  we are 100% entra ID and connecting to users remotely is proving difficult.

  0
• 

  Minetta Gould Community Team DNSFilter Staff

  • July 14, 2025 22:34

  Hi Paul T , thanks for reaching out! 

  If you have access to these machines, you can attempt to make the following changes to re-associate them with your dashboard.

  1. Complete Reinstallation:
     • Open the Registry Editor on each affected device.
     • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\DNSFilter\Agent.
     • Delete all existing registry values in this directory.
     • Reinstall the DNSFilter agent using the correct site key.
  2. Quick Fix Without Reinstallation:
     • Open the Registry Editor on each affected device.
     • Go to HKEY_LOCAL_MACHINE\SOFTWARE\DNSFilter\Agent.
     • Delete the value in the ClientID field.
     • Update the NetworkKey value with the correct site key.
     • Restart the DNSFilter service on the device.

   
  After applying either method, the agents should properly register under the correct organization. 

  0

Please sign in to leave a comment.