Web content filtering not working on devicesSolved

Could you please check if you can still access the URLs via different browsers?

Yes, the URLs were previously blocked by another MDM, but now they’re accessible across browsers without any issues. So the web filtering policy isn’t taking effect on those devices.

It sounds like the previous MDM solution didn’t fully clean up its configuration during disenrollment. There might be leftover registry keys or browser policy entries still affecting behavior.

You can try a few things to clear out any leftover settings that might be interfering:

First, check the browser policies by opening chrome://policy or edge://policy on the device. See if any old blocked websites are still listed there.

Next, take a look at the device’s settings (specifically the Windows Registry) to see if there are any entries related to website blocking left over from the previous MDM. These might be found under Chrome settings for the current user or the whole device.

If you do find anything, try removing those entries and restarting the device. After that, reapply the web content filtering policy from Hexnode and check if the changes show up in the browser’s policy view.

Thanks for the detailed steps! We ended up testing the Hexnode Gateway migration method on a few affected devices, and it worked as expected. The filtering policy is now applying correctly.