Forum Discussion
Cache server hostname source & LocalPolicyMerge setting
hi
In our organization we have the LocalPolicyMerge setting set to false thus blocking all standard or custom locally created inbound MDE firewall rule. Outbound does not have any such restriction. We do see that the clients does not receive OptionID235 value from DHCP server.
We did see a note in the Microsoft documentation [Delivery Optimization reference] been called out for this, but with less information on what is the configuration or setting that gets blocked.
If the LocalPolicyMerge setting is configured, such as part of security baselines, it can impact DHCP client and prevent it from retrieving this DHCP option, especially in Autopilot scenarios.
Does anyone have the same issue and what are the rules that were created to have this working?
Thank you.
1 Reply
- Viktor_GrzebykCopper Contributor
In case of you are speaking about clients that are not getting MCC Server by DHCP option.
Since local policy merge is disabled, you’ll need to push a complete set of firewall policies to the client from your management platform.
Bind this FW profiles to Domain Profile
https://learn.microsoft.com/en-us/windows/deployment/do/delivery-optimization-configure#ports
If it still doesn’t work, review this thread: MCC Deployment Large Enterprises | Microsoft Community Hub