Got my server mostly done now. But one issue has made things complicated; my inability to use Microsoft Remote Desktop on my default profile. To expand, I made my server from the innards of my older desktop to save money. This was the plan before the memory crisis, and by the time I did it, the plan made even more sense. Thus my default profile was active and had on it several years of usage. Stuff I lost unexpectantly when I turned my desktop into the server. It all came out of no where, but it was the first time I even tried to connect to Windows 11... yeah. That one. Luckily I had been using my laptop more than my desktop so I was able to get by, but it was a solution that I needed to find. Also luckily, my laptop was Windows 11, and surprise surprise, same issue.
Symptoms of this issue are vague. Simply the password reports as a fail. I tried to login manually online using the same account. No issue. I tried changing the password to force a sync. No solution. In the end? Well I'm not 100% sure this is the answer, as I don't want to re-create the issue, but it seems "Windows Hello logins only" as well as having an active PIN will cause the Remote Desktop login to fail. This seemed to be the solution on the laptop, and I tried to just the "Windows Hello logins only" first and the issue remained. So yeah. All good now, and I don't want to break either as I've got a job to do once I can sign into all of my "active" computers at once; scaling back the blight that is OneDrive. A topic for another day? Probably.
Anyway, this is such a bad design choice. Microsoft could have made the error say "no remote logins" rather than make you doubt the password itself. I get that it's a security issue to give hints as to why something failed, but you've got the password right. Can't it get to the Hello layer, and say "yeah, but no"? I used to use any VNC software before, but I eventually moved to the Microsoft one as I figured support would be better. Apparently not eh....
