How to add a remote LAN user to a computer and make an auto-log on to it on windows 10 pro
I have two computers with Windows 10 Pro, let's call my main computer "host" and the secondary computer "potato", ok? On the host, I have two users, one for local use and the other only for when I turn on potato, which accesses the host through this other user. I configured potato to autologon on the user that I have configured on it and to automatically start the remote connection with an .rdp file on the second host user, because I use potato only on remote connection with host. The problem is that every time I turn on the potato, I need to wait for it to go through the entire internal logon process on its user, wait until opens its explorer, wait potato remember to lunch the .rpd file, and only then it makes logon remotely on the host user. What I would like to do is add the second host user directly to potato, so that potato will log on directly to the host user, without having to go through his internal user. And so that the potato user's explorer is not running at the bottom of the MSRDP. I did a lot of research this week, and I had no success in accomplishing that feat. And as far as I can tell, apparently, the only way to make that is with host running Windows Server. So my question is: Is it possible to add this host user remotely to potato using Windows 10 Pro? If this is not possible, would anyone have a better solution on how to make potato a remote access hub (basically a thin client) in a better way? Thanks, everybody!Getting error when trying to manage local pc with windows admin center
I just installed the 1910 version of windows admin center on my windows 10 pro pc. Whenever I click on connect i get the error of: Connection error Connecting to remote server gaming-laptop failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic. I an unsure what to do at this point, any help would be greatly appreciated.
