Watching the patching communities closely I’ve noticed a sort of disconnect still lingering for understanding which Windows 10 servicing branch companies should choose to use. I covered this in depth almost a year ago and that information really hasn’t changed. In fact, as we’ve seen since the release of Windows 10, and then the subsequent availability for businesses, Microsoft has only worked to further solidify its OS servicing strategy.
Some companies are looking at Windows 10 servicing and considering the Long Term Service Branch (LTSB) as a viable solution for their business. As we’ve learned, LTSB is an option Microsoft made available for situations where remote systems should not be taken offline to be upgraded constantly. Some of those situations include ATMs and manufacturing systems. Imagine having customer walk up to get cash from an ATM only to see it rebooting to apply the latest cumulative update – or an assembly line halted, waiting for an update to apply. There are other situations, but you get the gist. Think of LTSB as the old Windows Embedded edition. You wouldn't run an Embedded OS version on a user's PC would you?
If you manage a normal small, medium, or large business, LTSB should be considered as a very last resort, if at all. Current Branch for Business (CBB) should sit atop your decision pyramid. Read through the following coverage (again, if that’s the case) to get the best understanding of this continually confusing topic:
- Update Servicing Branches Available for Each Windows 10 Edition
- Microsoft Describes New Business Servicing Branches for Updating Windows 10
- Microsoft's Windows 10 Upgrade Policy for Business Not What You Might Think
- Understanding the Long Term Servicing Branch and Current Branch in Windows 10
Choose the wrong one? Watch this video from community member and IT/Dev Connections speaker Mike Terrill on how to move from LTSB to CBB: