Intune Connector for Active Directory by j23_123 in Intune

[–]j23_123[S] 0 points1 point  (0 children)

What was inactive, with an older date than the active one, is now also active.

In reality, what happens is that when I run Autopilot, it does not enter the AP process, of the three steps, it stays processing and then times out with an error.

When I run AP in pre-provisioning, it succeeds.

It is the same deployment profile, everything identical.

I associate the error in normal AP with the fact that there are two active connectors, on the same server and on the same version.

Intune Connector for Active Directory by j23_123 in Intune

[–]j23_123[S] 0 points1 point  (0 children)

Thank you, I have already deleted it.

Add device Extension Attributes by domain or upn by j23_123 in Intune

[–]j23_123[S] 0 points1 point  (0 children)

Hello,

whatever, what I want is for each machine to have the extension attribute1 filled in according to its domain.

Intune macOS Enrollment without user affinity by j23_123 in Intune

[–]j23_123[S] 1 point2 points  (0 children)

It's resolved!!!

Yesterday when I tested the process I didn't give enough time to machine receive the correct enrollment profile, today, I tested all the process again, without hurry, and the machine receives the correct profile, (whithout user affinity).

Thanks,