How to Keep up with the Speed of Windows as a Service Configuration Manager ConfigMgr SCCM? The Windows 10 operating system introduces a new way to build, deploy, and service Windows. This new way of handling Windows 10 OS is called Windows as a service (WaaS).
Microsoft has reimagined each part of this Windows 10 process to simplify the lives of IT pros and maintain a consistent Windows 10 experience for its customers. These improvements focus on maximizing customer involvement in Windows development, simplifying the deployment and servicing of Windows client computers.
Introduction – Speed of Windows as a Service
Windows 10 comes with two servicing options (release types): feature updates (e.g., Windows 10 1511, 1607 and Creator Updates, etc.) that add new functionality two to three times per year and quality updates that provide security and reliability fix at least once a month.
Traditional Windows servicing has included several release types: major revisions (e.g., the Windows 8.1, Windows 8, and Windows 7 operating systems), service packs, and monthly updates.
How to Keep up with the Speed of Windows as a Service Configuration Manager ConfigMgr SCCM
Windows 10 deployment schedules are different from traditional Windows deployment schedules. The traditional deployment plan imposed a training burden on users because the feature revisions were often significant. In the case of Windows 10, it just keeps on evolving, and users will get a chance to Evaluate, pilot, and deploy in a phase-wise approach.
Windows Insider build should be part of the evaluation, Windows Current Branch (CB) build should be part of the pilot, and Windows Current Branch for Business (CBB) should be part of the production deployment. Windows as a Service provides more than 4 months for a pilot with CB release, 12+ months for deploying the CBB release, and 60 days of grace period for CBB release.
The main mantra of Windows as a service is a continuous evolution. So, what is the challenge of the constant development and deployment from an organization’s perspective? It’s mainly the size of Windows 10 feature updates and quality updates. Did Microsoft develop an entirely proven echo system to deliver all these updates with the existing enterprise network?
In my opinion, no, they are not. For example, as part of a feature update, an organization needs to deploy 3.6 GB of data to each machine every year. The same situation is there for cumulative quality updates. What is the solution to deliver this huge chunk of binaries to the end-user devices?
Adaptiva OneSite can help organizations to deliver a huge chunk of content to all end-user devices.
- OneSite automates many of the tasks around Windows 10 deployment, as well as ongoing deployment of feature and quality updates, significantly reducing the amount of time it takes a system administrator.
- OneSite’s predictive bandwidth harvesting technology is the only solution that lets you safely deliver feature and quality updates worldwide with: no throttling to slow down delivery, and no scheduling for after-hours—deploy content any time of the day without worry.
- To learn more about how Adaptiva OneSite can help your organization manage WaaS (Windows as a Service), visit: http://www.adaptiva.com/windows-10/
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…