Microsoft has confirmed in an email response that the fix is included in the 2010 HFRU. However, please note that this is not listed in the "Issues that are Fixed". I suggest that you independently confirm this with Microsoft.
Defender not Accepting AntiMalware Policy settings without access to AD
We are busy migrating from a third party antimalware product to using Defender. Our plan is to use System Center Endpoint Configuration Manger (or as I still like to refer to it, SCCM) to manage the application of policies as well as reporting on malware detections.
So far, in the labs, everything has been working perfectly, and we successfully followed Microsoft Learn on enabling SCCM infrastructure to deploy AntiMalware policies and monitor clients. Everything was working in the lab, and policies were correctly applied and testing with safe virus samples resulted in detection and reporting as desired. We then proceeded to test this in live environment, and it worked just as well.
When we started rollout, we experienced an issue where Defender would not 'activate' the AntiMalware policy that was deployed to the machines, unless the machines was on the office network or connected via VPN. As most of our machines are currently working remotely, and only come on VPN rarely, this is a big problem. We are using SCCM 2010, with a properly functioning Cloud Management Gateway to manage all of our machines. We confirmed that the machines all have the latest SCCM client.
The way I understand Defender to work is that when applying the policy, the policy added to the Registry, and then Defender will notice a chance to the registry and activate the changes it detects in the registry. It is the part of Defender activating the policy changes that is not working.
Troubleshooting showed that the SCCM client HAS applied the AntiMalware policy to the machine. This is shown by entries in the log file C:\Windows\CCM\Logs\EndpointProtectionAgent.log, as well as entries in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\EPAgent, as well as HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware.
Defender behaves the same way, no matter whether we deploy the AntiMalware policy to the machine before switching off the third party Antimalware (which auto enables Defender) or after. As long as the machine remains off the office network or VPN, Defender does not activate the policy settings at all.
If we apply the policy to the machine before removing third party antimalware, when it is on office network or on VPN, then as soon as Defender is enabled (even if this happens when computer is not in office or VPN), then Defender activates the custom settings from the AntiMalware Policy
I also found that the issue is not to do with SCCM deploying the policy, because Defender behaves in the same way if I export the AntiMalware Policy from SCCM to an XML file, and then manually import it using the command line "C:\Program Files\Windows Defender\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". Plus, as mentioned before, the policy itself IS getting applied, but Defender seems to ignore this until it has access to office network / VPN
I started looking at the Event Viewer and in the Windows Defender log, I tracked down the entries for Event Id 5007 (Windows Defender Antivirus Configuration has changed), and checked when it showed that it was activating the custom settings from the AntiMalware Policy. I then checked other logs in Event Viewer and noticed that when this happened, the machine was doing a Group Policy update. I repeated tests and found that Defender would only activate the AntiMalware policy settings if I was on office network / VPN and a group policy update happened.
This now makes sense as to why Defender will only activate the policy settings when it is on the office network or VPN.
I checked my GPOs in AD as well as GPRestult on the machines, and there is nothing that indicates blocking of Defender policies, or blocking of local computer policies.
Please can some assist me in getting this resolved, as our license for the third party antimalware is due to expire soon and this issue is the only thing holding us back from switching everyone to Defender. We cannot use Defender with its default settings due to a lot of custom exclusions we need to implement, and also wanting to lock down the settings in Windows and also stop users from being prompted what to do in the event of detection.
I did post a similar question (stupidly under another account) on this, but this was when I thought that the issue was the Cloud Management Gateway. I think my troubleshooting described above shows that it's something to do with Defender itself not activating the settings in the policy and not the application of the policy itself.
Windows for business | Windows Client for IT Pros | Devices and deployment | Configure application groups
2 additional answers
Sort by: Most helpful
-
Reza-Ameri 17,341 Reputation points Volunteer Moderator
2021-02-09T16:55:57.127+00:00 In case of Configuration Manage devices need to be within the company network, they have to be inside the network or connect through VPN.
In case you want to manage them over the internet, it would be best to consider using Intune.
You may consider deploying BranchCache too:
https://learn.microsoft.com/en-us/windows-server/networking/branchcache/branchcache
So when they connect to internet, they would authenticate with company's network and it is like they are inside company. However deploying BranchCache is complex. -
Teemo Tang 11,471 Reputation points
2021-02-10T06:29:51.3+00:00 “Defender would not 'activate' the AntiMalware policy that was deployed to the machines, unless the machines was on the office network”
Yes, it is a basic requirement. If we want to use Microsoft Endpoint Configuration Manager, most of the managed computers and servers are physically on the same internal network as the site system servers that perform management functions.
But, Configuration Manager provides two ways to manage internet-connected clients:
Cloud management gateway
Internet-based client management
Source:
https://learn.microsoft.com/en-us/mem/configmgr/core/clients/manage/manage-clients-internet-------------------------------------------------------------------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.