![]() ![]() Note we have thousands of group policies with lists like Applocker, IE settings, Office settings in multiple policies. So instead of Edge "appending" the registry key like IE does, the policy deletes the Tier 1 settings and applies only the Tier 2 settings. Microsoft Edge = Pop up blocker = Allow = *. *. *. IE Settings = Pop up blocker = Allow = *. *. *. *. *. *. Group Policies with Lists are SUPPOSED to be "cumulative" so if you add a Trusted site or a popup for IE in the Parent OU and different ones in the child OU they "merge" together. ![]() IE Settings = Pop up blocker = Allow = *. *. *. Microsoft Edge (latest ADMX) = Pop up blocker = Allow = *. *. *. ![]() "Health Authority A User and IE Edge Settings All" IE Settings = Pop up blocker = Allow = *. *. *.Ĭhild OU = Health Authority A (so this OU is inside the above one) = Tier 2 ![]() Group Policy linked to OU = "User and IE Edge Settings All" Group Policies have always been set to COMBINE and in the case of the Edge Policies they also should combine" not replace. There is absolutely no reason why it is not working. Anything that has a list if it is set again, the list gets replaced instead of appended. The same seems to go for all these "list" type Edge policies. If we allow 20 sites to not block popups then those 20 sites should remain EVEN if a subset of the organization wants to add their own sites to the list. However, for Microsoft Edge it is a REPLACE in policy and registry which is really, really bad for Enterprise. This goes for all the other IE GPO settings. So pop-ups allowed in the root policy and pop-ups allowed in the lower policies BOTH get added to the computer. In Group Policy for IE if you add "pop-up allow list" at a root group policy, and then another lower group policy the pop-up lists MERGE. We have 86,000 health computers we are migrating to Microsoft Edge from IE 11. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |