500 likes | 509 Views
Learn about the latest in Windows 10 deployment, including strategies, best practices, and tips for a successful deployment. Understand the different deployment stages, audience targeting, application compatibility, and how to deploy to different types of systems. Discover the benefits of the Current Branch for Business and Long Term Servicing Branch, as well as in-place and provisioning deployment methods.
E N D
What’s New in Windows 10 Deployment Michael Niehaus M317
Only 1580 days until the end of supportfor Windows 7 Windows 7 end of support date: January 14, 2020
Windows as a ServiceEstablishing a rhythm Microsoft Insider Preview Branch Current Branch Current Branch for Business Engineering builds Broad Microsoft internal validation Users 10’s of thousands Customer Internal Ring I Customer Internal Ring II Customer Internal Ring III Several Million Customer Internal Ring IV Hundreds of millions *Conceptual illustration only
What to Deploy Ongoing engineering development Windows Insider Preview Branch Current Branch For Business Current Branch Feedback and asks Specific feature and performance feedback Application compatibility validation Deploy to appropriate audiences via WUB Test and prepare for broad deployment Stage broad deployment via WU for Business Long Term Servicing Branch* Lab machines Early adopters Initial pilots IT devices Information workers General population Specialized systems Factory floor, point-of-sale, etc. Deploy for mission critical systems via WSUS
Current Branch vs. Current Branch for Business Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update If you are using WSUS or ConfigMgr, the setting doesn’t really matter. Affects Windows Update.
Current Branch for Business vs. Long Term Servicing Branch Long Term Servicing Branch (LTSB) Current Branch for Business (CBB) Capabilities Recommended Enterprise use scenario General information worker systems; salesforce, etc. Special systems: Air Traffic Control; Hospital ER, etc. Value of the latest features as they are released Several months to consume feature updates 1st party browsing choices Microsoft Edge, IE 11 IE 11 Support for Universal Office and some 1stparty Universal apps Support for Win 32 Office Ongoing security updates for the lifetime of the branch Ability to load universal apps No feature upgrade required to stay supported
Current Branch for Business vs. Long Term Servicing Branch Long Term Servicing Branch (LTSB) Current Branch for Business (CBB) Capabilities Transform Pro to Enterprise Bulk Upgrade from WU Pro only Bulk upgrade using media Microsoft Windows 10 Enterprise Microsoft Windows 10 Enterprise 2015 LTSB
When to deploy Windows Insider Preview Branch Current Branch For Business Current Branch Specific feature and performance feedback Application compatibility validation Deploy to appropriate audiences via WUB Test and prepare for broad deployment Stage broad deployment via WU for Business Evaluate Pilot Deploy 8 months (minimum) 4 months (minimum) 8-12 months of active development 12 month deployment (minimum)
When to deploy Pilot Pilot Pilot Deploy Deploy Deploy Evaluate Evaluate Evaluate • Be prepared to jump from one release to the next • Don’t try to skip one, as it compresses the deployment timeline too much
Wipe-and-Load Traditional process Capture data and settings Deploy (custom) OS image Inject drivers Install apps Restore data and settings Still an option for all scenarios How to deploy In-Place Let Windows do the work Preserve all data, settings, apps, drivers Install (standard) OS image Restore everything Recommended for existing devices (Windows 7/8/8.1) Provisioning Configure new devices Transform into an Enterprise device Remove extra items, add organizational apps and config New capability for new devices
Moving In-place Preferred option for enterprises Simplified process, builds on prior experience • Supported with Windows 7, Windows 8, and Windows 8.1 • Consumers use Windows Update, but enterprises want more control • Use System Center Configuration Manager or MDT for managing the process • Uses the standard Windows 10 image • Automatically preserves existing apps, settings, and drivers • Fast and reliable, with automatic roll-back if issues are encountered • Popular for Windows 8 to Windows 8.1 • Piloted process with a customer to upgrade from Windows 7 to Windows 8.1, as a learning process • Feedback integrated into Windows 10 to provide additional capabilities for automation, drivers, logging, etc. • Working with ISVs for disk encryption
Moving In-place MDT 2013 Update 1 ConfigMgrv.Next
When not to use in-place upgrade? Changing from Windows x86 to x64 Systems using Windows To Go, Boot from VHD Changing from legacy BIOS to UEFI Dual boot and multi-boot systems Image creation processes (can’t sysprep after upgrade) Using certain third-party disk encryption products
Support for Windows 10 CONFIGURATION MANAGER v.NEXT ENHANCEMENTS Upgrade task sequence Windows 10 configuration support
Provisioning, not reimaging Take off-the-shelf hardware Device is ready for productive use Transform with little or no user interaction
Provisioning, not reimaging User-driven, from the cloud IT-driven, using new tools • Company-owned devices:Azure AD join, either during OOBE or after from Settings • BYOD devices:“Add a work account” for device registration • Automatic MDM enrollment as part of both • MDM policies pushed down: • Change the Windows SKU • Apply settings • Install apps • Create provisioning package using Windows Imaging and Configuration Designer with needed settings: • Change Windows SKU • Apply settings • Install apps and updates • Enroll a device for ongoing management (just enough to bootstrap) • Deploy manually, add to images
Dynamic Provisioning DEMO
Traditional Deployment Enhancements to existing tools Minimal changes to existing deployment processes • New Assessment and Deployment Kit includes support for Windows 10, while continuing to support down to Windows 7 • Minor updates to System Center 2012 to add support • Minor updates in Microsoft Deployment Toolkit 2013 Update 1 to add support • Will feel “natural” to IT Pros used to deploying Windows 7 and Windows 8.1 • Drop in a Windows 10 image, use it to create your new master image • Capture a Windows 10 image, use it for wipe-and-load deployments
App & Device Compatibility Hardware requirements are unchanged Strong desktop app compatibility Windows Store apps are compatible Internet Explorer enterprise investments
Enterprise Investmentsfor Internet Explorer 11 Help with Compatibility Issues Enterprise Mode, offering improved Internet Explorer 8 compatibility and document type overrides Enterprise Site Discovery Toolkit, to better understand how users are browsing All capabilities will be carried forward to Windows 10 A Natural Stepping Stone to Windows 10 Migrate to Internet Explorer 11 on Windows 7 (before 2016) to prepare http://blogs.msdn.com/b/ie/archive/2014/08/07/stay-up-to-date-with-internet-explorer.aspx Legacy Web Apps
Application Compatibility TestingWindows as a Service requires a new approach Identify mission-critical applications and web sites Focus testing effort on just these apps Leverage internal flights for testing other applications and web sites From initial pilot groups to large populations of users Define groups to ensure broad hardware and software coverage prior to broad deployment React to issues reported, remediate issues before expanding Continue to pressure ISVs to adopt new model It works vs. it is supported by the ISV Submit http://GetHelp requests when customers are having issues, DX can help
Infrastructure Upgrades needed • Activation • Windows update needed to support Windows 10 with existing KMS servers (Windows Server) • https://support.microsoft.com/en-us/kb/3058168 • Supports Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2 • Support for Windows 7 and Windows Server 2008 R2 coming by October • New KMS and MAK keys needed, available on VLSC on 8/1 • Continued support for Active Directory-based activation
Infrastructure Upgrades needed • Microsoft Desktop Optimization Pack • New service packs needed for Windows 10 support, available soon
Other Notable Changes • Compact OS • For devices with low disk space (16GB/32GB), >GB savings, reduced growth over time with updates being compressed as well • Much easier to deploy (DISM switch), simpler partition structure (no extras), transparent to users • Next generation WIMBoot with fewer restrictions • Not beneficial on devices with larger volumes • Reset/Refresh • No more recovery partition needed or used • Reconstructs OS from (patched) side-by-side store (SYSTEM32\SXS) • OEMs will provide a provisioning package to put back customizations (drivers, apps), captured using USMT
Related Ignite NZ Sessions 1 Windows 10 in the Enterprise SKYCITY Theatre Wed 9:00am 2 What's New in Windows 10 Deployment NZ1 Wed 10:40am • Find me later at… • Hub Happy Hour Wed 5:30-6:30pm • Hub Happy Hour Thu 5:30-6:30pm • Closing drinks Fri 3:00-4:30pm 3 Upgrading to Windows 10: In Depth NZ1 Thu 10:40am 4 What's New in Windows 10 Management and the Windows Store NZ1 Thu 3:10pm
Resources Microsoft Virtual Academy TechNet & MSDN Flash • Free Online Learning http://aka.ms/mva • Subscribe to our fortnightly newsletter http://aka.ms/technetnzhttp://aka.ms/msdnnz • Sessions on Demand http://aka.ms/ch9nz