this post was submitted on 15 Apr 2024
756 points (98.3% liked)
Privacy
32173 readers
592 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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
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.
A company that's using Windows Server is not hiring the brightest mfers
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.