• 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.
  • mark3748@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 months ago

    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

    • Snot Flickerman@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      5 months ago

      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.

      • mark3748@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        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.