Forum Discussion
ATPHandler: Unexpected ConfigurationType, error when trying to onboard to Defender ATP using MECM
I am trying to onboard machines using the Microsoft Defender ATP Policies deployment. I specified the onboarding file which I downloaded from Defender ATP, and I also specified the workspace ID an ...
This was resolved by simply waiting. It seems that the policy is not pushed out correctly at first. And then after 2-3 days I started seeing devices onboarding. Very weird issue.
- This is such a weird behavior. I had the same thing happen. After waiting 2-3 days, the devices starting showing compliant and were successfully onboarded into MEM. I did onboard one Windows Server 2012 R2 and it was successful within an hour or two, so this behavior with needing to wait a few days may only be with Windows 10 devices, and probably Windows Server 2019.
