1. with Configuration Manager, MDT, and Intune
Deploying Windows 10
with Configuration Manager, MDT, and Intune
Aaron Czechowski
@AaronCzechowski
blogs.technet.com/configmgrteam
Michael Niehaus
@mniehaus
blogs.technet.com/mniehaus

2. Aaron Czechowski Washington, USA Senior Program Manager
17 years professional experience 8
3 years on ConfigMgr PG
Senior Program Manager
#MMSMOA

3. Michael Niehaus @mniehaus Redmond, WA, USA
20 years with SMS/ConfigMgr
12 years with Microsoft
3 years with Windows product management
Director of Product Marketing
com/mniehaus
#MMSMOA

4. Deployment methodologies
Imaging
Bare metal, Wipe and Load/Refresh, and Replace
Major system changes
Start “clean”
XP/Vista to 10
Upgrading
Swap OS and keep apps, data and settings
Win7/8 to 10
Keep overall configuration
New with Windows 10!
Provisioning
Transform vanilla device to enterprise-ready
Mobile users with off-the-shelf devices
SMB customers
Servicing
Windows as a Service
Windows 10 build-to-build upgrades

5. Windows 10 branch summary
Scenarios
Availability
Time in Market
Edition
Current Branch (CB)
Consumers
BYOD
Test systems
Features available 2-3 times a year
Regular security updates
1 branch in market at a time
Consume via Windows Update, WSUS or Configuration Manager
~4 months
Home
Pro
Enterprise
Education
Current Branch for Business (CBB)
Knowledge Workers
Salesforce
Road warriors
Features available 2-3 times a year
Regular security updates
2 branches available simultaneously
Consume via Windows Update, WSUS or Configuration Manager
4-8 months
Ability to defer updates
Pro
Enterprise
Education
Long Term Servicing Branch (LTSB)
Factory floor machines
Air Traffic Controllers
Emergency Room devices
No new functionality
Regular security updates
Branches available every 2-3 years
Consume via WSUS or Configuration Manager
5 years of mainstream support
5 years of extended support
Enterprise
Education

6. Imaging Windows 10

7. Wait, why do we still need imaging?
You can’t upgrade, service or provision a blank disk
Some scenarios don’t support upgrade (see upgrade section for details)
Do you trust your OEM to provide a clean, factory- default install of Windows?

8. Imaging for each branch
Long Term Servicing Branch (LTSB)
Business as usual
Current Branch (CB)
Revise every ~four months
Current Branch for Business (CBB)
Revise every ~eight-twelve months
Tips
Build upgrades cannot currently be offline serviced
Use MDT or Configuration Manager for process automation of image creation

9. Requires the Windows 10 ADK
MDT 2013 Update 1
Released in September
See for details
Requires the Windows 10 ADK
Available on Microsoft Hardware Dev Center us/windows/hardware/dn aspx#deploy
Full support for Windows 7 – Windows 10 imaging
ConfigMgr integration follows Windows 10 ADK

10. Configuration Manager
Specifically
System Center 2012 Configuration Manager SP2
System Center 2012 R2 Configuration Manager SP1
Windows 8.1 ADK
For existing deployments, keep as-is
For new Windows 10 deployments, create a Windows PE 10 boot image on a separate computer
Windows 10 ADK
Uninstall Windows 8.1 ADK, install Windows 10 ADK, restart
Windows PE 3.1, Windows PE 5 boot images can still be used, but no longer customizable
Create new Windows 10 boot images, customize in console
Create new USMT 10 package
The new Configuration Manager
Requires the Windows 10 ADK

11. Upgrading to Windows 10

12. Why Upgrade? Preserve applications, drivers, user data and settings
Reduce upfront testing and deployment prep
Compared to refresh, upgrade is…
Faster – 30 to 60 minutes, on average, to upgrade
Smaller – file size is just the default OS media, no applications
More robust – “bulletproof” rollback on failure to functional downlevel system
Zero ADK dependencies
Use it to supplement existing deployment scenarios
Refresh, replace, and bare metal
Another tool in the OS deployment toolbox

13. Configuration Drift/Change
Upgrade vs Refresh
Continue to use refresh (wipe and load) when…
Configuration Drift/Change
Domain membership
Local Administrators
Bulk application swap
Fundamental Change
Disk partitioning
BIOS -> UEFI
x86 -> x64
Base OS language
Custom Requirements
WinPE offline operation
Custom base image
3rd party disk encryption

14. Assessing Readiness Windows Setup compat scan
A new setup.exe parameter (/compat ScanOnly), append to same command line used to upgrade
Requires deploying entire media content, not just setup.exe
Runs same setup checks, just does not start upgrade
Requirements: hardware, power, etc.
Compatibility: apps, devices
Returns known exit codes, including separate for “success”
Common Return Codes
Description
MOSETUP_E_COMPAT_SCANONLY (0xC )
No compat issues (“success”)
MOSETUP_E_COMPAT_INSTALLREQ_BLOCK (0xC )
Actionable compat issues, like Apps
MOSETUP_E_COMPAT_MIGCHOICE_BLOCK (0xC )
Selected migration choice is not available, like Enterprise to Professional
MOSETUP_E_COMPAT_SYSREQ_BLOCK (0xC )
Not eligible for Windows 10
MOSETUP_E_INSTALLDISKSPACE_BLOCK (0xC190020E)
Not enough free disk space

15. Windows 10 Upgrade MDT 2013 Update 1
Configuration Manager Technical Preview 3

16. Provisioning Windows 10

17. Simplicity of provisioning
Plan
Create Provisioning Package
New Hardware (OEM Default)
Apply Provisioning Package
Ongoing Servicing

18. Creating a provisioning package
Windows Imaging and Configuration Designer
Windows 10 ADK component
Microsoft Intune
Configuration Manager (Technical Preview 2)
What can be provisioned:
Initial
Setup
Edition
Upgrade
Certificates
Connectivity Profiles
Management Enrollment
Modern
Applications
Win32 Applications
Enterprise Policies
Offline
Content
Browser Settings
Start Menu Customization
Assigned Access

19. Applying a provisioning package
At OOBE (out-of-box experience)
5 taps on button to open provisioning menu
Consume from removable media (SD/USB) or NFC
During runtime
Click on .PPKG file from
Local storage
Removable media
URL
Embedded in the image
Can be integrated with ConfigMgr OSD, MDT and WDS

20. Provisioning Packages
Windows Imaging and Configuration Designer

21. Servicing Windows 10

22. Reduce device management and operational costs Deployment flexibility
Windows as a Service
Keep Windows up to date
New features as they are ready
Security updates
Predictable release timing
Reduce device management and operational costs
Deployment flexibility
Time to test and deploy
Standardize ecosystem

23. Windows 10 branch summary
Scenarios
Availability
Time in Market
Edition
Current Branch (CB)
Consumers
BYOD
Test systems
Features available 2-3 times a year
Regular security updates
1 branch in market at a time
Consume via Windows Update, WSUS or Configuration Manager
~4 months
Home
Pro
Enterprise
Education
Current Branch for Business (CBB)
Knowledge Workers
Salesforce
Road warriors
Features available 2-3 times a year
Regular security updates
2 branches available simultaneously
Consume via Windows Update, WSUS or Configuration Manager
4-8 months
Ability to defer updates
Pro
Enterprise
Education
Long Term Servicing Branch (LTSB)
Factory floor machines
Air Traffic Controllers
Emergency Room devices
No new functionality
Regular security updates
Branches available every 2-3 years
Consume via WSUS or Configuration Manager
5 years of mainstream support
5 years of extended support
Enterprise
Education

24. Configuration Manager 2012
Specifically
System Center 2012 Configuration Manager SP2
System Center 2012 R2 Configuration Manager SP1
Full compatibility with existing features
Windows 10 deployment, update and management
Cumulative updates
CU1 released in August
CU2 coming soon
Windows 10 branch specifics
Supports Windows 10 LTSB 2015
Supports first two builds of Current Branch (RTM, November update)
The new Configuration Manager is required for future CB/CBB builds

25. Configuration Manager future
New version of Configuration Manager in Q4 CY15
Technical Preview available now
Brings Windows 10 full support
Deployment, upgrade, and management
Plus new features
Service pack-style in-place upgrade
New Configuration Manager servicing model
Update features and functionality
Supports current and future Windows 10 LTSB and CB/CBB
To go fast with Windows, you need to go fast with ConfigMgr

26. 2012 service packs and cumulative updates
Servicing Guidance
2012 service packs and cumulative updates
System Center 2012 Configuration Manager 2012 SP2 CU1
System Center 2012 R2 Configuration Manager SP1 CU1
Plan for Cumulative Update 2 soon
Start deploying Windows 10 (LTSB, CB or CBB)
Plan on upgrade to next version of ConfigMgr
Start in CY15 Q4, complete by CY16 H2
Otherwise deploy Win10 LTSB until infrastructure upgrade

27. Windows 10 Servicing
Configuration Manager

28. Discuss…
Ask your questions-real world answers!
Plenty of time to engage, share knowledge.
Evaluations: Please provide session feedback by clicking the EVAL button in the scheduler app (also download slides). One lucky winner will receive a free ticket to the next MMS!
Session Title: Deploying Windows 10 with Configuration Manager, MDT, and Intune
SPONSORS