Forum Discussion

Copper Contributor

Jun 28, 2019

Solved

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...

evasse
Jul 03, 2019
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

rhythmnewt

Copper Contributor

Jul 16, 2019

Roop_Kiran_Chevuri I sent you identifiable details about my user account and domain in a PM.

My setup is as follows On-Prem AD -> Ad Sync -> AAD -> Azure ADDS

I do have password write-back enabled.

I do NOT have multiple On-Prem AD instances.

I do have multiple stand-alone AAD (cloud-only) instances.

VM in question is domain-joined to my Azure ADDS instance and I have no problem authenticating into it with my domain credentials.

Thank you for looking into this.

Roop_Kiran_Chevuri

Microsoft

Jul 17, 2019

rhythmnewt Thanks for sharing this detail. Its very helpful to understand the setup. We have recently introduced a change where we need User SID's from VM and token to match before we allocate a session. There seems to be a case with AADDS where they may not always match. We are currently investigating how do we handle these scenarios. I will keep you posted on progress.

MarkMiddlemist_Mercato
Copper Contributor
Jul 18, 2019
Roop_Kiran_ChevuriGlad to hear there is a fix underway. Can you provide us at least a rough ETA please. We are currently investigating moving some of our systems to WVD but right now our investigations and POCs have had to go on hold because of the broken resource templates and now this.

Can you also please comment as to when this service will be covered under full support and SLA if clients such as ourselves are looking to go to market,

Thanks in advance

Mark
rhythmnewt
Copper Contributor
Jul 17, 2019
Thanks for the update, I hope the fix comes soon!
Roop_Kiran_Chevuri
Microsoft
Jul 17, 2019
We have identified a bug when are in this setup. This is now documented here : https://techcommunity.microsoft.com/t5/Windows-Virtual-Desktop/Announcement-Connectivity-issues-from-synchronized-users-to-VMs/m-p/759642#M1036 . We are actively working to fix this.