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.
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.
- Please like the comments which were helpful and mark one as solution to mark this topic as solved
- I'm trying to sign in with the global admin account now. Everything seems to have joined ok, and behaving as expected. The only issue now will be getting the individual apps to install as needed, but that's another issue. Thanks!
- Ah, the default location from SBS, good (old) times 😉 And yes, I don't know if a reset also works for the Computer account in AD. But removing is always better...
But... Are things ok now? Please like the comments which were helpful and mark one as solution to mark this topic as solved - I removed the OU entry in the Domain Join policy since that is optional. Our DC is setup to automatically add newly joined computers to the MyBusiness\Computers\SBSComputers\New OU.
I just used the Fresh Start feature in Intune since the device record was there, but I was stuck with that App failure, and couldn't reset from that point. The Fresh Start worked really well. It removed the device from Intune, but now it's back trying to setup again and there's a new device object in Intune.
I also just checked my AD, and there's a new device object in there as well. Something to keep in mind if someone uses Fresh Start. They need to remove the computer object in AD, otherwise there will be duplicate devices in there for each time you reset a device. - Ok, what were the settings in the domain profile? ou=Computers, ou=Company, dc=mycompany, dc=com instead of ou=Computers, ou=Company, dc=mycompany, dc=local?
- 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. - Curious! 🙂
Harm_Veenstra I was finally able to pull up a command prompt during enrollment. I was able to confirm I can ping both the on-prem DC, and the URLs for Intune and Azure. It doesn't appear to be an issue with connectivity. I'm going to review the logs to see if there's anything I'm missing.
- Yeah if I can get to a cmd prompt during enrollment, that would make a world of difference in troubleshooting. Unfortunately I just haven't been successful in doing so yet. Thanks for your time, and have a nice weekend!
- 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