Forum Discussion
Bug: Windows 10 Pro Education: This policy is blocked - its value will be ignored
Gunnar-Haslinger thank you for the report! Kelly got in touch and I was able to setup and reproduce the problem. You are correct in that we were incorrectly categorizing the Professional Education edition which resulted the "sensitive" policies always getting filtered out.
I have a fix ready that we will get in as soon as we can.
MicrosoftThanks, Deleted !
Gunnar-Haslinger Hello! Yes, I've reached out to some folks on the team and we will follow up with updates. Thanks!
-Kelly
MicrosoftGunnar-Haslinger thank you for the report! Kelly got in touch and I was able to setup and reproduce the problem. You are correct in that we were incorrectly categorizing the Professional Education edition which resulted the "sensitive" policies always getting filtered out.
I have a fix ready that we will get in as soon as we can.
Edge Can Version 88.0.704.0 already seems to include the Bugfix and respects the policies on Win10 Pro Education as expected.
Hope Dev/Beta/Stable get this update too soon.
- mkruger
Gunnar-Haslinger this will also be available in 87.0.664.53.
I like to re-open this issue, because the same problem occurs with "Windows 10 Pro for Workstations".
I just re-tested following three browser Versions:
- Edge v91.0.864.41 (Stable)
- Edge v92.0.902.9 (Beta)
- Edge v93.0.910.5 (Dev)
On todays most actual Win10-OS Version: Win10 v21H1 Build 19043.1052
I tested following Windows 10 Editions (SKUs / KMS Keys see https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys)
Windows 10 Enterprise: OK
Windows 10 Pro: OK
Windows 10 Pro for Workstations: ERROR!
Windows 10 Pro Education: OK
Windows 10 Education: OK
"OK" means my Policy shows no Errors, all "Status" Fields are OK.
"Error" means following result: "Error, Ignored - This policy is blocked - its value will be ignored."
All Policies which are documented as "This policy is available only on Windows instances that are joined to a Microsoft Active Directory domain or Windows 10 Pro or Enterprise instances enrolled for device management." do not work on "Windows 10 Pro for Workstations" Edition of Windows 10. All other Policies still work as expected, but Policies like HomepageLocation, DefaultSearchProvider, RestoreOnStartUpURLs etc... which need an MDM-Enrolled or AD-Joined Device don't work in my MDM-registerd Policy-Setup.
