Forum Discussion
Solved
Device Status when enrolled - Error
I have couple of questions.
1. I have defined the Configuration Profile for Domain Join profile and mentioned the
Computer name prefix -
Domain Name
Organizations Unit
But, it seems to be not joining the domain and it is not taking the prefix instead it is giving its own prefix as DESKTOP-blahblah
2. Under All devices it shows Error under "DEPLOYMENT STATUS", what am I doing wrong here?
3. It was showing as "Waiting for Install status'
oryxway, there's a lot that may be going awry here. Your screenshots show issues with hybrid join and app deployment.
- Assuming you're trying to hybrid join here (as that's what that configuration profile is for), may we also assume you've set up hybrid join in your AAD following these docs?
Configure hybrid Azure Active Directory join - Microsoft Entra | Microsoft Docs - Assuming this screenshot shows the device status for the "Domain Join" profile. Can you see any details else when you click on the error row?
- This screenshot seems to show app installations. That's completely unrelated, in my opinion, but it does make me suspect there's some other things that may be misconfigured. .
I suggest you troubleshoot things one step at a time, making sure each element works before moving adding the next.
- Assuming you're trying to hybrid join here (as that's what that configuration profile is for), may we also assume you've set up hybrid join in your AAD following these docs?
oryxway, there's a lot that may be going awry here. Your screenshots show issues with hybrid join and app deployment.
- Assuming you're trying to hybrid join here (as that's what that configuration profile is for), may we also assume you've set up hybrid join in your AAD following these docs?
Configure hybrid Azure Active Directory join - Microsoft Entra | Microsoft Docs - Assuming this screenshot shows the device status for the "Domain Join" profile. Can you see any details else when you click on the error row?
- This screenshot seems to show app installations. That's completely unrelated, in my opinion, but it does make me suspect there's some other things that may be misconfigured. .
I suggest you troubleshoot things one step at a time, making sure each element works before moving adding the next.
- My concern is that when I enable this in Azure AD Connect (which is not enabled) will it affect all the devices OnPrem?
We are only wanting the new OOBE devices joining the Hybrid Azure ADAADConnect will not affect your existing, on-prem devices (unless you tell it to do so
). Are you sure you need to hybrid join, though? I would suggest you simply try to work with AAD joined devices, and only start looking into hybrid joining if you really need to.
- Assuming you're trying to hybrid join here (as that's what that configuration profile is for), may we also assume you've set up hybrid join in your AAD following these docs?
