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.
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.
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.
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.
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.