Creating a VM from a generalized image and adding it to an Azure Virtual Desktop (formerly Windows Virtual Desktop) host pool involves a few steps, and there are some common issues that might cause the VM not to appear in the host pool. Here are some troubleshooting steps to follow:
Image Generalization: Ensure that the VM image was successfully generalized before creating the new VM. Generalization is a process that prepares the VM for duplication. You can generalize a VM using Sysprep (Windows) or waagent (Linux).
Custom Script Extension: If you're using a custom image, make sure that it includes the necessary configurations and extensions to join the Azure Virtual Desktop host pool. You might need to run custom scripts during VM provisioning to ensure it's correctly configured.
Agent Registration: Check if the Azure Virtual Desktop agent is installed and correctly registered on the new VM. The agent is responsible for connecting the VM to the host pool. You can review the agent's status and logs for any errors.
Network Configuration: Ensure that the VM has the necessary network connectivity to reach the Azure Virtual Desktop service. Check for any network issues or firewall rules that might be blocking communication.
Registration Token: Verify that you've configured the host pool correctly and used the correct registration token when creating the new VM. The registration token is necessary for the VM to associate with the host pool.
VM Pool Assignment: Make sure that the new VM is assigned to the correct VM pool within the host pool configuration. VMs are associated with specific pools.
Diagnostic Logs: Check the Azure Virtual Desktop diagnostic logs and events in the Azure portal for any errors or issues related to VM registration and pool assignment.
Update Configuration: If you've made changes to your VM image or host pool configuration, ensure that these changes are correctly reflected in the new VM.
If you've gone through these steps and are still experiencing issues, it might be helpful to review the Azure Virtual Desktop documentation and consider reaching out to Azure support for more specific assistance with your setup. Troubleshooting Azure Virtual Desktop configurations can sometimes be complex, and support can provide tailored guidance based on your specific environment and setup.