IT Faces More Hurdles with Win 10 Anniversary
December 05, 2016

Rex McMillan
LANDESK

Share this

Win 10 is now in official anniversary mode with its 1607 anniversary update ready to roll out to some 400 million devices. Microsoft is optimistic users will covet this update and offers suggestions on how you can fast track your update if so desired. While users may find the anniversary update features such as improved taskbar management helpful, IT pros will continue to grapple with the new way Microsoft is executing updates: these feature updates were previously called branch upgrades and quality updates, the latter also known as cumulative patches.

Feature updates' impact lies between a service pack and an operating system upgrade. They can be as large as 4GB and will typically occur every six months. They contain a combination of new features and fixes, and will cause an upgrade impact to the end user. These feature updates are going to have a much bigger impact on your network and local storage than the old service packs. They are bigger, going to be released more frequently, and will have a higher user impact during upgrades.

To add to the complexity, Win 10 is executing a number of types of servicing branches.


Even further, Microsoft has announced Win 10 Ver. 1607 is initially considered the Current Branch (CB) and will become Current Branch for Business (CBB) in four to six months.

If you're an IT pro charged with optimizing the performance of your enterprise, what do branches mean for you? Here are a few things to consider:

Choose Stability: Enterprises that must have minimal service disruptions, such as health care, may want to opt for the Long Term Servicing Branch, with updates every two to three years and a long support lifetime.

Test the Waters: IT can choose to deploy a more frequently changing branch on a subset of computers, the early adopters. This gives IT a type of beta trial, if you will, to identify potential application compatibility issues that could adversely affect performance.

Standardization: For your organization you may find that one branch will work for most machines.

Mitigate Risk: Some of the branches are supported for only months so where does this leave your network security? It means IT will have more work to do in making sure it deploys feature updates as they become available, since like it or not, Win 10 feature updates are frequent and support has an end date.

Upgrade Model

We've discussed how to parse out these branches, but let us emphasize that these branch updates are going to be constantly rolling out, and will often overlap.

Here is a four step approach that can be applied to different rollout plans:

Preview Insider Branch: Insider branch should be installed and used to preview features, perform early testing and prepare for the release of current branch. Due to release cadence, it will pay large dividends to use early branches to find and resolve issues. This enables IT to prepare for the release and piloting of CB and have time to mitigate potential issues.

Pilot on Current Branch: As branches are progressive in nature, rollouts should schedule the pilot phase to commence with the release of Current Branch. Current Branch will stabilize over time so pilot systems can detect issues that may affect production systems. This branch should be used for application compatibility testing. Leveraging CB enables the organization to test applications and be prepared to migrate to the branch when it is slated as CCB (Current Branch for Business).

Production on Current Branch for Business: When the branch is declared Current Branch for Business, it should be very stable and the pilot rollouts should have already identified branch compatibility issues that can be addressed before this phase begins. Production systems should be run on CCB.

Grace Period for Problem Upgrades: Enterprises should be done with upgrades before hitting the grace period and use this time to address problem upgrades only.

IT needs to evaluate the performance impact of these various branches, in terms of frequency, support limitations and security risks and have a plan in place to avoid disruption as these Win 10 updates start hitting your enterprise.

Rex McMillan is Principal Product Manager at LANDESK.

Share this

The Latest

February 24, 2017

Global revenue in the BI and analytics software market is forecast to reach $18.3 billion in 2017, an increase of 7.3 percent from 2016, according to the latest Gartner forecast. Gartner believes the rapidly evolving modern BI and analytics market is being influenced by the following 7 dynamics ...

February 23, 2017

An important aspect of performance monitoring is where the observer stands when looking at the IT scenario. Each participant has a different view of what is bad performance - network, database, web, system, user personnel, management and external people - customers, regulatory bodies etc. These are what I call viewpoints ...

February 22, 2017

An important aspect of performance monitoring is where the observer stands when looking at the IT scenario. If a complaint says the performance of an application is dreadful, the network man might say "Everything is fine" and the database man may agree, both saying "What's the problem?" All these people may say that the performance world is rosy but not to other people who have a different idea on what is rosy and what is not ...

February 21, 2017

Instapaper, a "read later" tool for saving web pages to read on other devices or offline, suffered an extensive outage 2 weeks ago. While Instapaper hit a unique problem — a file size limitation — its experience speaks to a much larger problem: scaling a database is difficult, and never quick. That basic fact explains why outages like this are surprisingly common ...

February 16, 2017

Hybrid Cloud is the preferred enterprise strategy, according to RightScale's 2017 State of the Cloud Report ...

February 15, 2017

IT departments often try to protect against downtime by focusing on the web application. Monitoring web application's performance helps identify malfunctions and their cause on a code level, so that the DevOps team can solve the problem. But, monitoring application performance only protects against application errors and ignores external factors such as network traffic, hardware, connectivity issues or bandwidth usage, all of which can have an impact performance and availability of a website ...

February 14, 2017

Everybody loves DevOps. In fact, DevOps is the hottest date in IT. That's because DevOps promises to satisfy the deepest longings of digital business — including fast execution on innovative ideas, competitively differentiated customer experiences, and significantly improved operational efficiencies ...

February 13, 2017

Forrester forecasted that direct online sales totaled 11.6 percent of total US retail sales in 2016, but digital touchpoints actually impacted an estimated 49 percent of total US retail sales, according to The State of Retailing Online 2017: Key Metrics, Business Objectives and Mobile report, released by the National Retail Federation’s Shop.org division and Forrester ...

February 10, 2017

Cisco's acquisition of AppDynamics – and the premium it paid – represents a "statement acquisition" that addresses several converging trends in both technology and financial markets. For strategic acquirers and tech investors, the acquisition is about delivering value to users and improving business outcomes through a go-to-market model that drives recurring revenues ...

February 08, 2017

Industrial and technological revolutions happen because new manufacturing systems or technologies make life easier, less expensive, more convenient, or more efficient. It's been that way in every epoch – but Continuity Software's new study indicates that in the cloud era, there's still work to be done ...