- 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 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.
Yup, you can DL enterprise Win11 for free to, just gotta know how to grab it from MS.
During setup press Shift + F10, type OOBE\bypassnro, press enter and have fun creating local accounts.
That has been err “fixed” some time ago. You cant open the command window during setup anymore
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.
