Forum Discussion
Why this policy is producing error? Configure new tab page URL
It's this Policy:
https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#newtabpagelocation
And based on the description, I've set it correctly on Edge 87 (the installed up-to-date policy files are also for Edge 87)
But it isn't being applied and I see an error in Edge:policy
why does it say the policy is blocked? what am I doing wrong?
Could it be because in the description it says:
"This policy is available only on Windows instances that are joined to a Microsoft Active Directory domain, Windows 10 Pro or Enterprise instances that enrolled for device management, or macOS instances that are that are managed via MDM or joined to a domain via MCX." ?
there it says this policy is available only on ..., I'm testing it on my personal Windows 10 machine that is not managed by a Windows server or MDM, could this be the reason?
If that is indeed the case then:
- the description is misleading, because it's not about availability, it's about whether the policy works or not.
- the error message in Edge://policy is vague and doesn't say exactly what happened and what is wrong.
- Any other policy that I tried works fine, this one doesn't. why a simple configuration like this would require a Windows server or MDM in order to work?
HotCakeX Your machine needs to be MDM-Managed or AD-Joined, otherwise you get a "this policy is blocked" Error.
Workaround for non-MDM-Managed an non-AD-Joined Devices, have a look at my Blog-Post:
https://hitco.at/blog/apply-edge-policies-for-non-domain-joined-devices/
- Spoiler
Gunnar-Haslinger wrote:HotCakeX Your machine needs to be MDM-Managed or AD-Joined, otherwise you get a "this policy is blocked" Error.
Workaround for non-MDM-Managed an non-AD-Joined Devices, have a look at my Blog-Post:
https://hitco.at/blog/apply-edge-policies-for-non-domain-joined-devices/
Thanks, I just finished reading your blog post, It is a workaround on those specific Windows versions but there are things that need to be considered:
- I'm using Windows 10 20H2 (release preview) and it might/might not work with those registry keys. and I don't want to use them in case it conflicts with something else somewhere in Windows that is still undocumented or just simply unknown.
- Windows 10 is always changing and evolving, this solution is a brute force method to achieve what I want.
I would rather have an explanation to know at least why this requires a domain controller or MDM to work. after all, what I was doing is just a test and I didn't want to fire up any servers to do a simple task like that, but apparently, I need to.
so again, these 3 are my main concerns and I want Edge team to consider as feedback and change the behavior (if possible) in the future:
