• Spuddlesv2@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    This stuff always makes me laugh. Firstly, yes absolutely, Microsoft shouldn’t do this sort of crap. But more importantly, the person complaining about it here is shouting out for the world to hear “I don’t know how to manage Windows servers properly!”. There is one single group policy setting that stops this from happening. A single, set-and-forget GPO. Anyone managing Windows environments that isn’t aware of this, shouldn’t be managing Windows environments.

    • risencode@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      5 months ago

      This is a ridiculous statement. Copilot should be opt-in, not opt-out and the setting is new.

      Perfectly reasonable by the sysadmin to not have that already set.

    • AMDIsOurLord@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      There are 5 million ways to configure windows and each have an absurd and almost by-design level of convolution. You can’t possibly expect people to know about a new GPO immediately

      • Trollception@lemmy.world
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        5 months ago

        That is why companies will hire good sys admins who do their job and stay on top of the important group policy settings. This absolutely would not be missed by any reasonably competent IT dept.