WaaS at MSIgnite - Official Rings and asking for Feedback

Hi together,

today I am writing you with new official material and information from the Ignite and I want to ask you for feedback!

You can download the current slides and videos from the Ignite with the same following script: Ignite Download Script

The slides in this blog post can be found here: Servicing Windows 10: Understanding the Windows as a service process and improvements
Michael Niehaus, Director of Product Marketing

Designing and implementing your flighting strategy to support your Windows 10 deployment decisions
John Wilcox, WaaS Evangelist

Further Sessions should also have your attention: Succeed with app compat for Windows as a service
Chris Jackson
How Microsoft deploys Windows 10 and implements Windows as a service internally
Robert Van Winkle
Windows 10 servicing explained (WAAS): Deploying Windows as an inplace upgrade
Adnan Hendricks
How to design and complete your successful move to Windows 10 and WaaS
John Wilcox, WaaS Evangelist

What more?

As usual you should really take a look at the sessions from Michael Niehaus.

You will find a lot of similar points from my previous article "Automating Windows as a Service" and I really recommend you to take a look at the stated sessions in this article.

In terms of tools a very big recommendation is to evaluate the mentioned tools from the Windows Analytics:

They will help you a lot!

The following material is the information you should be aware of:

So - what is Waas?

A new day - some new slides - the same and simple information:

First of all you must know the difference between Quality and Feature Updates:

Every 6 months a new release is published - every spring (03) and fall (09)

Each one serviced for 18 months - please don´t forget the time (you would not be the first one) :

Aligned with O365

Not aligned, but assisted and supported by System Center Configuration Manager.

I saw many customers missunderstanding the latest blog article around alignment, but the following slide should clarify it very clearly.
You will continue to have 3 releases of ConfigMgr every year.

Why WaaS?

Customers continuously ask about the why. Why is every IT manufacturer moving their software to an agile approach and why do we do the same for our OS?
Actually we are the last ones to move into these type of servicing times and here are just some of the big arguments to do so:


Security is the number one - the most important thing to stay secure, is to stay up to date with all your applications - and finally now also the OS. We will continuously work on security in the OS and adding security features to it within every release. Some may be visible - some not. Some things you get to know - some not. A typical example is the Edge Browser. Did you know that Edge is out of the box MUCH more secure than the IE? Probably not?! Take a read here.


Continuously adding new Feature Updates brings new productivity features along - how Windows looks like and can be administrated and this in smaller timeframes with smaller changes with each release.

#Hardware Support

Coming with new hardware there needs also to come changes within the OS to adopt these new, available or changed hardware features:

#No more big deployments

Moving from big and disruptive deployments, which came very often along with a complete migration project and hardware costs, to the Semi-Annual-Channel and adopting this in the daily and operative work, which can lead in a total reduction of costs by using automation and recurring processes.


The recurring Cycle

Smaller deployments with less changes in smaller timeframes. It may sound easy, but you really should recognize the different approach.
Switching from release deployment to an always recurring agile deployment is a huge step.

Each release should be adopted from every customer within the following 3 phases:

How many devices in each phase?

What about App Compat?

Our Compatibility Promise

So you have proactive and reactive testing for your apps. This is one of the arguments for deployment rings:

The Deployment Rings

How could these deployment rings look like?

As you see in the picture we added the "Deployment Decision" in here. A simple recommendation I always give to my customers is to prepare initially every new release version. You don´t really need to deploy every release, but you should have the possibility to do so, if you run later on into other problems.

You should evaluate Insider Preview for Business!

You can gain important information from an Insider Preview!
Some of these points can be:

  • validating new / deprecated features
  • testing new features
  • testing LoB apps
  • get an insight what is coming, before it´s there

How does the deployment rings look like in a high-level view?

In the "Target" area you see the stairs - each step is a ring with different devices in it.

How does the official Microsoft recommendation look like?

All of the following groups are dynamically and also users are allowed to join the early ones, if they want to (and they will want to withing time)

The idea is to deploy the next version on dedicated machines and gathering feedback / data to make with this data the deployment decision, if you want to deploy this version in the broad deployment for your company.

Canary is the initial ring with a small amount of chosen users:

  • IT-Admins
  • Client Team
  • Application Holder / Key Users

Self-Selects: Small amount of users, who want to have early access. They can place themselves into this ring.

Sample: It should deliver you a complete presentation of all job roles, apps, geographical locations. You want to gather the feedback with Windows Analytics or other feedback channels and with this data/feedback you make the deployment decision for this release.

Broad: If the data in Windows Analytics or the feedback was sufficient and good you push out the release to all devices.

And now with some more details:

And what happens, if you encounter any problems within your reactive deployments?
Just stop, fix and continue.


What Tool / Technology to use for Servicing?

You have the following four possibilities to use - you could also combine, which may become hard to manage. Most of my customers went for SCCM and WUfB.

Difinitely evaluate within SCCM the two possibilities:

And finally the session takeways from the session BRK3048, which I highly recommend you to do or use / understand and share:


I showed you the latest officially presented information and now it´s time for feedback! As stated above I want to hear about your approaches and ideas!

Here are some questions which you could probably answer:

  • What do you think about WaaS?
  • How do you configure your rings?
  • What technology do you use?
  • Do the published ring recommendations fit for your company?
    • If not - why?
  • What can be improved?
  • Do you need further help?

P.S: Be honest and professional and please not insulting ;)

David das Neves

Premier Field Engineer, EMEA, Germany
Windows Client, PowerShell, Security