Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, July 30, 2015 3:26 PM | 2 votes
I get this message when i try to access my Win 10 Pro computer from my Win 10 Home computer using the Remote Desktop Connection App. I can access the Pro computer from a Win 7 computer i have and i can access a Win 7 Pro computer from my Win 10 Home computer.
Please help; thanks.
All replies (4)
Friday, July 31, 2015 8:36 AM ✅Answered | 1 vote
Hi,
According to the error message, this can be account problem. Please follow steps below for test:
Open Remote Settings in System of Win 10 PRO, then check Allow remote connection to this computer.
Another method you can use was that add "Remote Desktop Users" to the users that are allowed to log on to the terminal server using remote desktop.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Friday, July 31, 2015 7:04 PM ✅Answered
You can't use Azure AD accounts for RDP'ing currently - there hasn't been any timeline as to when this functionality will be added.
Personally, Azure AD is a pain - it makes itself look like a regular domain join, but it's really not. It's unfortunate that Microsoft hasn't made the distinction clearer between a regular domain join and Azure AD join. As a workaround, remove the system from Azure AD, and re-join the normal way. This will allow RDP'ing into your machine like you want.
Hope that helps!
Friday, July 31, 2015 6:21 PM
I have been able to remote desktop from one to another as long as I use a local user on target machine. However, what I want to do, which is a capability that will positively advance AAD adoption, is to be able to joine both pc's, say PC1 and PC2 to my AAD domain. Then on PC1 I log on as global admin and try to connect to PC2 with my global admin username - that does not work and I have been told by MS Support it is not supported yet- can you confirm this as MS Support is basically like a million people with differing competencies - so just casting a wide net on this as it is a critical feature from my perspective regarding the goal of using AAD as your sole "domain controller in the sky"
Thursday, August 25, 2016 4:12 PM | 1 vote
You can't use Azure AD accounts for RDP'ing currently - there hasn't been any timeline as to when this functionality will be added.
Personally, Azure AD is a pain - it makes itself look like a regular domain join, but it's really not. It's unfortunate that Microsoft hasn't made the distinction clearer between a regular domain join and Azure AD join. As a workaround, remove the system from Azure AD, and re-join the normal way. This will allow RDP'ing into your machine like you want.
Hope that helps!
This shouldn't be marked as an answer because the original poster never mentioned Azure at all. It might apply to Heschelpop's post, but not the original poster's.