Android client can't login to WVD (spring 2020)

%3CLINGO-SUB%20id%3D%22lingo-sub-1497822%22%20slang%3D%22en-US%22%3EAndroid%20client%20can't%20login%20to%20WVD%20(spring%202020)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1497822%22%20slang%3D%22en-US%22%3E%3CP%3EI%20try%20to%20use%20Android%20client%20version%2010.0.6.1048%20.%3CBR%20%2F%3EWe%20have%20synchronized%20on-premise%20AD%20and%20Azure%20AD%2C%20but%20we%20have%20different%20domain%20names%20for%20users.%3CBR%20%2F%3EThe%20Android%20client%20can%20pass%20through%20the%20first%20half%20of%20log%20in%20with%20my%20Azure%20AD%20account%2C%20but%20when%20client%20try%20to%20go%20next%20step%20it%20fails.%20I%20see%20the%20appeared%20window%20with%20suggestion%20to%20write%20password%20again%20but%20I%20can't%20use%20on-premise%20AD%20account%20name%20because%20the%20client%20use%20only%20Azure%20AD%20user%20name.%20There%20is%20no%20possibility%20to%20change%20user%20name%2C%20because%20it%20is%20blocked.%20It's%20strange%20because%20in%20similar%20situation%20for%20WEB%20client%20we%20can%20use%20different%20users.%3CBR%20%2F%3EHow%20can%20I%20use%20Android%20client%20for%20users%20with%20different%20domain%20names%20for%20on-premise%20and%20Azure%20AD%3F%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1502275%22%20slang%3D%22en-US%22%3ERe%3A%20Android%20client%20can't%20login%20to%20WVD%20(spring%202020)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1502275%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F57619%22%20target%3D%22_blank%22%3E%40Sergey%20Osherov%3C%2FA%3E%26nbsp%3BIs%20this%20working%20well%20with%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fconnect-windows-7-and-10%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EWindows%20Desktop%20client%3C%2FA%3E%3F%20There%20are%20some%20restrictions%20to%20ensure%20that%20the%20AD%20Account%20used%20is%20the%20same%20as%20the%20one%20that%20was%20synchronized.%20Trying%20to%20see%20if%20this%20is%20an%20issue%20specific%20to%20the%20Android%20client%20or%20if%20it%20might%20be%20the%20way%20things%20are%20configured.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I try to use Android client version 10.0.6.1048 .
We have synchronized on-premise AD and Azure AD, but we have different domain names for users.
The Android client can pass through the first half of log in with my Azure AD account, but when client try to go next step it fails. I see the appeared window with suggestion to write password again but I can't use on-premise AD account name because the client use only Azure AD user name. There is no possibility to change user name, because it is blocked. It's strange because in similar situation for WEB client we can use different users.
How can I use Android client for users with different domain names for on-premise and Azure AD?   

3 Replies
Highlighted

@Sergey Osherov Is this working well with the Windows Desktop client? There are some restrictions to ensure that the AD Account used is the same as the one that was synchronized. Trying to see if this is an issue specific to the Android client or if it might be the way things are configured.

Highlighted

@David Belanger  The Windows Desktop Client works good, but not works with Android client.

Highlighted

@Sergey Osherov 

 

I get this also, it sucks as WVDI hasn't got full sso capability yet with out ADFS, and our business has not implemented any SSO at all, so we rely on Azure AD for login to the WVDI service and on prem AD for Domain login to the Virtual Machines. The Android Client seams to be the only one that dosnt prompt correctly for the domain login. The Client caches the Azure AD username and dosnt let you change it, at the point it authenticates the VM login.

 

This is a simple fix, on vm authentication just do not disable the text box and allow people to put in a different user name. This is two mins development work but actually means the Android client becomes usable.

 

Thanks

 

Lee