this post was submitted on 23 Oct 2023
92 points (91.1% liked)
PC Master Race
14975 readers
184 users here now
A community for PC Master Race.
Rules:
- No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
- Be respectful. Everyone should feel welcome here.
- No NSFW content.
- No Ads / Spamming.
- Be thoughtful and helpful: even with ‘stupid’ questions. The world won’t be made better or worse by snarky comments schooling naive newcomers on Lemmy.
Notes:
- PCMR Community Name - Our Response and the Survey
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Are you using Enterprise edition? Standard hardware across users? Active Directory to push a standard set of GPOs and registry edits? Most of this stuff shouldn't be that hard to manage if you have an actual environment set up to do so and not a cobbled together unmanaged mess that grew/was built ad-hoc. That said not all of us are lucky enough to have any better than ad-hoc, and Microsoft in their infinite wisdom stopped offering general desktop and server management courses that might teach this shit a few years back.
Beyond that, you should probably hold back non-security patches and updates by a few weeks to a month. That gives you time to test on a pilot machine and identify what new settings you'll have to push to client machines, and time for the internet and MS to find any issues before you have to do so yourself.