{"id":5245,"date":"2017-12-05T11:06:03","date_gmt":"2017-12-05T17:06:03","guid":{"rendered":"https:\/\/www.poweradmin.com\/blog\/?p=5245"},"modified":"2017-11-30T11:09:26","modified_gmt":"2017-11-30T17:09:26","slug":"a-breakdown-of-the-various-kinds-of-windows-10-2016-and-the-upgrade-rings","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/a-breakdown-of-the-various-kinds-of-windows-10-2016-and-the-upgrade-rings\/","title":{"rendered":"A Breakdown of the Various Kinds of Windows 10\/2016, and the Upgrade \u2018Rings\u2019"},"content":{"rendered":"

\"\"<\/a>With a significant number of users worldwide still clinging tenaciously to their installations of Windows 7 \u2013 and smaller number holding onto the markedly less popular Windows 8.x variants \u2013 Microsoft\u2019s dream of a smooth and global transition to its latest desktop and network operating systems has yet to become a reality.<\/span><\/p>\n

\u00a0<\/p>\n

But improvements and new features continue to be added, and updates or upgrades (the two words are used interchangeably, in a Microsoft context) continue to be issued for Windows 10.<\/span><\/p>\n

\u00a0<\/p>\n

For many Windows 10 users, the manner in which these updates are being made available is a source of some confusion and concern. So in this article, we\u2019ll be looking to clarify some issues surrounding Windows 10 updates, and the concept of \u201crings\u201d.<\/span><\/p>\n

Intentions & Implications of Windows 10 Update Strategy<\/span><\/h2>\n

Microsoft\u2019s strategy for delivering upgrades for Windows 10 builds on the conceptual model used for enterprise deployments in previous versions of their operating platform. In the past, organizations using Windows were required to categorize their users into distinct sets, so that updates could be rolled out in phases.<\/span><\/p>\n

\u00a0<\/p>\n

Users such as \u201cWindows Insiders\u201d (the scheme for early adopters of new Microsoft operating systems and software, who are fast-tracked into their installations) or company IT staff (who would be more likely to have a good understanding of a new system) would be earmarked as eligible for the first wave, or \u201cring\u201d of upgrade software.<\/span><\/p>\n

\u00a0<\/p>\n

Upgrades would then be issued on a descending scale, in rings depending on the level of technical understanding of the user, or the level to which an operating system change might negatively impact their work.<\/span><\/p>\n

\u00a0<\/p>\n

This general idea remains for Windows 10, but the creation and management of the upgrade groups or rings is handled differently. Users in those categories likely to be negatively impacted by an upgrade are also given the option of bypassing certain upgrade schedules and holding their position in a particular ring, for a longer period \u2013 perhaps till a later upgrade cycle, which might have preferable features.<\/span><\/p>\n

\u00a0<\/p>\n

With the rings concept making a number of alternate upgrade paths and time-frames available to users, it\u2019s been argued that this approach may lead to a fracturing or fragmentation of the Windows 10 operating system. But Microsoft and many analysts have played down the negative effect of delays which certain upgrade rings might impose on enterprise users, in favor of the overall stability and uniformity of a common ecosystem \u2013 once Windows 10 becomes the predominant force in the enterprise market.<\/span><\/p>\n

\u00a0<\/p>\n

That\u2019s yet to happen, but in anticipation Microsoft has charted a provisional time-frame with major upgrades appearing at intervals of roughly four months. The company has also set out a proprietary structure for those updates, and the channels through which they\u2019re delivered \u2013 as described in the following sections.<\/span><\/p>\n

Update Branches<\/span><\/h2>\n

In Microsoft parlance, \u201cbranches\u201d are a general term denoting a category of user for whom a particular mode and time-frame for update delivery has been allocated.<\/span><\/p>\n

\u00a0<\/p>\n

For example, the initial upgrade on Microsoft\u2019s consumer time-table<\/a> was scheduled mainly for devices running Windows 10 Home, and upgrading via the Windows Update service.<\/span><\/p>\n

Update Rings<\/span><\/h2>\n

Each branch on the Microsoft upgrade map is further segmented into \u201crings\u201d \u2013 again determined by the upgrade path and time-frame allotted to each.<\/span><\/p>\n

\u00a0<\/p>\n

It\u2019s within the ring system that customers can proactively pace their own upgrade paths, by opting for a slow or fast ring release.<\/span><\/p>\n

Semi-Annual Channel (Targeted), or CB<\/span><\/h2>\n

The \u201cCurrent Branch\u201d (or CB) update track was the initial upgrade path offered to Windows 10 Home consumers, and to those users of Windows 10 Pro who opted in for that upgrade package.<\/span><\/p>\n

\u00a0<\/p>\n

As the Windows 10 upgrade ecosystem evolved, CB was superseded by its new classification as a Semi-Annual Channel (Targeted) update path, for the consumer market.<\/span><\/p>\n

Semi-Annual Channel, or CBB<\/span><\/h2>\n

The Current Branch for Business (or CBB) upgrade path followed the consumer-level Current Branch (CB). This delay was claimed by Microsoft as an opportunity for the company to iron out more bugs in its operating system before releasing it to its most important customer base \u2013 the business market.<\/span><\/p>\n

\u00a0<\/p>\n

Like CB, Microsoft\u2019s Current Branch for Business has since received a new classification, and is now simply known as the Semi-Annual Channel.<\/span><\/p>\n

Windows Server Update Services (WSUS)<\/span><\/h2>\n

Users of Windows 10 Pro and Windows 10 Enterprise can manage their updates using Windows Server Update Services<\/a> (WSUS) \u2013 a Windows Server role, available in the various versions of the Windows Server operating system. Consumers may also accomplish the same end by using a third-party patch management program.<\/span><\/p>\n

\u00a0<\/p>\n

For business users, WSUS largely supersedes the previous platform, Windows Update for Business (WUB). Within a commercial organization, WSUS enables companies to defer updates until a later time, to selectively approve individual updates, to choose when updates are delivered, and to specify which particular devices or groups of devices receive specific updates. All of this may be managed from a single centralized hub.<\/span><\/p>\n

\u00a0<\/p>\n

WSUS provides an extended set of controls over Windows Update for Business, but lacks the scheduling options and deployment flexibility of System Center Configuration Manager (SCCM).<\/span><\/p>\n

\u00a0<\/p>\n

To use WSUS for the management and deployment of Windows 10 feature updates, WSUS 4.0 (available in Windows Server 2012 R2 and Windows Server 2012 operating systems) must be installed, along with the KB3095113 and KB3159706 Windows patches on the WSUS server.<\/span><\/p>\n

Express Installation Files<\/span><\/h2>\n

Express Installation Files is a feature of WSUS aimed at reducing the bandwidth consumption of upgrade operations.<\/span><\/p>\n

\u00a0<\/p>\n

Working on the assumption that current updates often feature most of the same files as previous versions (at least in binary terms), Express Installation Files analyzes the difference between the new files associated with an update, and existing files on the client system. It then authorizes the download of only those files which have actually been altered.<\/span><\/p>\n

Configuring Automatic Updates & Update Service Location<\/span><\/h2>\n

For system managers, it\u2019s a good practice to prepare for upgrade cycles by configuring the Configure Automatic Updates and Intranet Microsoft Update Service Location Group Policy settings for your particular environment. This forces all of your affected Windows client devices to contact the WSUS server, so that it can manage their updates.<\/span><\/p>\n

Creating Computer Groups<\/span><\/h2>\n

As we\u2019ve seen conceptually, it\u2019s possible to use computer groups or \u201cdeployment rings\u201d to target a subset of your devices which have specific qualities, so that they can receive tailor-made feature updates. Deployment rings in Windows 10<\/a> allow machines to be separated into their own upgrade time-lines, and reduce the risk of issues arising from feature deployment upgrades affecting the entire organization at once.<\/span><\/p>\n

\u00a0<\/p>\n

In practice, these deployment rings can be created and controlled via WSUS. Groups may be populated by hand from the WSUS Administration Console, or automatically via Group Policy. The process of adding computers to computer groups in the WSUS Administration Console is known as server-side targeting.<\/span><\/p>\n

Long-term Servicing Branch, or LTSB<\/span><\/h2>\n

We\u2019ll end with a legacy term which you may still see displayed on some Microsoft products.<\/span><\/p>\n

\u00a0<\/p>\n

The Long-term Servicing Branch or LTSB is\/was a feature of Windows 10 Enterprise, an OS exclusively available to organizations with a volume licensing agreement tied to the Microsoft\u2019s Software Assurance (SA) program.<\/span><\/p>\n

\u00a0<\/p>\n

Systems on the LTSB only received security patches and critical bug-fixes. A new LTSB build was scheduled to be issued every two to three years, integrating some or all of the feature changes introduced via CB or CBB in the intervening years.<\/span><\/p>\n

\u00a0<\/p>\n

All of these upgrade paths have since evolved, and been superseded by Windows Server Update Services (WSUS) and its associated tools.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

With a significant number of users worldwide still clinging tenaciously to their installations of Windows 7 \u2013 and smaller number holding onto the markedly less popular Windows 8.x variants \u2013 Microsoft\u2019s dream of a smooth and global transition to its latest desktop and network operating systems has yet to become a reality. \u00a0 But improvements […]<\/p>\n","protected":false},"author":10,"featured_media":5247,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-5245","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-windows"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/5245","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/comments?post=5245"}],"version-history":[{"count":4,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/5245\/revisions"}],"predecessor-version":[{"id":5248,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/5245\/revisions\/5248"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media\/5247"}],"wp:attachment":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media?parent=5245"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/categories?post=5245"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/tags?post=5245"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}