This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 54%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
The article https://learn.microsoft.com/en-us/windows/client-management/connect-to-remote-aadj-pc shows how to connect to an AAD joined PC from another AAD joined PC.
I have followed these instructions and I cannot connect. The LENOVO ThinkCenter Edge machines are both brand new installs of Windows 10 updated to 10.0.19042.928 and registered to AAD with the same user. For testing, both PC are on the same network and have 10.6.2.xx IP's. Wireshark shows that the PC's can connect to each other. Remote Credential Guard has not been enabled.
The Remote Desktop slider in new settings doesn't go to "on" no matter what I do, there is a thread about that here: https://social.technet.microsoft.com/Forums/en-US/e694929c-6b89-4691-b75d-dc9ff57b8e49/remote-desktop-wont-stay-enabled?forum=win10itprosetup
It is no longer possible in the later version of windows to access the System Properties without running Sysdm.cpl from a command prompt.
The standard "can't connect" error shows. Remote users now connected to Azure AD cannot work remotely.
We are transitioning from on premise domain. RDC is still working fine to the remaining domain computers. There isn't a problem with the network.
Can anyone advise?
Need to change Network from Public to Private..
cant-enable-remote-desktop-in-windows-10-pro
If this answer or any other one solved your issue, please mark it as accepted which would be much more efficient for other community members to find useful information.
Let us know if further assistance is required.
@Spencer Thompson
Thank you for your time and patience throughout this issue and I'm glad that you were able to resolve this! Please feel free to mark your answer as accepted so others in the community experiencing this issue can easily find this.
Thank you again!