Quick question - reversing switch from local account to Microsoft Account under W10

[David]

I have always used local accounts.
Somehow on my latest W10 install I have been lured into using a Microsoft
Account.
I'm not quite sure how because up to now I've logged in with the local
account.
However after leaving it a few days it now wants me to log in with the
Microsoft Account.

Is there a way using another local admin account I can revert, or do I
have to recover the password and log into the account?

All very confusing because the Microsoft Account is tied to a non-
Microsoft (ntlworld) email account, so I assume that the email account
password is different from the Microsoft Account password.

I wondered why I was getting emails saying a Microsoft Account password
reset had been requested, when I hadn't done anything.

Cheers



Dave R

[Adrian Caspersz]

Post by David
I have always used local accounts.
Somehow on my latest W10 install I have been lured into using a Microsoft
Account.
I'm not quite sure how because up to now I've logged in with the local
account.
However after leaving it a few days it now wants me to log in with the
Microsoft Account.
Is there a way using another local admin account I can revert, or do I
have to recover the password and log into the account?
All very confusing because the Microsoft Account is tied to a non-
Microsoft (ntlworld) email account, so I assume that the email account
password is different from the Microsoft Account password.
I wondered why I was getting emails saying a Microsoft Account password
reset had been requested, when I hadn't done anything.

Microsoft account, erm - what's that? :-p

For years, I been home-lab running professional versions of windows
against my own domain controller, an installation of Windows Server on a
lowly Intel NUC. I now have redundancy across two domain controllers,
both hosted as VMs on a couple of independent hypervisors (Proxmox). I
could put one of those VMs in the cloud - but at the moment I have
better things to do than jump on that bandwagon.

Having Active Directory on-premises, an AD domain, user and computer
accounts, complete control of group policy, a WSUS server scheduled to
look after patching - makes looking after individual windows
installations and security painless (well, until I get hit with a
Cryptolock attack if I'm silly enough to use Windows for heavy internet
use).

A world of sanity, looking at the typical Windows Home(tm) experience
out there, where users don't even have control of automatic reboots...

For convenience, I even use Microsoft AD to authenticate logins for
Linux machines using SSSD.

In theory it's possible to go the other way, and use Linux Samba as an
authentication server for Windows, but again for me better things to do
than travel down that rabbit-hole Microsoft is almost guaranteed to
break. I don't think distributed group policy works in that scenario.

But for instance, it even looks possible to let a QNAP NAS fly as a
authentication domain controller from the built-in software they supply.