join
2 TopicsAVD Re-join AzureAD / EntraI
Hi everybody, I have an issue that I accidently did a "dsregcmd /leave" on my Azure Virtual Desktop machine. The environment is Cloud Only so I don't have an Active Directory onprem. As today everything worked good but I had to move the AVD to another subscription. The login for the users didn't work anymore so I tried differtent things and the last one was the dsregcmd /leave. One of the worst decicions of my life. Does anybody have an idea how I can rejoin this VM back to Entra without creating a new VM? There are several applications with many custom changes so that a new VM would be the worst. I tried dsregcmd /join /debug which ended in error code DsrCLI: logging initialized. Cannot start Task: 0x80041326 Failed to schedule Join Task. Error: 0x80041326 DeleteFileW returned 0x80070002. I tried dsregcmd /forcerecovery /debug which ended in the error code CAA50024 and DsrCLI: logging initialized. DsrCmdRecovery::DetermineIfRecoveryIsNeeded: DsrGetJoinInfoEx returned no join information. DsrCmdRecovery::DetermineIfRecoveryIsNeeded: Forcing return of S_OK instead of S_FALSE. DsrCmdRecovery::DetermineIfRecoveryIsNeeded returned 0x00000000 (NEED RECOVERY). DsrCmdRecovery::NotifyUser returned 0x00000000. The command az vm extension set --publisher Microsoft.Azure.ActiveDirectory --name AADLoginForWindows .. gave me an feedbach with "Succeeded" but did't change anything. How can I rejoin this device to Entra so that the users can login with their Entra Identities again? Because it is a multi-session-AVD I don't have the options to join this device to entra in Settings > Accounts..... I hope someone can help me with this problem.Solved718Views0likes3CommentsAVD Domain Join Errors
Just curious of other people are seeing errors during domain join when creating a new AVD pool in ARM, but when the VM's are checked they were successfully joined. I have seen this several times in the last three months. What it looks like to me is that the template in the ARM tries to perform the join while the new VMs are coming out of Sysprep, throws the error message, then later successfully joins the VMs. The one time I did get into a VM that had this error, I was able from within the VM using a Bastion connection, join the computer to the domain using the same service account credentials I had specified in the ARM.2.6KViews0likes0Comments