Hey folks! I'm curious about how everyone manages Windows Updates these days. Do you still take charge of them yourself or do you just let Microsoft handle it with deployment rings? Currently, we are running a local WSUS alongside SCCM, and we also use Acrobat Catalog since it requires admin credentials for updates. I'm considering shifting to Microsoft Update and stopping SCCM deployment for most updates, except for Acrobat. Honestly, I can't remember the last time we skipped a deployment. We're not co-managed yet, but I'm thinking it might be a good idea to set up SCCM's connected cache and use its deployment rings to move towards Windows Update for Business (WUfB). This way, once we start co-management, we'll be ready to transition settings to Intune and enable Autopatch. What does everyone think?
5 Answers
I still manage updates myself, and I have to say, it’s a solid patching system that works well for me.
Honestly, I just let the system do its thing with Windows Update for Business and ignore the rest. It's been working for me.
We still manage updates, but it's way lighter than before. A lot of places are moving towards WUfB with update rings instead of fully controlling everything through WSUS/SCCM. It's less overhead since you don't have to constantly approve updates anymore. Your plan sounds good—using SCCM deployment rings first, then transitioning to WUfB is a smart move!
I recommend Windows Update for Business (WUfB) only if your machines aren't falling behind. It can simplify things.
I switched to Autopatch about a year ago, and I absolutely love it. It's so much easier!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures