- Microsoft removes guide on converting Microsoft accounts to Local, pushing for Microsoft sign-ins.
- Instructions once available, now missing - likely due to company’s preference for Microsoft accounts.
- People may resist switching to Microsoft accounts for privacy reasons, despite company’s stance.
What’s crazy is the cybersecurity teams at big corporations actually hate this because its putting half their security in Microsofts hands. (And their security has been abysmal for a hot minute or more)
Corporations hate this shit too because they want to be using their internal, domain-controlled users, not Microsoft accounts that pass a ton of trade secrets to Microsoft. Is Microsoft training its AI on your trade secrets? Who knows!
So Microsoft is literally killing core competencies not just for end-users, but for businesses, too.
This will convince a lot of businesses the switch to an all Linux internal domain to be worth it, imho.
Are they (Microsoft) like suicidal or something? They are absolute madmen
I really wish it would, but the people that are the decision makers at businesses simply do not care what Microsoft does as long as it doesn’t impact their bottom line. Yes it’s incredibly user hostile. Yes it’s an administrative nightmare for the IT people, but for the suits that write the checks? It’s just the cost of doing business and they literally could not give a fuck if you paid them.
What’s even crazier is that corporate customers don’t actually deal with this in any way! There’s no Microsoft account required on an Active Directory controlled PC.
Source: I am big corporate IT. Oh, and my personal AD deployment, outside of work
How are you accomplishing this? Provisioning the PCs to be part of the domain with a Powershell install script during automated setup? Because I was under the impression that this also had become a difficult task with 11. Because a Windows 11 machine doesn’t know it’s going to be part of the domain until it has been added to the domain. So, the only way I can see that working is like Powershell combined with WDS or something.
Source: Am small IT
EDIT: Also, the LTSC version of Windows 11 isn’t coming until later in 2024. So I’m very curious how this works with 11 specifically.
Windows 11 Enterprise likely uses a different OOBE, I just tell it to join during setup. At work, everything is image-based and pre-configured so no standard OOBE.
Like most things at MS, those with the resources get everything they want while the little guy gets screwed.
During setup press Shift + F10, type OOBE\bypassnro, press enter and have fun creating local accounts.
Windows 11 pro OOBE > get device online either via WiFi or wired network or bypass via commands > set up for school or work > sign in options > Domain Join. This asks you for local account name and password for a local administrator account and then drops you on the login screen.
As cool as it would be to see a big shift to Linux, I think you underestimate how deeply entrenched companies are with Microsoft, so unwilling to change, the lack of support for proprietary software, and probably most importantly, the lack of IT support to manage a Linux environment.
I’ve been full Arch since December in my personal stuff and have been a Sys Admin+ for 9+ years. I would not say I currently have the skills to effectively administer a Linux environment. I could get there, and there is a lot of overlapping knowledge, like the network stack didn’t change, but I don’t think I’m an outlier.
I recently switched from being the sole IT guy at a small/medium company so a place with about 2k employees. I have maybe met a couple of people within the company IT that I think could make the switch relatively well, and 70% of others that just don’t got it.
Long term it would probably be fine, but that’s not how companies work in most cases. I just don’t think most places are willing to bite the bullet now to benefit later.
