I installed windows 11 a dozen time at work (never at home) and I just click on "domain login", it just creates a local account and then after the install I have to manually join the domain. No Microsoft account enforcement at all.

It's regular Windows 11, not Enterprise, we are a small company.

But I'm wondering, this bypass is too easy, is it because it sees that the DNS server is also an active directory server, so it allows that, or the trick is that you tell him you want to join a domain?

Or maybe it's a domain enrollment bug because we're using samba 4 under Debian as active directory server and not Windows server/entra id/whatever they call it this month?

The Enterprise/IoT SKUs, which of course include LTSC, still let you use a local account, for now...

I won't be surprised if they plug that at some point way down the line too though given they're already playing with Windows on the Cloud in the enterprise sector.

Use Windows 11 IoT Enterprise LTSC, problem solved.

Or, you know, that other thing.

How many months away are we from Windows requiring a subscription to use, with a cheaper version for the OS + Office and a more expensive that also bundles AI?

At this point I just net user /add it, which just creates the user manually and then you can reboot and just log into it.

It's not like you need anything from the OOBE at all, so might as well just skip it entirely.

Doesn’t stop me from using Windows 11 as much as I want.

Which is none.

Is this about Windows Home edition? I don't need to do anything hacky to get a local account but I also don't use Home edition.

Glad I found one and used it. If I didn't need Windows for my classes, I'd be on Linux already.

I found it because the wifi was stuck off and if I couldn't turn it on unless I set up windows... Which dumbly requires internet.

So once that comes to pass, someone in my situation would be SOL.

So I guess Lennox phone and Linux computer as well