Windows 10/11 Download

[EarDemon]

Ok, I think I have Remote Desktop at least not erroring out right away. However, it's asking for a username and password. However, I only log into that machine with a Windows login PIN number.

How can I figure out just WHAT username and the password it wants for Remote Desktop login?

If you logon to Windows with a local account, you need a password. You would have had to set one up when creating the account at some point. If you logon to Windows with a Microsoft Account, I have no idea how that works, I have never done that, but I have seen a couple people who got tricked into logging on with an MS account and they use a PIN. I set up the local accounts on all of my devices initially with a PW, then set up Fingerprint recognition as my primary login method, which requires a PIN as a back up method.

If you open a Run window and type in lusrmgr.msc (or control userpasswords2), you'll be able to add/remove local accounts and reset passwords.

By the way, my Network Neighborhood is essentially empty as well, just showing my NAS. Seems to come and go if it shows all of my Windows device or not.

For RDP, I haven't used the built in Windows client in forever at home. I've been using mRemoteNG for years, it is vastly superior, especially if you toggle between multiple RDP sessions, than Microsoft's native client.

 

[b4pjoe]

Ok, I think I have Remote Desktop at least not erroring out right away. However, it's asking for a username and password. However, I only log into that machine with a Windows login PIN number.

How can I figure out just WHAT username and the password it wants for Remote Desktop login?

Go into settings ===> accounts. It should show you the account you are logged in with. Usually a Microsoft or Outlook account. If you don’t know the password you will need to reset it.

 

[primestar31]

If you logon to Windows with a local account, you need a password. You would have had to set one up when creating the account at some point. If you logon to Windows with a Microsoft Account, I have no idea how that works, I have never done that, but I have seen a couple people who got tricked into logging on with an MS account and they use a PIN. I set up the local accounts on all of my devices initially with a PW, then set up Fingerprint recognition as my primary login method, which requires a PIN as a back up method.

If you open a Run window and type in lusrmgr.msc (or control userpasswords2), you'll be able to add/remove local accounts and reset passwords.

By the way, my Network Neighborhood is essentially empty as well, just showing my NAS. Seems to come and go if it shows all of my Windows device or not.

For RDP, I haven't used the built in Windows client in forever at home. I've been using mRemoteNG for years, it is vastly superior, especially if you toggle between multiple RDP sessions, than Microsoft's native client.

Ok, I logged in a single time as a Local User, setting up a username and password. I then logged out of that, and then logged back in with the Microsoft "Hello Pin". Now, even though I'm logged in as a Microsoft user, I can use the local account credentials to log in with Remote Desktop on my other laptop.

I'll keep the other remote client software you mention in mind also, thanks!

 

[EarDemon]

Yes, you now have two user profiles on the computer, a Local one and an MS Account. Since it's a new profile, the desktop and other things will be at default settings. It sounds like you made the new local user a local administrator, since if you didn't and made it a Standard User you would have had to add the account to the Remote Desktop Users group (or do System Properties ->Remote -> Select Users). Also, if you are not local admin, you won't be able to view the contents of the Library folders (My Docs/Pics/Videos/Download) for the other users.

Actually, now that I type this, I wonder if you can add the MS account to the Remote Desktop Users group.

 

[harshness]

How can I figure out just WHAT username and the password it wants for Remote Desktop login?

It is difficult/dangerous to make recommendations not knowing what your environment is (i.e. work .vs. home) and your level of Windows expertise.

The user name should be easy (unless the computer is headless -- no monitor or keyboard). Powershell will drop you into the home directory (C:\Users\<username>).

You can set the password if you have the PIN.

You could also add a hosts entry in the "calling computer" to set the machine name to the IP address (assuming that your DHCP server always serves up the same IP address to that machine).

 

[primestar31]

It is difficult/dangerous to make recommendations not knowing what your environment is (i.e. work .vs. home) and your level of Windows expertise.

The user name should be easy (unless the computer is headless -- no monitor or keyboard). Powershell will drop you into the home directory (C:\Users\<username>).

You can set the password if you have the PIN.

You could also add a hosts entry in the "calling computer" to set the machine name to the IP address (assuming that your DHCP server always serves up the same IP address to that machine).

Thanks, this is for home, see post 223 above. I have it all set up now and working fine as far as I can tell. As for my expertise, 28 years of IT support at my pre-retirement job. From IBM mainframe, to CP/M controlled lab computers, to Dos, and up through Windows 7. Then Windows 10 at home since I've been retired. Though IT skills can atrophy really quick when you are 8 years post retirement, and don't use them every day anymore.

I DID Google all this before making the post, but there's so MUCH stuff out there that seemingly conflicts, it gets hard to weed out the crap, and right to the exact few steps needed for something like this.

Oh yeah, and what started this was my upgrading Windows on Patch Tuesday. I should have remembered not to do that, and get the latest and greatest, that has God knows WHAT bugs in it. In this case, Microsoft trying to lock it down so freaking tight that you just about might as well as not plug in a network cable at all.