Domain Join Intune Not Applicable
Intune ad connector communicate with ad and create offline domain join blob.
Domain join intune not applicable. That is no longer the case thanks to cloud computing platforms such as azure and intune and other mdm service provers. Next you must assign the policy to users or devices. You can navigate to below location and analyze the log while troubleshooting.
Offline domain join connector domain join device config profile intune can anyone shed any light on what s failing here or at least point me in the direction of some sort of troubleshooting log files please. Check the netsetup log to check whether computer received offline domain join blob from intune or not. If you re unable to sign in to the intune connector for active directory then turn off ie enhanced security configuration for the administrator.
The computer applies the offline domain join blob and restarts. Ad connector sent back the offline domain join blob to intune. Give your profile a name select the platform as windows 10 or later and the profile type to domain join.
A non domain joined computer was restricted to the status of being in a lowly workgroup in which every machine was an island unto itself. Intune ad connector installed in your on premise server for offline domain join blob. From an administrator perspective the event viewer on the server running the connector will show event id 30140 in the log odj connector service from the source odj connector service source with a successful creation of the computer object.
A domain join configuration profile includes on premises active directory domain information. Any help greatly appreciated. Enter a computer name prefix the domain name and the ou in distinguished name format.
It used to be that a non domain joined status meant isolation. Intune sent the offline domain join blob to the device. That makes perfect sense as the domain join profile must come via microsoft intune.