Forum Discussion
An internal error occurred / can't connect anymore
- Please set-up a validation pool as we have a fix deployed to the validation pools. Learn here how to set those up: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-validation-host-pool We recommend to make use of Azure Service Health Alerts where you will be notified when the fix is available for production: https://docs.microsoft.com/en-us/azure/virtual-desktop/set-up-service-alerts
evasse Unfortunately we cannot deploy to Validation ring because the machine fails to join the domain. We are using the same script as to deploy to prod ring (which has no issues to join the domain) with the only difference being the
15:10:25 - Resource Microsoft.Compute/virtualMachines/extensions 'rmrvwval4-0/joindomain' failed with message '{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'joindomain'. Error message: \"Exception(s) occured while joining Domain '{sanitized}.com'\"."
}
]
}
}'
Deleted Please review our troubleshooting section under https://aka.ms/wvdpreview. We have articles on that as well.
evasse I looked over the troubleshooting steps but none of it applies, we deploy to a new resource group in the same vnet, same region, same source image as our production ring. If I create the new host pool with -ValidationEnv $False flag then there is no problem with domain join, and the only issue is the SID error on connection.