nvjilo.blogg.se

#HTTPS WWW REMOTEPC COM LOGIN PRO#

When done, restart your computer and verify you can connect from another PC using the local account username/password you just set.Make sure you set a password during the process (a user account with no password cannot connect by RDP, even if it has appropriate permissions otherwise).

Windows will show some warnings and suggest you don’t do this, but do it anyway.

Go to Settings > Accounts > Your Info, then click “Sign in with a local account instead”.

Here’s the long steps should you wish to take them: Once set, you’ll be able to keep using those local credentials even if you later re-link your user account to a Microsoft Account. Method Two, the Alternative (Slight Hassle) WayĪnother way to get local credentials set for your user account is to unlink your Microsoft Account, setting a local password during the process. If you see this, your command worked and you’re all done. Go ahead and close it and the terminal window - you’re all done.Īt this point, you should be able to connect to the remote computer using the same account & password you just used to run the above command. After supplying the password and pressing Enter, you’ll know it worked if you see the About Windows dialog box open.

Since your local user account had no password, it wasn’t eligible for RDP use even if it has appropriate permissions otherwise. It sounds (and is) pretty simple, but what it does in the background is caches your Microsoft Account credentials. This command runs the “winver” program under the credentials of the user account specified. You can just put this directly into your Run box.

On the PC hosting the remote desktop session (running Windows Pro or better), run the following command, replacing the example email address with your Microsoft Account email address that you use to login to the computer. If you sign-in to your PC using a Microsoft Account, you may be unable to connect to that with Remote Desktop.

#HTTPS WWW REMOTEPC COM LOGIN PRO#