ATPHandler: Unexpected ConfigurationType, error when trying to onboard to Defender ATP using MECM

%3CLINGO-SUB%20id%3D%22lingo-sub-1996474%22%20slang%3D%22en-US%22%3EATPHandler%3A%20Unexpected%20ConfigurationType%2C%20error%20when%20trying%20to%20onboard%20to%20Defender%20ATP%20using%20MECM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1996474%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20onboard%20machines%20using%20the%20Microsoft%20Defender%20ATP%20Policies%20deployment.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20specified%20the%20onboarding%20file%20which%20I%20downloaded%20from%20Defender%20ATP%2C%20and%20I%20also%20specified%20the%20workspace%20ID%20an%20workspace%20key.%20I%20defined%20both%20the%20file%20and%20key%20because%20I%20am%20targeting%20both%20up%20level%20and%20down%20level%20clients%20in%20my%20collection.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20ATPHandler.log%20file%20I%20see%20the%20following%20error%20messages%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3EATPHandler%3A%20Unexpected%20ConfigurationType%2C%20%20ATPHandler%2016-12-2020%2020%3A55%3A35%203552%20(0x0DE0)%0AATPHandler%3A%20Failure%20in%20CATPHandler%3A%3AHandleUIPolicy%3A%200x80070057%20ATPHandler%2016-12-2020%2020%3A55%3A35%203552%20(0x0DE0)%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20on%20a%20down%20level%20client%20(Windows%20Server%202012%20R2).%20I%20followed%20the%20recommended%20steps%20from%20this%20manual%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fconfigmgr%2Fprotect%2Fdeploy-use%2Fdefender-advanced-threat-protection%3Fredirectedfrom%3DMSDN%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fconfigmgr%2Fprotect%2Fdeploy-use%2Fdefender-advanced-threat-protection%3Fredirectedfrom%3DMSDN%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20on%20a%202016%20machine%20I%20get%20the%20same%20error%20message.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20site%20version%20is%3A%26nbsp%3B5.00.9012.1000%3C%2FP%3E%3CP%3EThe%20client%20version%20is%3A%26nbsp%3B5.00.9012.1052%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%20I%20tried%20to%20recreate%20the%20entire%20policy%2C%20I%20even%20did%20a%20fresh%20download%20of%20the%20onboarding%20file.%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20can%20I%20do%20to%20further%20troubleshoot%20this%3F%20There%20is%20not%20much%20information%20to%20be%20found%20about%20this%20error%20message.%20I%20found%20one%20forum%20post%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fconfiguration-manager%2Funexpected-configurationtype-quot-error-when-attempting-to%2Fm-p%2F1810793%22%20target%3D%22_self%22%3Ehere%3C%2FA%3E%2C%20but%20that%20does%20not%20provide%20a%20solution%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1996474%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Edefender%20atp%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2014184%22%20slang%3D%22en-US%22%3ERe%3A%20ATPHandler%3A%20Unexpected%20ConfigurationType%2C%20error%20when%20trying%20to%20onboard%20to%20Defender%20ATP%20using%20MEC%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2014184%22%20slang%3D%22en-US%22%3EThis%20was%20resolved%20by%20simply%20waiting.%20It%20seems%20that%20the%20policy%20is%20not%20pushed%20out%20correctly%20at%20first.%20And%20then%20after%202-3%20days%20I%20started%20seeing%20devices%20onboarding.%20Very%20weird%20issue.%3C%2FLINGO-BODY%3E
New Contributor

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 workspace key. I defined both the file and key because I am targeting both up level and down level clients in my collection.

 

In the ATPHandler.log file I see the following error messages:

 

 

ATPHandler: Unexpected ConfigurationType, 	ATPHandler	16-12-2020 20:55:35	3552 (0x0DE0)
ATPHandler: Failure in CATPHandler::HandleUIPolicy: 0x80070057	ATPHandler	16-12-2020 20:55:35	3552 (0x0DE0)

 

 

 

This is on a down level client (Windows Server 2012 R2). I followed the recommended steps from this manual: https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/defender-advanced-threat-protectio...

 

Edit: on a 2016 machine I get the same error message.

 

The site version is: 5.00.9012.1000

The client version is: 5.00.9012.1052

 

So far I tried to recreate the entire policy, I even did a fresh download of the onboarding file. 

What can I do to further troubleshoot this? There is not much information to be found about this error message. I found one forum post here, but that does not provide a solution for me.

1 Reply
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.