Manish, amazing video. Question: Is there any other way to ease the process of grabbing the Identifier at scale? doing for hundreds of devices manually will be quite a work.
Sir , please make SCCM real time scenario based issues and steps to solve them. Like Action Cycles missing, updates stuck with installing status, application stuck with installing,patch not reflecting in software center. This will be very helpful for beginners like me.🙏
HI @ManishBangia, Thank you so much for making this video. After you added the device corporate identifier to Intune, could you please clear this that how the device which was at the OOBE screen will be able to get the device preparation profile.
Autopilot device preparation profile will not be offered automatically until unless it is configured. But the initial experience of OOBE will be same till username / password is entered (either for autopilot device prep. or Microsoft Entra join without any profile).
Which method is best practise for a corporate environment? Since we are having only corporate Windows devices, personal enrollment restriction set to Block and having our vendor uploading most of the device hashes, I still don't get the complete idea behind this? This seems to work when some specific user wants to join the personal device but not prefferable for bulk?
For corporate environment, the best option should be to block the personally owned devices. Determining corporate device should be done via: 1. Uploading hardware hash (For Autopilot v1) 2. Uploading Windows corporate Identifier (For Autopilot v2)
Thanks Manish. One question, If I upload the Corp Identifier to Intune, will the device allows me to perform Azure AD join ? or simple no login to device with no Autopilot ? so I can extract Hardware hash of the device to use Autopilot v1?
Azure AD Join (Microsoft Entra join) has no relation to Intune enrollment. For joining the entra id, you need to allow Microsoft entra join which can be accessed via Azure portal > Microsoft Entra ID > Device settings > Allow Microsoft Entra join
1st like 1st view thank you so much sir
Manish, amazing video.
Question: Is there any other way to ease the process of grabbing the Identifier at scale? doing for hundreds of devices manually will be quite a work.
Just keep an eye on posts and discussion, probably soon there might be created by someone, currently I am not aware of this.
Sir , please make SCCM real time scenario based issues and steps to solve them.
Like Action Cycles missing, updates stuck with installing status, application stuck with installing,patch not reflecting in software center. This will be very helpful for beginners like me.🙏
Will try
HI @ManishBangia,
Thank you so much for making this video.
After you added the device corporate identifier to Intune, could you please clear this that how the device which was at the OOBE screen will be able to get the device preparation profile.
Autopilot device preparation profile will not be offered automatically until unless it is configured. But the initial experience of OOBE will be same till username / password is entered (either for autopilot device prep. or Microsoft Entra join without any profile).
Hi Sir, Thanks a lot. How to create a Dynamic Device to Rule to grab only the corporate identifier registered device?
Which method is best practise for a corporate environment? Since we are having only corporate Windows devices, personal enrollment restriction set to Block and having our vendor uploading most of the device hashes, I still don't get the complete idea behind this?
This seems to work when some specific user wants to join the personal device but not prefferable for bulk?
For corporate environment, the best option should be to block the personally owned devices. Determining corporate device should be done via:
1. Uploading hardware hash (For Autopilot v1)
2. Uploading Windows corporate Identifier (For Autopilot v2)
Thanks Manish. One question, If I upload the Corp Identifier to Intune, will the device allows me to perform Azure AD join ? or simple no login to device with no Autopilot ? so I can extract Hardware hash of the device to use Autopilot v1?
Azure AD Join (Microsoft Entra join) has no relation to Intune enrollment. For joining the entra id, you need to allow Microsoft entra join which can be accessed via Azure portal > Microsoft Entra ID > Device settings > Allow Microsoft Entra join
@@ManishBangia thanks, let me check this out.
@manish Bangia hello sir can we do per user per device binding so that user can not logged in to another device
This can be achieved by enabling Device Platform Restrictions.