I'm working with AVDs running on Windows 10 Enterprise for Virtual Desktop and need to migrate them to Azure AD Join. After switching the VM from domain to workgroup, I attempted to join Azure AD through the 'Access work or school' option, but the '+' button didn't show up. I read somewhere that my image doesn't support Azure AD Join. I also tried using the 'AAD Login for Windows' extension and set the necessary IAM roles. While RDP worked, the AVD agent didn't. I then ran `dsregcmd /leave`, which left me unable to log in, as the VM is neither domain-joined nor Azure AD joined. Can anyone advise me on how to recover this locked-out VM? What is the recommended process to migrate AVDs to Azure AD, and is there a suitable image for AAD-joined AVDs? Thanks a lot!
3 Answers
It's crucial to treat your VMs more like cattle instead of pets. Customizing your images and utilizing FSLogix and OneDrive for user data can help avoid such lockout issues in the future. But for now, you may need to look for a supported AVD image that can work with Azure AD Join.
Thanks for the karma, folks! But seriously, consider utilizing the AVD-Accelerator for a more structured implementation. You want a solid base image tailored with your necessary software, sysprep it, and save it to an image gallery. That way, new session hosts can easily be derived from this image. I know this doesn't help you right now, but having a sustainable setup is the way to go!
The safest approach is probably to create new VMs from scratch using an appropriate AVD image. You'll have an easier time managing those in the long run. An infrastructure-as-code setup can really help with flexibility too! Installing everything anew might seem like a hassle, but in the end, it can save you from these kinds of issues down the line. Just a thought!
I get that, but many AVDs are already live, and clients are using them. I could snapshot the disk, but then I'd need to reinstall everything, which is a lot of work. Plus, some users have data directly on the C drive.