Jan 10 2019 03:52 AM
Jan 10 2019 03:52 AM
I'm started to make some tests on Intune, but I had some struggles to register machines and also to understand some what the system does in background.
I follow the steps from Microsoft page (Link) and I think there is everything setup correctly. I choose this method because we have Active Directory on-premise that is synchronize with Azure AD, so this is an Hybrid Active Directory.
Also I setup Intune connector to synchronize all machines that we had register on our Active Directory (on-premise) and after that I was able to see all my machines.
My first doubt is something related with this (probably). Once we've our machines register in our Active Directory (on-premise) and they are synchronized with Azure AD, why do I need to create a Organization Unit (OU) in our Active Directory (on-premise) with Delegation Control?
Another question that I have is about Autopilot Deployment. I run the script "Get-WindowsAutoPilotInfo" on my machine to import it on Intune AutoPilot (that was imported successfully) after the import I check the Azure devices and my machine was duplicated, as you can see on the screenshoot:
The differences on the screenshoot is the "Hybrid Azure AD Joined" that is the synchronization from Intune connector and the "Azure AD Joined" is from AutoPilot import. I supose that second register is because I created a Device Configuration Profile (like as said on the link that I follow), see the screenshoot:
Do I really need this profile, once I already have the machine registered on Azure AD?
Jan 14 2019 02:44 PM
I have this exact same issue, the device joins local AD, reboots I sign in, the device joins Azure AD and I end up with two devices in Azure AD. One shows as Azure AD and the other as Hybrid Azure Joined. I also noticed that the Company Portal fails to recognise the device is joined and the user is not shown as the owner in Azure AD.
Jan 15 2019 06:02 PM
Jan 16 2019 09:09 AM
Jan 16 2019 12:45 PM - edited Jan 16 2019 12:46 PM
this is the message I received from Intune Support As you requested, below are the details regarding the process of setting up Hybrid Azure AD join support for Autopilot:
1. Intune 1810
2. Windows 10 with October 2018 update
3. Successfully configure Hybrid Azure Active Directory Join for Managed Domains
4. Federated domains are not supported at this time
Jan 21 2019 10:31 AM
Jan 26 2019 03:07 AM
My Company has a federated domain, ADFS configured in Azure AD Connect and uses Windows Autopilot Hybrid Azure AD join without issue
Jan 26 2019 08:47 PM
Jan 26 2019 08:49 PM
Jan 29 2019 11:36 PM
Jan 30 2019 02:19 PM
Jan 30 2019 11:03 PM
Jan 30 2019 11:17 PM
You mean that problem?
Yes I am encountering this issue for a few days now. I contacted MS Support they are working on it, but they did not tell me it is an ADFS/Hybrid AAD issue.
Jan 30 2019 11:19 PM
Jan 30 2019 11:25 PM