Event banner
Windows Office Hours: March 21, 2024
Event Ended
Thursday, Mar 21, 2024, 08:00 AM PDTEvent details
Get answers to your questions about adopting Windows 11 and managing the Windows devices used by remote, onsite, and hybrid workers across your organization. Get tips on keeping devices up to date ef...
Char_Cheesman
Updated Mar 21, 2024
reastman1966
Mar 18, 2024Brass Contributor
I am looking for some insight on what could be happening with enrolling into Intune. This is for a few devices but have 500+ successfully enrolled in Intune and Autopatch. This is Auto Enrollment using GPO's
Devices are Active Directory and Entra ID joined. Everything shows up fine in the Azure portal. Dsregcmd /status shows they are joined, and all the pertinent information is there. When I look at these devices in Intune, they are showing pending, and they are showing not registered in Autopatch. In Event Viewer Applications and Services Logs/Microsoft/Windows/DeviceManagement-Enterprise-Diagnostics-Provider/Admin shows Event ID 75
What ends up in Intune All Devices Device name shows the user that enrolled then _Windows_date. It shows it is managed by Intune, Not evaluated, prirmay user and then Intune registered is Pending. Doesn't seem to matter how long or who logs into the device.
The other issue I have is the IntundODCStandAlong.ps1 file has errors when it runs listed below
PS C:\Users\Workday3941> wget https://aka.ms/intunexml -outfile Intune.xml
PS C:\Users\Workday3941> wget https://aka.ms/intuneps1 -outfile IntuneODCStandAlone.ps1
PS C:\Users\Workday3941> powerShell -ExecutionPolicy Bypass -File .\IntuneODCStandAlone.ps1
At C:\Users\Workday3941\IntuneODCStandAlone.ps1:25 char:10
+ b,
+ ~
Missing argument in parameter list.
At C:\Users\Workday3941\IntuneODCStandAlone.ps1:38 char:15
+ button, input, optgroup, select, textarea {
+ ~
Missing argument in parameter list.
At C:\Users\Workday3941\IntuneODCStandAlone.ps1:62 char:9
+ }
+ ~
Unexpected token '}' in expression or statement.
At C:\Users\Workday3941\IntuneODCStandAlone.ps1:67 char:9
+ }
+ ~
Unexpected token '}' in expression or statement.
At C:\Users\Workday3941\IntuneODCStandAlone.ps1:78 char:9
+ }
+ ~
Unexpected token '}' in expression or statement.
At C:\Users\Workday3941\IntuneODCStandAlone.ps1:87 char:9
+ }
+ ~
Unexpected token '}' in expression or statement.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingArgument
- AllieWolfMar 21, 2024Occasional ReaderI struggled with GPO based hybrid join for a bit. In my case it was licensing. Not every user in my org gets an F3 or higher so several devices were pending enrollment until a licensed user account logged into the machine. We purchased some stand alone Intune device licenses to make up the difference.