In this video tutorial, the presenter discusses how to perform a Windows autopilot hybrid join. The key steps and points covered in the video include:
1. Explanation of what a hybrid join is: Joining a Windows PC to Azure AD, enrolling it into an MDM (Mobile Device Management) solution, and then joining it to an on-premise domain controller.
2. Prerequisites for a successful hybrid join: The PC must have a way to contact the on-premise domain controller, and the domain controller should be running Windows Server 2016 or above.
3. Common issues and errors: The presenter mentions common issues such as blue screen errors during the join process and explains how to overcome them.
4. Configuration steps: The video demonstrates the following steps:
- Creating an Organizational Unit (OU) in Active Directory for InTune to join machines.
- Configuring permissions for the OU to allow InTune to write to it.
- Installing the InTune connector for Active Directory.
- Configuring Azure AD Connect for device registration and right-back to the on-premise domain controller.
5. Group Policy creation: The presenter creates a group policy to register devices in Azure AD.
6. Configuration Profile creation: A configuration profile is created for Windows 10 devices, specifying settings such as the computer name and OU for joining.
7. Deployment Profile creation: A deployment profile is created for the Windows PC, specifying settings like the user, language, and the need to skip AD connectivity checks.
8. Enrolling the PC: The video shows the process of enrolling the PC in InTune and setting it up for autopilot.
9. Final verification: The video concludes with a demonstration of the PC successfully joining the domain and becoming a hybrid-joined device.
The presenter also mentions the need for patience, as it may take some time for devices to appear correctly in Azure AD after the initial join.
Here are the key facts extracted from the provided text:
1. Windows Autopilot hybrid join allows a Windows PC (Windows 10 or 11) to be joined to Azure AD, enrolled in an MDM, and joined to an on-premise domain controller.
2. To perform hybrid join, the machine must have a way to contact the domain controller, which should be running Windows Server 2016 or above.
3. Some people have encountered blue screen errors when attempting this process.
4. The text provides instructions on how to correctly set up Windows Autopilot hybrid join, including creating an OU, delegating control to the domain controller, installing the InTune connector, and configuring Azure AD Connect.
5. It mentions the importance of configuring Group Policies and Azure AD Connect for device registration.
6. The text guides the reader through the steps of creating deployment and configuration profiles in InTune for hybrid join.
7. It demonstrates the process of registering a device with InTune, including PowerShell commands and user credentials.
8. The text shows the device successfully joining the domain, becoming a hybrid Azure AD-joined machine.
9. It mentions that it may take some time for Azure AD Connect to consolidate the hybrid-joined machine with the Azure AD-joined machine.
10. The process successfully demonstrates how to set up a machine for Windows Autopilot hybrid join.