Forum Discussion
Christian_Montoya
Jul 17, 2019Microsoft
[Announcement] Connectivity issues from synchronized users to VMs joined to AAD DS
Hi everyone, thanks for the continued testing of WVD. We’ve seen multiple connection errors with UPN when connecting to VMs joined to Azure AD Domain Services. We’ve done some preliminary investigati...
- Nov 04, 2019
Christian_Montoya : A fix has been rolled out to production for this issue.
jeffb8
Brass Contributor
Any update on a resolution? This is a hard blocker for us.
The workaround only works with NEWLY CREATED users - meaning I cannot delete a Windows Server AD user, then recreate with the same username as an Azure AD sourced user. It seems like Windows Virtual Desktop permanently stores the upn and sid in its database....so deleting and recreating the user in Azure AD doesn’t help...
The workaround only works with NEWLY CREATED users - meaning I cannot delete a Windows Server AD user, then recreate with the same username as an Azure AD sourced user. It seems like Windows Virtual Desktop permanently stores the upn and sid in its database....so deleting and recreating the user in Azure AD doesn’t help...
Christian_Montoya
Aug 07, 2019Microsoft
jeffb8 Richard Harrison Integral-Consulting rhythmnewt Alex Ignatenko : Hi everyone, apologies for this thread going a bit quiet. We've done investigations and started implementing the fix, but will take time to roll into production. Once I get a better date, I will reach out here so you all can continue your testing!
Since we roll out in phases, I'd highly recommend setting up a host pool for validation, as this will be the first place to test.
Again, thanks all and we're definitely trying to get this fix rolled out as soon as we can.
- rhythmnewtAug 07, 2019Copper ContributorThank you for keeping us informed!
- jeffb8Aug 07, 2019Brass ContributorThanks. Is there an eta for when a fix will be available to host pools in validation mode?
If not, is there any way to submit a support request to get you to delete stale user accounts from your sql azure database or is this exposed in any way? It would at least allow us to proceed with testing if there was a way to recreate the user accounts with problems. As I mentioned above - today we can’t even delete/recreate the user. It has to be created as a cloud only user with a different upn...