A brand new way of building, deploying, and servicing Windows
Millions 10’s of thousands Users Broad Microsoft Engineering Microsoft Insider Preview builds internal Branch validation Time ~6 months
Unmatched flexibility and control, depending on needs Windows Insider Preview Branch Current Branch Current Branch for Business Long Term Servicing Branch Specific feature and performance feedback Deploy to appropriate audiences Application compatibility Test and prepare for broad Specialized systems validation deployment Information workers General population Deploy for mission Early adopters, initial pilots, critical systems NUMBER OF DEVICES IT devices Benefits from new features Test machines, small pilots No need for frequent new Begins broad deployment features (or any sort of change) Too expensive for general population STAGE Release
With Windows 7 and 8, servicing choices added complexity and cost, increased fragmentation, and reduced quality What we What customers are testing are running Y YY Windows 7 Test Lab PC: Typical Windows 7 PC: Fully Patched Selectively Patched
With Windows 10 servicing, consistency and simplicity are paramount Changes being considered for older Windows releases as well
Windows Insider New Windows 10 Preview Branch Release Specific feature and Deploy to pilot audiences Deploy to all audiences, performance feedback in waves to reduce risk Validate and prepare Application compatibility for broad deployment validation Deploy / Use Grace 60 days 6+ months of active ~4 months 12+ months development 16+ months to validate, deploy, and use each release Evaluate Pilot Deploy / Use The process repeats…
Traditional deployment (every 3-5 years) 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 Apps Infra Imaging Deploy Windows as a service (twice per year) 2009 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 Apps Infra Imaging Deploy
1 Configure Insider PCs • Lab or secondary PCs • Enough to explore new features, measure compatibility 2 Identify special PCs • Deploy Windows 10 Enterprise LTSB • Limited numbers (we hope) 3 Recruit volunteers for pilots • Willing participants who will provide feedback • Cover the broadest set of apps and devices possible 4 Divide broad population of PCs • Standard deployment best practice • Focus on risk reduction, minimizing disruption
Understand Current Branch vs. Current Branch for Business Each Windows 10 release has its own lifecycle Starts as Current Branch, progresses to Current Branch for Business Each device can specify a preference for when to move forward to the next release Defer for CBB Each deployment or management tool can implement this idea differently
Long Term Servicing Current Branch Branch (LTSB) Capabilities for Business (CBB) General information worker Special systems: Recommended Enterprise use scenario systems; salesforce, etc. Air Traffic Control; Hospital ER, etc. Value of the latest features as they are released Several months to consume feature updates 1 st party browsing choices Microsoft Edge, IE 11 IE 11 Support for Universal Office and some 1 st party Universal apps Ability to load universal apps Support for Win 32 Office Ongoing security updates for the lifetime of the branch No feature upgrade required to stay supported
Microsoft Windows 10 Enterprise Microsoft Windows 10 Enterprise 2015 LTSB (Current Branch, Current Branch for Business)
Outstanding compatibility means a smooth migration from Windows 7 or Windows 8.1
Analyze the machine as a whole Early detection of issues with flighting Aggressive approach to removing upgrade blocking apps and drivers after evaluating user experience Data driven approach on the long tail of apps T argeting of upgrades starting with the most ‘healthy’ machines
Differences Limited enterprise telemetry available Some apps needs to be supported by ISV and / or verified in house IT can create custom mitigations to make experience seamless Web app compat is a concern
Get links to Windows 10 ISV support statements http://www.readyfor10.com We are actively engaged with ISVs, to ensure full support for Windows as a service
Call to action • Understand that Windows as a service requires some changes • Be an insider • Get all your drivers up on WU • Be able to position CB, CBB and LTSB • Implement a Windows 10 servicing process
Recommend
More recommend