Same for me. I tried with the value a disable but the deployment fails. I would really like to find a fallback method.

same. not sure if I need it yet, but I can’t deploy the disable and then find out someone need IE, and it’s irreversible. Excluding things from the OMA URI Policy works, but in order to do that I’d have to know every device that needs IE in advance. I can’t go through 5000 devices to figure out which one needs IE.

I’m also struggling to get this to work from domain group policy. I tried your suggestion and it throws an error when editing policy thereafter!?

What I did was…

1) Confirmed my DC C:\Windows\PolicyDefinitions\inetres.admx file does indeed contain the “DisableInternetExplorer” setting.

2) Backed up my SYSVOL\PolicyDefinitions\inetres.admx copy and replaced it with the local copy from above.

3) Try and create a new GPO via group policy editor and it throws out and error.

Resource ‘$9string.AllowSaveTargetAsInIEMode)’ referenced in attribute displayName could not be found

File
\\MyDomain.com\SysVol\MyDomain.com\Policies\PolicyDefinitions\inetres.admx, line 35191, column 278

Is this potentially because I have a mixture of Server 2016 and Server 2019 domain controllers? The domain is running at 2016 functional level.

Or perhaps do you need to install Edge before this will work?

Hi Dennis,

You could give this a try;
First, check the inetres.admx file on your local system. If it contains the DisableInternetExplorerApp setting, you should copy that file to your central store or PolicyDefinition folder.
But I’ve not tested that, as I’m using Intune to manage the devices.

I am having a similar issue as Andy above. I am logged into our DC but I do not see this GPO option either on the COMPUTER or USER configurations.

DC = Windows Server 2019 STD

However, on my local GPO I do see this option. Locally I am running Windows 10 version 20H2

My question is how do I enable this policy on the domain level?

Our DC is in-house and we do not use InTunes.

Thanks in advance for your reply and again this article.

Are you running at least 19042.804?

Any ideas?