The user account used to try to connect to remote pc did not work. When attempting to connect from the Mac when NLA is disabled I receive "The During this configuration however, the Mac Remote Desktop Client will not connect to the desktop screen when remoting into the recipient machine.
If I disable NLA on the recipient (host pc) and change the connecting (local) RDP file to include enablecredssp:i:0 and then connect, NLA is bypassed and I can connect to the logon screen to enter in the username and password of the AAD account which accepts When I use my work email address (that is used to join that windows PC to AAD) I receive " The credentials that were If you are signing in to your work account, please use your work email address". Tells me that "Remote machine is AAD joined. If I try to use a variation of the AzureAD\username format it If I leave NLA enabled on the recipient (host) pc, I can connect to it via any remote desktop client I have tried if I use the credentials of a local account that exists on that recipient pc. More on the windows to windows connection: That is why I wanted to know under what requirements and use case the MAC remote Desktop App was tested when 10.2.1 was released that specifically supported the use of remoting Every instance I find in theseįorums (and others) that talk about it disable NLA on the windows recipient (host).
Regarding the windows to windows connection I have never been able to get this to be successful either. No I have not tried with any previous version of the Mac Remote Desktop App prior to 10.2.9. Please supply the conditions that were used to validate the release with the accommodations made for AzureAD in release 10.2.1 Like most others I have tried all combinations of username I can think for clarification, the AzureAD is literally supposed to represent AzureAD and not or conotosoAAD correct?
So even if NLA is disabled on the Windows 10 host, I don't see an option to address this on the MAC version and have been unable to connect vis the MAC version in any other way. In that combination I have gotten windows Remote Desktop client to work, but the MAC version won't as Iĭon't believe the MAC version supports the credssp option as indicated in the "Remote Desktop URI Scheme" (). The prevailing advice going around is that NLA must be disabled to connect via Remote Desktop and also disable credssp. Is there any information regarding the supported configuration for the (receiving) windows 10 azure ad joined pc host? The MS supported scenarios in the link above speak about leaving NLA enabled and I cannot find anyone that confirms that they have gotten To connect to an AAD joined PC, your username must be in one of the following formats: “AzureAD\user” or addition, we addressed some bugs affecting the usage of smart cards in a remote session.īeing that the MS page does not even acknowledge that the Microsoft Remote Desktop app is a supported scenario () I was surprised to see that this was already addressed in In this release we enabled connectivity to Azure Active Directory (AAD) joined PCs. Never successfully accepts the login information.
Unable to remote into Win 10 pro machine with Mac Remote Desktop client 10.2.9.