Microsoft Defender Device Onboard Local Script Device Limit

Question

Hello,

I would like to use the Defender Onboarding Local Script to onboard between 40 & 50 devices that failed to onboard with the Intune deployment method used for mass deployments.

It says that this type of deployment method can only be used on a device count between 1 & 10, but we would like to use it to onboard approximately 40-50 devices.

I know this is not recommended by Microsoft but is this a technically solution to use to help us close the device gap and what happens if we go over the 10-device limitation. I have already tested this on a couple of devices and it works but we want to be assured that if we deploy this to all devices (700+), 40-50 of those not onboarded, that this will do the job.

Thanks,

Shaun

Answer 1

That's right. Using the local script option is not a recommended choice for production. This is because the data reporting frequency is higher than other onboarding methods when onboarding using a local script. Microsoft suggests that this could have environmental impact.

I suggest investigating why those devices are not being onboarded with Defender. Utilize the methods recommended for mass onboarding, such as Intune, since you already use it. I'm sharing a few reference guides with you that might be helpful in resolving this issue.

1. Make sure you are meeting the Minimum License Requirements for on-boarding clients to Defender: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/run-analyzer-windows?view=o365-worldwide
2. Make sure you are meeting the Hardware and Software requirements on those devices that are not getting on-boarded: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/minimum-requirements?view=o365-worldwide#hardware-and-software-requirements
3. Run the Defender client analyzer tool on the device and Investigate the logs: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/run-analyzer-windows?view=o365-worldwide

If any of the above methods are not working, Log a Support ticket with Microsoft as it could be an issue at the backend.

--If the response is helpful, please click "Accept Answer" and upvote it --