Feb 17 2021 08:26 AM
Feb 17 2021 08:26 AM
Hello, are there any plans on improving tools for policy conflict resolution? With so many areas to configure duplicate policy settings it can be confusing to resolve these conflicts as they happen. I can't click into the policies that are shown in conflict, or the settings, without looking around for where those policies are. It would be helpful to click the policy and be taken directly to where it is configured so that we can more easily resolve it.
For example I have a policy in conflict currently, with a ticket open for the issue, which is EDR conflicting with the built in onboarding policy for instance. I can't dig into the onboarding policy at all, and the only thing configured with EDR is to enable sample sharing for all files. That settings is set to not configured on the Defender ATP Sensor Configuration Policy (all that is configured there is Microsoft Defender for Endpoint client config package type being set to onboard) and that's about all the insight I have into the settings.
Additionally, are there plans to extend features available for Server 2016/2019 to Server 2012 R2 or are we expected to upgrade our environments if we want to be able to take actions against them in the ATP portal
Feb 17 2021 09:07 AM
@BrandonD930 great questions.
1. How did you set the policies? Through MEM? Right now, if two policies conflict, MEM will show an error. We have conflict resolution on the roadmap, but I don't have a specific timeline to share at this point.
2. Yes for Server 2012 R2 - there is work in progress to get to feature parity with the capabilities that are available for Server 2019.
Feb 17 2021 09:17 AM
@Maayan Bar-Niv Thank you for the response! :)
1) Yes, I had started with the Security Baselines inside MEM in the overview area, then quickly realized that setting further more narrowly scoped policies up inside Endpoint Security would cause massive conflicts as policies clashed. I removed all the baseline policies and have defaulted to configuring items individually to try an eliminate any conflicts. That was working well, as I had zero conflicts, until very recently when the issue I spoke of above came about. No changes were made to any policies, I've just been rolling more machines into my Test Pilot. I should also mention that we are co-managed between SCCM 2002 and Intune with a pilot group of around 270 machines currently. Better troubleshooting tools would be much appreciated :)
2) Good to know that features are coming to bring feature parity across all currently supported products :)