This webinar discusses Windows 10 for enterprises and focuses on helping organizations migrate to and manage Windows 10 as a service. The webinar covers key topics like the Windows 10 release cadence, new features in recent updates, digital transformation opportunities, improving productivity with ongoing feature updates, and testing strategies for ongoing updates. It also discusses how Windows 10 enables a DevOps approach and can reduce long-term costs compared to traditional operating system deployment models.
3. Agenda
Understanding our audience
Goals of this webinar series
Key information from Interchange
Get your update process right
New feature impact
Looking forward
5. #Goals
1. Create a conversation
2. Help migrate to and manage Windows-as-a-Service
3. Provide multiple perspectives
• Multiple voices and points of view
• Short segments addressing Windows 10 issues
4. Help get the most out of Windows 10
9. Release Type
Feature Update Quality Update
Constant Enhancements
Simple
deployment
w/ Rollback
18-month
servicing
2X / year
Iterative Quality
Supersedes
Previous
Update
Fixes –
Bugs, Sec.,
Reliability
Single
Cumulative
10. Windows 10 1903
Windows 10 1809
Windows 10 1803
Windows 10 1709
2018 2019
Release Cadence
2020
Each supported for 18 months
From the date of release
12. Windows 10 Additional support
Additional 12 month servicing (not support) extensions available
(6 months free for 1607, 1703 and 1709 Enterprise)
13. Support
Release Release date End of support
End of servicing
(Enterprise &
Education)
Windows 10, version
1511
November 10, 2015 October 10, 2017 April 10, 2018
Windows 10, version
1607
August 2, 2016 April 10, 2018 October 9, 2018
Windows 10, version
1703
April 5, 2017 October 9, 2018 April 9, 2019
Windows 10, version
1709
October 17, 2017 April 9, 2019 October 8, 2019
16. Improving Productivity with Windows 10
• Continual improvements:
New features twice per year,
improving productivity
• Minimized end-user disruption:
Less change with each release
Windows XP Windows 7
Windows 10
Disruption Improvements
17. Moving from Project to Process
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015
Traditional deployment (every 3-5 years)
Apps Infra Imaging Deploy Service Packs
2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031
Windows as a service (twice per year)
Apps Infra Imaging Deploy WaaS Prep
18. Testing – Flip the script
Proactive
Testing
Data
Driven
Reactive
Testing
Current Future
19. Windows 10 = DevOps
Continues
Business
Planning
Collaborative
Development
Continuous
Testing
Continuous
Release &
Deployment
Continuous
Monitoring
Collaborative
Customer
Feedback &
Optimizations
DevOps
No more migrations
Incremental
improvements
Power is in the
process
20. TCO – Currently
How the real world look like…
• Average deployment time:
Every 5 years
• Calculation for 5 years:
10 deployments
• Break-even:
10% effort for each deployment
• Best study:
25% effort for each deployment
2017 2020
Apps Infra Imaging Deploy
*Based on information from…Microsoft…
Feature Update
Twice per year with new capabilities
18 months of servicing and support for each feature update release
Very reliable, with built-in rollback capabilities
Simple deployment using in-place upgrade, driven by existing tools
Quality Update
A single cumulative update each month with no new features
Security fixes, reliability fixes, bug fixes, etc.
Supersedes the previous month’s update
The aim should be something like this:
On top the resource consumption as it has been there in the last years
On the downside the utopic plan to adopt WaaS
The downside contains an additional huge workload for “WaaS Prep”
This is the current situation for many customers.
Starting in the WaaS model, the best achieved consumptions are currently around 25% effort of each deployment compared to the old very highly disruptive deployments.
But, this results into an additional TCO of 150% for the operational teams, and this is where you need to work on.
This means – if you continue to work with the exact same processes and techniques, you will surely have an increased effort.
How can you handle this? next slide
TURN ON THIS FEATURE TO CREATE SECURE, ISOLATED BROWSER SESSIONSWindows Defender Application Guard is one of the most important security features in Windows 10. Using Hyper-V virtualization, it offers a way to access the web in a secure, isolated session that can't install ransomware or otherwise compromise the system.https://www.zdnet.com/article/whats-new-in-windows-10-spring-creators-update/
-> Proactive Testing gives you safeness and control with a high certainty.Manual testing can be even better than just working with the information from Upgrade Readiness, because you can walk through check-lists and ensuring stability. But in an testing environment applications can behave differently and you have to invest a lot of resources. Many customers find also automated testing very promising, but remind yourself that many errors cannot be even found by automated testing. You should use proactive tests for LOB applications, Upgrade tests and (may be) applications, which are known to be problematic or self-developed.
-> Reactive Testing returns the most accurate results by creating the less effort.Reactive testing is very unconvential in IT today. Why? Because the impression for stability has been completely different in the past 20 years. Though, with the previous provided information, and speaking about Windows 10 - reactive testing creates only very small and controlled downtimes. You define the impacted computer collections and after encountering an issue, you can just retrieve the information of the blocking application/s and roll back your Windows environment for the dedicated users to the previous version. Afterwards you can just pause the deployment of the upgrade, fix the error, and then just turn the deployment on again.