Forum Discussion
gdglee
Jun 28, 2019Copper Contributor
An internal error occurred / can't connect anymore
We've been running WVD succesfully for a few months, but since this morning my users cannot login anymore. Not through the desktop and not through the webclient. The desktop client returns 'An intern...
- Jul 03, 2019Please 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
sbuntun
Jul 08, 2019Brass Contributor
JanPijnacker evasse This is true for us as well.
rmaddron
Jul 09, 2019Copper Contributor
evasse - anything new on this? All of my client's IDs are sourced from on-prem AD > AADC > AAD. The error remains on my existing pools, and based on the feedback here - suspect it will with a validation pool deployment. Moving to cloud only IDs isn't really an option
Can you provide any more detail on what leads to this condition?
- richiewrtJul 09, 2019Copper Contributor
This started working for me yesterday without any intervention on our part. I did notice that the RDS Infrastructure Agent updated on 7/3/19 to 1.0.833.5