Hello! Thank you for reaching out to the Hexnode community. We understand it can be frustrating when configurations don’t behave as expected, especially when managing multiple operating systems.
To help clarify the behavior you’re seeing:
- Platform Differences: On Windows, Hexnode allows you to target specific browsers for web content filtering. On macOS, the filtering is limited to Safari.
- Wildcard Support: You are correct, wildcards are not supported for Web Content Filtering. URLs must be entered exactly as they appear (e.g., https://www.example.com) to be recognized and blocked correctly.
Rest assured that as long as the URLs are valid and entered precisely in the correct format, the policy is designed to deploy and enforce these restrictions seamlessly across your managed fleet.
To help us narrow down the root cause, could you please clarify the following:
- Is the policy failing on both Windows and macOS, or is it limited to just one of the platforms?
- Are you seeing any specific error messages on the devices, or are the sites simply loading as if no policy is applied?
- Have you ensured that the URLs added to the policy exclude any wildcard characters (like *)?
Once we have these details, we can dive deeper into the troubleshooting steps for you!
Best regards,
George
Hexnode UEM