Forum Discussion
No logged events from ODJ connector service on Windows Server 2022
- Making some progress now. I don't know why it all of a sudden started working, but I did change my domain join profile back from mycompany.com to mycompany.local and that seemed to work. I was presented with the "Setting up your device for work" window and made it all the way to the Device setup - Apps section when it finally failed.
I have since removed all apps from Intune that I wanted to pre-load onto the device, with the exception of Company Portal and M365 apps. If those successfully install after the device reset is complete, then I will start adding each additional app individually until there is a failure.
Should be able to ping --> You verified that it is possible from both LAN / WLAN?
Shift-F10 should work, FN-Shift-F10 perhaps?
When we used to manually join the new workstations to the domain, we would go through the steps in the Network ID section of Windows Advanced System Properties. This requires putting in the FQDN of the domain on the network (companyname.local), and then entering the creds of a user who is authorized to add devices to it.
Because this works in the way described above, this leads me to believe that the DCs are visible to any connected device on the network. The only thing I can think of is, because I have no way to specify what the domain FQDN is on the new device during the enrollment process, the device isn't able to find the DC, but I thought that information would be provided from Azure and the Intune connector.
- If it's a laptop, try connecting a USB keyboard... I think it's just FN-Shift-F10... But if you can join AD using the same network cable... It should be alright, I guess...
The machine, when it's deploying, talks to Intune. Intune knows the machine is deployed using the Hybrid Deployment profile and knows which OU. It asks for a blob from Active Directory, which the machine running the connector from the Domain Controller fetches. The machine uses that blob to Domain Join... That should be the process if I'm correct... Does the connector machine have good access to AD (If it's Domain Joined, I guess yes 😉 ), and are all the permissions in AD setup correctly?Harm_Veenstra All permissions should be setup correctly. The server is a domain controller with AD, so there shouldn't be any issue there.
This is a laptop, but I haven't had any issues with the keyboard for entering the creds at the beginning of the enrollment process. Not sure why it's not allowing a command prompt.
I did read somewhere that you can only do that during the device stage and not the user stage? Not sure if that is correct, or even applies.
When we've joined workstations in the past it has been with either an ethernet cable, or over the wireless LAN connection. There's never been an issue there, but that's a different process.
I'm still thinking there's an issue either with the device not having line of sight with the DC, or there's a problem with the ODJ Connector. That appears to be the stage I'm stuck at.
- If you can choose the keyboard layout during setup, you should be able to press the keys.. And it's one of those too, but you can also ping the device from the Domain Controller if you know what IP address it got from DHCP