Forum Discussion
VMs not being added to host pool or AD
I've been provisioning session host monthly for the last year or so, but this month it started to fail. If I use the portal to add session host to a host pool, the VMs get created but most do not ge...
Take this:
- Check VM Image: Ensure that the VM image you're using is correctly configured and doesn't have any issues. Since you've tried using an older golden image, it might be worth creating a new image from scratch to rule out any image-related problems.
- Verify Network Connectivity: Ensure that the VMs have the necessary network connectivity to reach the Azure Virtual Desktop service and the domain controllers. Check for any network issues or firewall rules that might be blocking communication.
- Review Logs: Check the logs for the RDagent and RDagent bootloader installation. Look for any error messages or warnings that might provide more insight into why the agents are not being installed.
- Check Azure AD Join Configuration: Verify that the Azure AD join configuration is correct and that the VMs have the necessary permissions to join the domain. Ensure that the domain join account has the required permissions.
- Update VM Extensions: Ensure that the VM extensions, such as the Azure Virtual Desktop agent and bootloader, are up to date. You can manually update these extensions if needed.
- Use Custom Script Extension: Consider using a custom script extension to manually install the RDagent and RDagent bootloader during the VM provisioning process. This can help ensure that the agents are installed correctly.
- Check for Recent Changes: Review any recent changes in your environment, such as updates to policies, configurations, or permissions, that might be affecting the VM provisioning process.