- #REMOTE DESKTOP CONNECTION WINDOWS 10 HOW TO#
- #REMOTE DESKTOP CONNECTION WINDOWS 10 WINDOWS 10#
- #REMOTE DESKTOP CONNECTION WINDOWS 10 PRO#
#REMOTE DESKTOP CONNECTION WINDOWS 10 WINDOWS 10#
Figure 1 shows these two remote desktop clients side-by-side on a current Windows 10 desktop. Another is the newer Remote Desktop, a Universal Windows Platform app that Microsoft calls URDC, with package name Microsoft.RemoteDesktop_.0_圆4_8wekyb3d8bbwe. One is the old, familiar Terminal Server-based Remote Desktop Connection (RDC), also known as MSTSC for its executable name mstsc.exe. Upvote if it does.Ever need to access a computer remotely? It’s easy to do in Windows 10, but Microsoft has provided a few different ways to get there. HTH other people who run into this post while searching. In any case, this should be in the docs for Remote Desktop Access - Microsoft PMs I hope you monitoring recent replies and are able to fix this in future Windows updates (add docs, and detection for this case). Remote client can send your password hash which matches the one stored locally on the machine. This type of setup (PIN from start) does not create a password hash which I assume is what RDP client uses to authenticate you in a remote session, so the step 3 (log out and log back in with a password) is what fixes it on the local machine and then This would be the same case if you use Windows Hello, Fingerprint reader or other similar deviceĢ. When I setup the machine I immediately setup login PIN during initial process and have been using it ever since instead of password. MACHINE_NAME\user1, Password: your_MSA_passwordġ. After this I was able to login from Remote Desktop client on a Mac using the following: User: Log back in using password for your MSA (not PIN, fingerprint or anything else)Ĥ. Usern local user as the above post describes.ģ.
I have observed that other users with longer names like are truncated to
To verify run user manager: Start + R: lusrmgr.msc. I verified that my user (me) is in the Remote Desktop Users group (this gets setup automatically in step 1). The machine was setup to use MSA from start, there is no specially created local user except the "administrator" that gets createdĢ.
#REMOTE DESKTOP CONNECTION WINDOWS 10 PRO#
I enabled the Remote Desktop Access on my Windows 10 Pro machine while logged in as Microsoft Account (MSA) user. I run across this thread in the search of the answer and the following worked for me.ġ. I am not sure why the RDP can not authenticate the hotmail credentials that must be stored somewhere against the account? As it has no issue using these credentials when logging in to the machine locally. Hopefully this example makes sense and is clear on what I am trying to achieve. However if I was to username " johnc" and password "mypassword" then it would autheticate and connect me fine as it can recognise the shortened system generated username in What I couldn't work out is why the user was only able to make a connection using thier shortened username as per the internal user that windows created automatically when the hotmail profile was created.Īs an example say my hotmail account was called " a nd password "mypassword" if i tried to RDP using username " "mypassword" I would received a username and passsword could not be authenticated error in the remote desktop connection dialog.
#REMOTE DESKTOP CONNECTION WINDOWS 10 HOW TO#
I am ok with how to configure the system to allow remote sessions and also how to assign users to the correct group in order for them to connect.