Every Windows release evolves the operating system architecture to better defend against attacks – not just patching! And Windows and Office updates\u00a0support new\u00a0ways of working: inking, voice control, improved navigation, etc.<\/p>\n
So, updates are good – right?<\/p>\n
How often do I need to update?<\/h3>\n
We’re no longer in a world of 5+5 years (mainstream+extended) support. Microsoft has publicly stated its intention to ship two feature updates to Windows each year (in Spring and Autumn). The latest of these is Windows 10 1803 (also known as Redstone 4), which actually shipped in April. Expect the next one in\/around September 2018 (1809). Internally to Microsoft, there are new builds daily; and even publicly there are “Insider” Preview builds for evaluation.<\/p>\n
That means that we need to stop thinking about Windows feature updates as projects and start thinking about them as process – i.e. make updating Windows (and Office, and supporting infrastructure) part of the business as usual norm.<\/p>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-1.png?resize=700%2C391&ssl=1\")
<\/p>\n
OK, but what if I don’t update?<\/h3>\n
Put simply, if you choose not to stay up-to-date, you’ll build up a problem for later. The point about having predictable releases is that it should help planning<\/p>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-2.png?resize=700%2C391&ssl=1\")
<\/p>\n
But each release is only supported for 18 months. That means that you need to be thinking about getting users on n-2 releases updated before it gets too close to their end of support. Today, that means:<\/p>\n
- \n
- Running 1703, take action to update.<\/li>\n
- Running 1709, plan to update.<\/li>\n
- Running 1803, trailblazer!<\/li>\n<\/ul>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-3.png?resize=700%2C391&ssl=1\")
<\/p>\nWe’re no longer looking at major updates every 3-5 years;\u00a0instead an approach of continuous service improvement is required. This lessens the impact of each change.<\/p>\n
So that’s Windows, what about Office?<\/h3>\n
For those using Office 365 ProPlus (i.e. licensing the latest versions of Office applications through an Office 365 subscription), Windows and Office updates are aligned (not to the day, but to the Spring and Autumn cadence):<\/p>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-4.png?resize=700%2C393&ssl=1\")
<\/p>\nSo, keep Office updated in line with Windows and you should be in a good place. Build a process that gives confidence and trust to move the two at the same time\u2026 the traditional approach of deploying Windows and Office separately often comes down to testing and deployment processes.<\/p>\n
What about my deployment tools? Will they support the latest updates?<\/h3>\n
According to Microsoft, there are more than 100 million devices managed with System Center Configuration Manager (SCCM) and\u00a0SCCM also needs to be kept up-to-date to support upcoming releases.<\/p>\n
SCCM releases are not every 6 months – they should be every 4 months or so – and the intention is to update SCCM to support the next version of Windows\/Office ahead of when they become available:<\/p>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-5.png?resize=700%2C391&ssl=1\")
<\/p>\nAgain, start to prepare as early as possible – and think of this as a process, not a project. Deploy first to a limited set of users, then push more broadly:<\/p>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-6.png?resize=700%2C394&ssl=1\")
<\/p>\nWhy has Microsoft made us work this way?<\/h3>\n
The world has changed. With Office existing on multiple platforms and systems under constant threat of attack from those who wish to steal our data (and money) it’s become necessary to move from a major update every 3-5 years to a continuous plan to remain in shape and execute every few months – providing high levels of stability and access to the latest features\/functionality.<\/p>\n
Across Windows, Office, Azure and System Center Microsoft is continually improving security, reliability and performance whilst integrating cloud services to add functionality and to simplify the process of staying current.<\/p>\n
How can I move from\u00a0managing updates as a project to making it part of the process?<\/h3>\n
As mentioned previously, adopting Windows as a Service involves a cultural shift from periodic projects to a regular process.<\/p>\n
Organisations need to be continually planning and preparing for the next update using Insider Preview to understand the impact of upcoming changes and the potential provided by new features, including any training needs.<\/p>\n
Applications, devices and infrastructure can be tested using targeted pilot deployments and then, once the update is generally available and known to work in the environment, a broader deployment can be instigated:<\/p>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-7.png?resize=700%2C393&ssl=1\")
<\/p>\nAim to deploy to users following the model below for each stage:<\/p>\n
- \n
- Plan and prepare: 1%.<\/li>\n
- Targeted deployment:\u00a09%.<\/li>\n
- Broad deployment: 90%.<\/li>\n<\/ul>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-8.png?resize=700%2C390&ssl=1\")
<\/p>\nRemember, this is about feature updates, not a new version of Windows. The underlying architecture will evolve over time but Windows as a Service is about smaller, incremental change rather than the big step changes we’ve seen in the past.<\/p>\n
But what about testing applications with each new release of Windows?<\/h3>\n
Of course, applications need to be tested against new releases – and there will be dependencies on support from other vendors too – but it’s important that the flow of releases should not be held up by application testing. If you test every application before updating Windows, it will be difficult to hit the rollout cadence. Instead, proactively assess which applications are used by the majority of users and address these first. Aim to move 80-90% of users to the latest release(s) and reactively address issues with the remaining apps (maybe using a succession of mini-pilots) but don’t stop the process because there are still a few apps to get ready!<\/p>\n
You can also use alternative deployment methods (such as virtualised applications or published applications) to work around compatibility issues.<\/p>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-9.png?resize=700%2C388&ssl=1\")
<\/p>\nIt’s worth noting that\u00a0most Windows 7-compatible apps will be compatible with Windows 10. The same app development platform (UWP), driver servicing model, etc. are used.\u00a0Some device drivers may not exist for Windows 10 but most do and availability through Windows Update has improved for drivers and firmware. BIOS support is getting better too.<\/p>\n
In addition, there are around a million applications registered in the Ready For Windows<\/a> database, which can be used for spot-checking ISVs’ Windows 10 support for each application and its prevalence in the wild.<\/p>\n
New cloud-enabled capabilities to guide your Windows 10 deployment<\/h3>\n
![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-10.png?resize=700%2C390&ssl=1\")
<\/p>\n![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-11.png?resize=700%2C388&ssl=1\")
<\/p>\n![](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/windows-as-a-service-12.png?resize=700%2C390&ssl=1\")
<\/p>\n