Just after the setup, you may have quite few errors/warnings while the connector tries to register. You can also check the service Intune ODJConnector ServiceĪ Windows event log – ODJ Connector Service – is also available below the Applications and Services Logs Once your connector has been successfully registered it will display in the Intune Connector for Active Directory blade Once installed click on the Configure Now button this will launch the connector registration process – use either a Global Administrator or an Intune Administrator account NOTE with the preview ensure you have English US language only You need to ensure the Autopilot OU is sync with Azure AD.ĭownload and install the Intune ConnectorĪccess the Intune\Device enrollment\Windows enrollment\Intune Connector for Active Directory (Preview) blade to download and add a connector. You need to ensure your Mobility option (MDM/MAM) is set to Intune and targeted users are part of the MDM user scope (from the Azure Active Directory\Mobility (MDM and MAM) blade).ĭelegate the create and delete actions (using the Create custom task to delegate option) for Computer objects to the OU where the Autopilot, with Full control to the computer hosting the connector. NOTE this is also currently being rolled out so if you are missing all or some of these options you will need to wait a little.
Off course, to get it working you need to ensure the device will be connected to your corporate network to be able to access your Active Directory to make the join operation. Now (currently in preview – so there could be some glitch and may change), you can assign an Intune profile to your Windows 10 devices to join your Active Directory domain.
It has been quite a limitation so far for Windows 10 managed with Intune it was impossible to get them to join an Active Directory domain using Autopilot, making these devices Azure AD Hybrid joined devices.
0 kommentar(er)
