Roaming Client - Split policies
We would like to have the "Automatically Disable the Roaming Client on Protected Networks" feature without implementing the virtualized OpenDNS servers.
This would allow you to create an "on-network" & "off-network" policy as described in the following Umbrella Knowledge base.
---
The key difference is we would like the determination made by a match in the defined Networks. So I can have one policy when my network matches and a different policy when I am on an undefined network that OpenDNS does not recognize. That way I can block streaming content when a roaming client is in one of my offices on a known network and when they go home and are using their own network they can have a less limited set of content filters that have the potential to use lots of bandwidth and potentially looser content filters like NSFW content.
-
Hello,
Thanks for submitting this. If I'm understanding you correctly, you'd like the Roaming Client to adopt a different policy when it's off of a defined network as opposed to when it's on that network? This is what the article you linked documents the client doing already, but you can't define your employee's home networks in this way. You can only register your own networks.
When the Roaming Client detects that it's behind a network that is registered in your Dashboard, it will back off, and let the network's Policy apply instead.
Please let me know if I'm misunderstanding what you're requesting, or if you have any other questions or concerns.
Please sign in to leave a comment.
Comments
1 comment