this post was submitted on 08 Apr 2024
321 points (93.5% liked)
Technology
59314 readers
4719 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
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
You can disable or streamline that stuff with either group policy or registry keys.
I used to do the same work (several years ago) and I started researching fixes and writing scripts to speed up my work.
Make a to do list of what your computer setup process is. Figure out the earliest you can launch a script (netshare or usb). Then start writing scripts for your tasks.
Installing apps, file transfers and system configs.
That seems like a lot of convoluted bullshit just to get your os to work, considering you need to update the whole thing every week.
You sure you haven't tried arch? Openbsd? You sound like a typical user.
I'm talking about supporting an American enterprise environment that handles medical patient data. No Linux workstations really. Easier to comply with HIPAA that way.
Is it convoluted BS? Sure why not. But Microsoft services are really sticky once you get integrated at a large scale (5k workstations plus over 100 servers).
And when they withdraw support for that feature, do you think laws will cause all the computers to crash?
or you could just use linux.
Sounds like the same level of effort, and it doesn't try and fight you every possible step of the way.
As mentioned above, this is corporate work and it's not as easy to sell as Microsoft
yeah i suppose that should be a given though, frankly.
Unfortunately our setup is not that sophisticated and neither am I. It's a goal we're working toward, but we're just caught in a loop doing archaic shit because the workload is too high to fix it.
At that point why not run a WDS
Because you're a level 1~2 technician hired in to support an enterprise windows environment and you have no choice.
Hit the nail on the fucking head.