I'm highlighting each day someone in the enterprise tech community that I think you might be interested in knowing. To keep up with all of my picks, subscribe to my twice-monthly newsletter using the form on the right side of this page.
Don't forget: If you'd like to suggest a site, blog post or personality for consideration as a future ITUnity Champ, email me at firstname.lastname@example.org and I will be happy to take a look. (You can even nominate yourself.)
Today's ITUnity Champ:
Sandys is an expert in SMS and Configuration Manager. He’s a Microsoft Most Valuable Professional in Enterprise Mobility, co-author of/contributor to several books about System Center Configuration Manager and is a frequent speaker at various Microsoft, community and user-group events around the world.
I found Sandys’ blog thanks to a recent article in Redmond Channel Partner. As those following all things Windows 10 know, Microsoft has made changes to some of the settings in Windows 10 to make update and upgrade deferrals more granular and lenient for many. However, some System Center Configuration Manager users have found reconciling these settings changes with SCCM convoluted and confusing.
As Redmond Channel Partner noted, Microsoft seems poised to fix some of the issues around this. In the interim, Sandys’ post on Windows 10 servicing and Configuration Manager, which attempt to set the record straight, is definitely worth a read:
Windows 10 Servicing with ConfigMgr Confusion
A lot has been written and spoken by Microsoft and in the community of Windows 10 as a service and it’s multiple servicing models, commonly called Windows 10 Servicing. This of course includes Current Branch (CB), Current Branch for Business (CBB), and Long Term Servicing Branch (LTSB). LTSB is special servicing branch of Windows 10 but this post is completely non-applicable to it because, well, eww yuck, it’s best to avoid LTSB altogether.
There are a lot of incorrect and misleading statements floating around about CB and CBB in both official Microsoft documentation, unofficial documentation, and community blog posts to name a few sources. Here’s a summary of these statements which are more or less all related and stem from a faulty understanding of what the service model really is or rather what a customer should use it for. Additionally, these statements seem OK on the surface and in some scenarios may actually appear to be true. But, once you peel back the layers, it’s easy to see that they are not and can be bad for your environment if you treat them as true.