![]() Would you please clarify the part “ which seems to auto login by itself”? With the "no password" setup i get immediatly disconnected by the local machine which seems to auto login by itself after connecting via RDP. Yes, I have tested this, more specifically, remotely connect to a Windows 10 machine from a Windows 8.1 machine. The important part here is not about connecting from a Win10 machine, it's about connecting to a Win10 machine. Further informations provided if needed). ( I have enabled this by modifying secpol.msc 's security policies. This is not working anymore after upgrading to Windows 10. I am used to configure Windows to allow RDP connections as a user without password (home usage only). That's what I meant when I mentioned the following: This policy setting is enabled by default on other Windows Systems, too, except that the error message is displayed right after clicked Enter in RDC. This behavior is caused by security restriction configured in Group Policy, more specifically, which is:Ĭomputer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Limit local account use of blank passwords to console logon only. The important part here is not about connectingįrom a Win10 machine, it's about connecting Local account use of blank passwords to console logon only" option isĭisabled on both machines. Let's say pc1 has user1 and pc2 has user2. Both of my machines have only 1 user with blank password. I'm not sure if we are talking about the same situation. I have tested to use a user account which has blank password to RDP to Windows 10, and got the error message below:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |