Windows 10: C# unable to enroll a device using graph

I hava a powershell function that calss a C# function app to enroll a device in Autopilot. I can't get it to work. I quite sure the problem lies with the hardware identifier binary blob. I tried every string format but I always get the same errorHere's how the hardware identifier is retreived in powershell $devDetail = Get-CimInstance -CimSession $session -Namespace root/cimv2/mdm/dmmap -Class MDM_DevDetail_Ext01 -Filter "InstanceID='Ext' AND ParentID='./DevDetail'" if $devDetail -and -not $Force { &nb

:)

 

Enrolling Android Device in Intune - Google Account?

After doing my own research it appears this depends on what kind of Android device you want to enroll. Starting with:

• Set up Android Enterprise work profile enrollments
• Set up Android Enterprise dedicated device enrollments
• Set up Android Enterprise fully managed enrollments

In my case, I wanted to enroll a fully-managed device:

Enroll Android Enterprise dedicated, fully managed, or corporate-owned work profile devices in Intune - Microsoft Intune

According to the above documentation:

*Admins or users are to: (5) On the Google sign-in screen, enter afw#setup instead of a Gmail account, and then choose
NEXT.*

The next step is to scan or input the Android enrollment token - Intune blade (Azure portal) > Device enrollment - Android enrollment > Android enrollment (under Manage) > Corporate-owned, fully managed user devices (Preview)

 

Windows audio device graph isolation problem

Hello,

Windows Audio Device Graph Isolation is an official part of Windows and serves as the primary audio engine in Windows 10. It handles the audio enhancement effects provided by Windows. If you are using any enhancements, we suggest that you disable them and
see if the sounds stops. You may disable your enhancements by following the steps below:

• Right-click the Volume icon in the Taskbar.
• Click Sounds.
• From the Sound window, click the Playback tab, then select the device that you suspect is causing the issue.
• Click Properties.
• On the Enhancements tab, click the Disable all enhancements checkbox.
• Click OK.

 

Unable to enroll Device into Azure AD using 3rd Party On-Premise MDM

Turns out this is a known bug by the 3rd Party MDM provider (mobileiron) and there is a simple fix for it. These are a combination of regex entries[0-9] appended to URI parameters. This fix applies only to the latest Windows 10 Builds i.e from 1809, 1903 upwards that were impacted. So anyone enrolling with the latest builds (i.e 1809 updwards)should get in touch with their mobileiron provider for this fix immediately.

The temporal workaround in my case was to roll back to 17134 and earllier windows builds, tested and finally works as expected. I am in touch with Mobileiron regarding these Regex entries.

Follow this link for further details -> Unable to enroll Device into Azure AD using 3rd Party On-Premise MDM for solution.

in a nutshell if you want to avoid this error message in your test environment whiles waiting for the permanent fix from Mobileiron just roll back to the earlier windows version as stated above and go through the configuration and enrollment steps once again as a workaround. Should work.