I recently encountered a frustrating issue with a machine that was reset. The user used to log in with a local account, but after reconfiguration, it now requires Entra access for login. Since this change, the user can't connect to a VM via RDP. The issue arises because the RDP connection automatically appends the domain '@*****.com' to the username, which causes the login to fail. We've found a temporary workaround by signing in with 'username@invalid' to confuse the AzureAD UPN parser. However, I'm looking for a more permanent solution instead of having to do this workaround each time. By the way, we discovered a method where setting up the session in Moba and exporting the connection seems to bypass the Entra requirement.
3 Answers
To use a local login, try adding '.' in front of the username, like '.-admin'. This should help you log in properly without the domain getting appended.
Make sure to use '.' before the username to enforce a local login. Windows typically defaults to Entra or email credentials unless specified otherwise. This little tweak might save you some headaches!
You might want to try using 'MicrosoftaccountUPN' or your email as the username. Sometimes that works well for bypassing issues with directory credentials.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures