Forum Discussion
FuriousFred
May 10, 2023Copper Contributor
Enable Network Protection - Error "-2147467259" - Windows Server 2016
Hi
When assigning an antivirus policy, where "Enable Network Protection" is either configured to audit or blocked mode, in Intune to a group of onboarded servers. Makes all Windows server 2016 report "Enable Network Protection - Error -2147467259".
Does anyone know why and how to solve this issue?
Regards
Frederick
- Jan_LoddeCopper Contributor
FuriousFred Did you receive a response in the Escalated Ticket from Microsoft?
- Jan_LoddeCopper ContributorHello I have exactly the same issue with one of our clients. He has 2 identical systems Windows 2016 Terminal Server and only one reports the error "-2147467259" in the network protection area.
I have opened an escalated ticket with Microsoft as there is no information about the error code.
I would also be very interested in finding a solution here.- PJR_CDFIron ContributorIs Network Protection enabled in the server OS?
Have you followed the instructions here - https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/network-protection?view=o365-worldwide#network-protection-for-windows-servers- Jan_LoddeCopper ContributorWe have set the network protection in the Intune policy to "Audit Mode". This setting is apparently also transferred to the system (see registry).
However, an error is still displayed.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\Network Protection]
"AllowNetworkProtectionOnWinServer"=dword:00000001
"EnableNetworkProtection"=dword:00000002
"AllowNetworkProtectionDownLevel"=dword:00000001
- Tyler_SysadminCopper ContributorI've seen this, or a very similar error code in Intune/Defender for Endpoint several times now. In my case it seems infrequent and random. The configuration profile or compliance policy will work on >95% of systems but fail here and there with an error like this. I think it must be due to some kind of integer overflow, 2147467259 seems far too close to 2147483648 (half the maximum value of a 32bit integer represented in base 10) for it to be a coincidence.
I'd be very interested if anyone here knows more about these errors, especially if there is a way to avoid them.
Cheers,
Tyler