Following PR #58 too. That patch had one extra ability that your main branch doesn't have yet: omitting the username field.
Without this field, the RDP window opens and asks the password for the last authenticated user on the device, or to switch to another user, within the joined domain. Well it looks exactly like the authentication screen in front of the actual computer.
Random image to exemplify:
The current behavior, with this field, is to always ask for username and password, with undefined domain.
Random image to exemplify:
Note that I'm connecting to AAD-joined devices from personal (non-AAD-joined) device. FTR, the username is indeed AzureAD\email@domain like shown on the second image. The corresponding config is
UsernameTemplate: '.\AzureAD\{{ username }}'
(no idea why .\ is required) and the following defaults are needed
authentication level:i:2
enablecredsspsupport:i:0
as documented on many websites. I think these info are valuable and should appear on the README.
Following PR #58 too. That patch had one extra ability that your main branch doesn't have yet: omitting the
username
field.Without this field, the RDP window opens and asks the password for the last authenticated user on the device, or to switch to another user, within the joined domain. Well it looks exactly like the authentication screen in front of the actual computer.
Random image to exemplify:
The current behavior, with this field, is to always ask for username and password, with undefined domain.
Random image to exemplify:
Note that I'm connecting to AAD-joined devices from personal (non-AAD-joined) device. FTR, the username is indeed
AzureAD\email@domain
like shown on the second image. The corresponding config is(no idea why
.\
is required) and the following defaults are neededas documented on many websites. I think these info are valuable and should appear on the README.