This is useful when we have to enroll device in bulk for example educational devices. You have to create 1 package to enroll the device in bulk.This package is vaild for 6 months because the token will be expired after 6 month.
In case of Bulk enrollment you have to ensure that user with package name (user created during bulk enrolment package creation ) should be part of MDM scope. If MDM scope is set for all users then no action required. Let me know, in case you are looking for something else.
@@ChanderManiPandey Hi Chander, thanks for your response. So I have added package user in a dynamic group and this group is a part of MDM user scope. However, after installing the provisioning package, the device is getting joined to Azure AD but not getting enrolled in Intune.
Thanks for your response. Yes the package name user has Intune license assigned to it and tenant has Azure AD P1 license. Turns out that it only works when MDM user scope is set to All. Anyways thanks for your help. Much appreciated
@@ChanderManiPandey should we include other files in the folder that's created along with .ppkg? or just the .ppkg whose file size is around 10KB will do?
In this video I am showing, How to do Bulk enrollment of Windows 10 / 11 Device in Microsoft Intune using Windows configuration Designer (WCD)
😊
Very Good Understanding ThankYou.
Is the number of device we can enroll using BERT is still 1000?
No device limit.
Only limit is bulk token expiration which is 180 day maximum
When you create the Bulk package for install. You need create 1package per 1user correct ? Or 1 package can use for multiple users ?
This is useful when we have to enroll device in bulk for example educational devices.
You have to create 1 package to enroll the device in bulk.This package is vaild for 6 months because the token will be expired after 6 month.
Did you say 1000 or 2000 devices can be enrolled with bulk enrollment?
Hi @directedbypuma its 1000 devices
Could you also tell what is the value of MDM user scope set under Automatic Enrollment?
In case of Bulk enrollment you have to ensure that user with package name (user created during bulk enrolment package creation ) should be part of MDM scope.
If MDM scope is set for all users then no action required.
Let me know, in case you are looking for something else.
@@ChanderManiPandey Hi Chander, thanks for your response. So I have added package user in a dynamic group and this group is a part of MDM user scope. However, after installing the provisioning package, the device is getting joined to Azure AD but not getting enrolled in Intune.
Please check if the user you used to enroll the device has Microsoft Intune license and Azure AD Premium license assigned?
also have you enabled MAM ?
Thanks for your response. Yes the package name user has Intune license assigned to it and tenant has Azure AD P1 license. Turns out that it only works when MDM user scope is set to All. Anyways thanks for your help. Much appreciated
How can I copy the .PPKG to a USB and run it on a machine without going through the OOBE? Thanks!
Format the USB drive and Copy the .PPKG file you created to the root directory of the USB drive and Apply the .PPKG on the Target Machine
@@ChanderManiPandey should we include other files in the folder that's created along with .ppkg? or just the .ppkg whose file size is around 10KB will do?
Good question.
Yes Only .PPKG
can i use this way to onboard windows server?
Intune is not for server
will it reset the device?
No