Forum Discussion
AnuragSrivastava
Jan 05, 2021Iron Contributor
MDATP Windows 10 onboarding | Intune
Hi, I created a pilot group of 10 users and onboarded them to MDATP by creating Microsoft Defender ATP (Windows 10 Desktop) Configuration Profile in Intune. The users got successfully onboarded and ...
Thijs Lecomte
Jan 05, 2021Bronze Contributor
If there is a conflict you probably have a policy that also does onboarding (maybe an endpoint security one). But this should not impact the devices that you see in MDE.
Have you checked this script to see if you have correct connectivity? https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/configure-proxy-internet#verify-client-connectivity-to-microsoft-defender-atp-service-urls (needs to be done locally)
This provides some info on where to search for errors in the event viewer. What do you see here?
https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding
Have you checked this script to see if you have correct connectivity? https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/configure-proxy-internet#verify-client-connectivity-to-microsoft-defender-atp-service-urls (needs to be done locally)
This provides some info on where to search for errors in the event viewer. What do you see here?
https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding
AnuragSrivastava
Jan 06, 2021Iron Contributor
It was one of the conflicting endpoint security policy. I have deleted that now and now there are no machines with conflict status.
Still I could see 8-10 machines with pending status, any steps to troubleshoot the same.
- Thijs LecomteJan 07, 2021Bronze ContributorHave you checked the event viewers I linked before? As well as ran the connectivity tool?