Forum Discussion

Christian_Montoya's avatar
Christian_Montoya
Icon for Microsoft rankMicrosoft
Jul 17, 2019
Solved

[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...
DubC85's avatar
DubC85
Copper Contributor
Sep 27, 2019

ArthurOpenhost 

That's not helpful to those of us who would rather not have to deal with ADDS and AD Connect unnecessarily.   

ArthurOpenhost's avatar
ArthurOpenhost
Copper Contributor
Sep 27, 2019

DubC85 Maybe i wasn't clear but i went from :

On-prem AD + AADConnect + AADDS (WVD VM being joined to AADDS)
-> was stuck with this bug for several months

 

to : 


On-prem AD + AADConnect + On-prem AD extended to Azure vNet (WVD VM being joined to AD)
-> everything worked on the first try

  • jaycrumpgp's avatar
    jaycrumpgp
    Brass Contributor
    Sep 30, 2019

    ArthurOpenhost 

     

    Yep, this works great, and has since the beginning (adding a hostpool that's actually on your on-prem domain and not AADDS joined).  I didn't even add a DC out in the Azure vnet - just joined on-prem domain over the S2S tunnel.

     

    I wish I could use that - I would be six months ahead now.  The smaller attack surface of available users (filtered sync to AADDS) will be required for us.

Resources