This has been discussed in quite some detail (at least as much detail as available). Take a trip through the archives, and you'll probably stumble across those discussions
From: [email protected] [mailto:[email protected]] On Behalf Of s kissel Sent: Wednesday, September 23, 2015 7:47 AM To: [email protected] Subject: [mssms] Windows 10 Software Updates - Anyone have a clear understanding? All - We know that Consumer users will be straight automatic updates and features (Current Branch) which may or may not include fast and slow rings. We know that LTSB Enterprise Customers will get Security updates only, and no new features, controlled by SCCM, EMS, and WSUS. What's muddy is the Windows Update for Business, which won't be fully implemented until 2016. This includes presumably slower updates and features after MS, insiders, and Consumers get updates, and business will have up to a year to install them using Current Branch for Business (CBB). Are there slow and fast rings within this realm? As well as a "No" ring (also used for critical systems) in which IT manages updates via SCCM, EMS, and WSUS after extensive testing? If a client has SCCM, but would prefer to manage what updates their business gets via some cloud platform, and doesn't have to download updates to DPs and push them out, his this even an option? Intune perhaps? I'm trying to determine what this "hybrid" model looks like where you have some users in an organization managed by SCCM, and others by essentially automatic updates, but in slower (business) rings. Is Windows Update for Business only peer-to-peer? Any one have a clear direction and understanding on this that could shed some light? Much appreciated! -S
