MicrosoftCUs aren't generally the main issue for us at least. It's the Builds...
I'm honestly not sure how we can go from 1607 to the next or latest build in our environment.
We have clients in remote locations who are on a pair of bonded T1s.
Doing these build updates and just crossing your fingers nothing goes awry is nerve wracking to say the least.
There needs to be a workstation LTSB option that still has the ability to access the Microsoft store.
We are on a 4 year lease schedule and could totally roll new builds every PC cycle, but deploying remotely is an unmitigated nightmare that takes us away from legitimate projects.
Also on a side note, could you please tell me why my end-users need xbox, pandora, candy crush, etc...? We can kill those applications via MDT, but rolling the updates they get reinstalled.
I'd like to hear some suggestions on making these build updates as easy as possible. And for the love of god don't suggest SCCM, we don't have someone dedicated to managing that monster.
