Let’s learn more about the Windows Autopilot Hybrid Domain Join Step by Step Implementation guide. This post will learn details about the Windows Autopilot Hybrid Domain Join scenario.
In most Windows Autopilot deployments, Windows 10 or Windows 11 machine is Azure AD joined. But the majority of the organizations still rely upon On-premise on-prem Active directory join.
Hybrid Azure AD is domain joined plus Azure AD registered devices. So you will need to have connectivity to the on-prem active directory, and you also will need to have additional components such as Intune Connector for Active Directory.
Following are some of the basic posts related to Windows Autopilot. Hopefully, these posts will help you to start the Windows Autopilot journey.
1. Beginners Guide Setup Windows Autopilot Deployment
2. Dynamically Deploy Security Policies and Apps to Windows Autopilot Devices
3. Where is Autopilot Assign Profile Button in Intune Portal
4. Windows Autopilot End to End Process Guide
5. Repurpose/Reprovision Existing Devices to Windows Autopilot
6. Windows AutoPilot Profile AAD Dynamic Device Groups.
7. Windows Autopilot License Requirements
Why are we talking about Hybrid Azure AD Join? Hybrid Azure AD Join is the same as Hybrid Domain join when your on-prem Active Directory is synced with Azure AD using AAD Connect.
There are many dependencies to have on-prem Active Directory or domain join Windows 10 Devices.
NOTE! – In this post, Hybrid Azure AD Join is referred to as Hybrid Domain Join and Domain Join.
Dependencies are mainly for Group policy and Application authentication (Legacy – mainly NTLM). Many organizations want to adopt a new deployment using Autopilot.
- But at the same time, they also wish Windows 10 to be part of Active Directory.
Microsoft introduced the “Hybrid Azure AD or Hybrid Domain Join” deployment to meet the above criteria. You can deploy a Hybrid Autopilot profile from Intune.
- With this solution, we can provision Windows 10 using Intune, and the computer will be joined to On-premise Active directory as well.
This is a series of posts as listed below.
- Hybrid Azure AD join Architecture and How to setup Windows Autopilot from Intune Portal (This Post)
- Hybrid Azure AD join Autopilot – Troubleshooting Tips
Windows Autopilot Hybrid Domain Join Setup Architecture
Following the high-level architecture flow of Windows, Autopilot Hybrid Domain join setup architecture.
Windows Autopilot Workflow – Hybrid Azure AD Join
This section will see 12 steps workflow of the Windows Autopilot Hybrid Domain Join scenario.
- User Receive the Windows 10 Autopilot enabled computer from OEM or IT.
- User switches on the computer. The Computer connects Autopilot service and downloads a hybrid Autopilot profile (Windows Autopilot Hybrid Domain Join Profile).
- The user goes through the Autopilot OOBE and sign-in using the corporate account.
- Computer enrolled to Intune. Offline domain join configuration profile Deployed from Intune. Then Computer asks for an Offline domain to join the blob.
- Intune communicates with Intune AD connector. Intune AD connector installed in your on-premise server for offline domain join blob.
- Intune AD connector communicate with AD and create offline domain join blob.
- AD connector sent back the offline domain join blob to Intune.
- Intune sent the offline domain join blob to the device.
- The Computer applies the offline domain join blob and restarts—the user’s login with an AD credential.
- Intune deploy policy and apps to computer. (Enrollment status page – Optional).
- User prompted to log in using domain credential—the Group policies deployed from Active Directory. Intune also pushes policies in the back-end.
- User login and ready to work
Prerequisites for Hybrid Autopilot Setup
The Prerequisites for Windows Autopilot Hybrid Domain Join are divided into server and client-side.
- Configured hybrid Azure Active Directory join.
- Windows 10 automatic MDM enrollment enabled
- Windows Server 2016 or above (To Install the Intune AD Connector)
- Internet connectivity on Intune Connector for Active Directory Server.
- If there are any Internet proxies, make sure you go through this article.
Note: It is recommended to configure Intune AD connector to bypass the on-premises proxy.
- Windows 10, version 1809 or later.
- Internet access. The Proxy rule should be applicable for the client-side and the server-side in the Windows Autopilot Hybrid Domain Join scenario.
- Connectivity to Active Directory and domain controller during deployment.
VPN connection to On-prem AD is not supported. VPN connection to on Prem AD is Supported now.
Hybrid Autopilot Configuration Steps
Let’s check the configurations required for Windows Autopilot Hybrid Domain Join setup into two. In this post, we will go through these configurations in detail.
- On-premise configurations
- Cloud configurations (Intune)
There are two configurations required as part of on-premise configurations.
- Setup Intune AD Connector (Intune Connector for Active Directory)
- Delegate Permissions
Intune AD connector (Intune Connector for Active Directory)
Following are the Intune AD connector requirement. Make sure that you have all the needs in place before the implementation.
- The Intune Connector installation requires Windows Server 2016 or later.
- Intune Connector Server should be able to communicate with Active Directory.
- Intune Connector Server must have access to the internet. If you have a proxy in your environment, please follow the proxy recommendations.
- In production, For High availability, Consider multiple servers with connectors.
- If you have any Active Directory domains in your environment, consider a connector for each part.
- Intune AD connector server system locale should be set to English US.
How to Configure Intune Connector for Active Directory
The following steps will help you complete the Intune AD connector configuration (Intune Connector for Active Directory) for Windows Autopilot Hybrid Domain Join scenarios.
- Login to Intune Console.
- Select Device enrollment > Windows enrollment > Intune Connector for Active Directory > Add connector > Click on the download Connector setup file.
ODJConnectorBootstrapper.exe will be downloaded.
Copy the ODJConnectorBootstrapper.exe to Server designated to host Intune Connector for Active Directory.
Install the executable ODJConnectorBootstrapper.exe.
Click Browse if you want to change the default installation path.
Select Configure after successful Intune AD connector installation
Select Sign In.
NOTE! – Sign in using Global Administrator or Intune Administrator user. Please ensure the admin has Intune license assigned.
Intune Connector for Active Directory gets enrolled. After a few minutes, Intune AD connector server starts communicating with Intune cloud service.
NOTE! – For Intune connector Installation logs, you can navigate to below path. C:\Users\userid\AppData\Local\Temp\Intune_connector_for_Active_Directory_<Year>
You can refer to the below log for more details on Installation.
NOTE! – After Signing in, Intune connector will start communicating with your Azure tenant. It takes less than 5 minutes for the connector to appear in the Intune console. Navigate to the below path to see all the connectors in your environment. Also, you can verify the latest Intune connector sync timestamp.
Delegate permission for Intune Connector for Active Directory
The Offline Domain Join Connector service is responsible for creating Computer Objects. Offline Domain join Connector acts as a mediator.
Offline Domain join Connector service communicates with on-premise Active Directory and Intune cloud.
As shown in the below picture, the Connector service works with the local system account. Hence the server computer object (SERVERNAME$) must have permission to create the computer objects in AD.
NOTE! – By default, all domain accounts have permission to join a maximum of 10 computers to AD. To change this default behavior, you need to delegate permission. Let’s configure the permission.
- Launch Active Directory Users and Computers (DSA.msc).
- Right-click the organizational unit and then select Delegate Control.
Select “Next” to continue.
In the Delegation of Control wizard, add your Intune connector server computer object.
Select Create a custom task to delegate > Next.
Select the Computer objects, Create selected objects in this folder, Delete selected objects in this folder checkboxes, and select the Next button to continue.
Under Permissions, select the Full Control check box as shown below.
You have completed the permission delegation for the Intune AD connector to create Offline Domain join blob for Windows Autopilot Hybrid Domain Join Scenario.
Intune cloud Side Configurations
This section will go through different configurations required within the Intune console for Windows Autopilot Hybrid Azure AD Join (Windows Autopilot Hybrid Domain Join) scenario.
Intune Autopilot Profile Configuration
The following configurations will help you configure the Windows Autopilot hybrid domain join scenario.
- Login to Intune, select Device enrollment > Windows enrollment > Deployment Profiles > Create Profile.
- Type a Name and, optionally, a Description.
- For Deployment mode, select User-driven.
- In the Join to Azure AD as box, select Hybrid Azure AD joined.
- Select Out-of-box experience (OOBE). Configure the OOBE options as needed and create a profile.
On the profile page, select Assignments. And Select groups.
In the Select group pane, select your device group. Please make Autopilot computer hardware ID imported and added to the device group.
Intune Configuration Profile – Hybrid Domain Join
This section will go through three(3) configurations for Windows Autopilot Hybrid Domain Join. These configurations define in three(3) settings.
- Computer naming template
- Domain name
- Organization Unit path
- In Intune, select Device configuration > Profiles > Create Profile.
- Select Windows 10 and later.
- Profile type: Select Domain Join.
- Provide a Computer name prefix, Domain name, and (optional) Organizational unit in DN format.
Notes from the Field:
#1 – Please ensure the Organization unit is in DN format. If there is any typo, your computer will be stuck with the message “Please wait while we set up your device.” I will cover this in my second post. If you don’t update the Organization unit, the default computer container is used.
#2 – Hybrid autopilot supports computer naming using the prefix. You cannot use variables such as %SERIAL%. If you use variables, then you will get the error message “Something went wrong” with code “80180005” or “80070774“. I will explain this in my second post.
- Assign the profile to the Autopilot device group.
CSP to Disable User Setting in ESP
Below CSP configuration will prevent this timeout error. In my second post, I will explain the Windows Autopilot Hybrid Domain Join Troubleshooting Tips. Let’s go through the steps to configure this CSP.
./Vendor/MSFT/DMClient/Provider/MS DM Server/FirstSyncStatus/SkipUserStatusPage
Navigate via Intune blade – Create a profile – Settings – Configure – Custom OMA-URI Settings – Windows 10 and later – Add OMA-URI settings.
Assign the CSP to the Autopilot device group.
(Optional) Turn on the Enrollment Status Page
It is recommended to enable the Enrollment status page. For more details, refer here.
Results – Windows Autopilot Hybrid Domain Join
After completing Windows 10 deployment using Hybrid Autopilot, you will get below Login screen. As seen below, you can log in to the computer using an AD Domain user account.
After login, you can verify whether your machine is a Hybrid domain join or not by executing the below command.
In my second post, we will go through events and logs that help troubleshoot.
- Windows Autopilot Video Starter Kit
- Beginners Guide Setup Windows AutoPilot Deployment
- Dynamically Deploy Security Policies and Apps to Windows AutoPilot Devices
- Where is AutoPilot Assign Profile Button in Intune Portal
- Windows AutoPilot End to End Process Guide
- Windows Autopilot Deployment Scenarios – On-Prem Hybrid Domain Join