https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# microsoft-365
s
This message was deleted.
n
@Kasper Johansen or @James Kindon: Any chance either of you have come across this before? It's failing at the join phase, and there isn't much more info than this.
k
Is the device AD identity synced to Entra ID?
n
I'm told it is, yes. Actually just found a CTX article that looks like it may be relevant: https://support.citrix.com/article/CTX475187/windows-11-vda-machines-stuck-at-initializing-for-azure-ad-or-hybrid-azure-ad
Yep, that was it. It's now hybrid joined.
ANd here I was blaming Microsoft.
😂 1
They can still kiss my pasty white ass, though. 😄
😂 2
r
LMAO
r
Well reading that it is a Microsoft issue.
Do your feeling is still valid 😝
n
I will accept that, ha!
I was going to ask tomorrow anyway, but in case somebody else has an opinion, any reason why we would not run dsregcmd /leave in our master image while sealing - for both persistent and non-persistent? The latter for sure, but persistent is still new to me for AAD/O365.
r
I think its a requirement if your using mcs to deploy
n
Interesting. We've never done that in any of our persistent images in the past. I'll have to add it to my finalization script.
r
I still do it but via BIS-F. But in the case the master OU is not synced with Entrap ID connect. But I do it as a fail safe anyways to ensure it's (master image) not AADHJ by mistake.
That also may explain why I haven't ran into this yet. Because all my hybrid joins were 2308+. Unless I'm misreading the Verbiage.
n
In case anyone else stumbles across this later, my solution ended up being adding the registry value via GPP, letting Microsoft's native tasks, etc. handle joining AAD. So far, it has worked well.
Open in Slack
PreviousNext
Powered by