• Trollception@lemmy.world
      link
      fedilink
      arrow-up
      4
      arrow-down
      14
      ·
      7 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.

      • bitfucker@programming.dev
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        7 months ago

        I don’t use windows so I don’t know the specifics. If microsoft is INFORMING the user beforehand about this change (that copilot switch/policy is now available) AND DISCLOSE that in the future if you didn’t touch this switch then copilot may be installed, sure, blame admin. Otherwise, this is a shitty move from software update POV

        To add: Maybe you can link the change log provided by microsoft before this update that adds those switches or rules to prove that it has indeed been disclosed to the admin.

    • Spuddlesv2@lemmy.ca
      link
      fedilink
      arrow-up
      7
      arrow-down
      18
      ·
      7 months ago

      There is one GPO to disable co-pilot. One. It’s not even hard to find and has been available for more than 6 months.

      And yes I would absolutely expect someone whose job it is to manage Windows servers to know about it. And certainly, I would expect them to look it up before declaring to the world how bad at their job they are.