Event details
Hello Team,
With Autopilot Device Preparation, I always recommend customers disable personal devices from enrolling to Intune and thus Device Preparation requires these Corporate Device Identifiers to be uploaded to Intune. Is this the recommended approach? If so, would there be any easier ways to get the Corporate Device Identifiers uploaded to Intune? Right now, it requires that you manually pull it (similar to Hardware Hash) and requires device intervention.
Appreciate it in advance!
- Pearl-Angeles
Community Manager
Thanks for your participation in today's AMA. The panelists covered this topic around 44:13.
We previously used QuickCreate HyperV wizard with offline JSON provisioning (the JSON file injected into the Windows folder inside the VMDK). Today, we cannot offer this service any longer, because this offline JSON provisioning is no longer supported. We were told to use Corporate Identifiers, but it requires device intervention as YesaitRavanty said, because you need to pass the Corporate Device Identifier to the Intune Admin so that he/she adds it to Intune.
YesaitRavanty : there is no recommended approach as of today, as Device Prep seems still in early days : no device renaming (MS : yes, we understood that labeling on device name is bad. It is however useful when talking to your IT colleagues about A-devices, T-devices and C-devices, for Admins/Teachers/Classmates for example), no GroupTag (means there is no persistent variable, that is kept across new Windows OS reinstallations, like for example creating rings of devices using EntraID groups), no OOBE customization to bypass the privacy questions, and no much ability to recognize some basic company branding when device boots for first time so that you feel welcome.
