but we learned some things we had to do better
TRANSCRIPT
What’s New and Upcoming with OS Deployment in System Center Configuration Manager and the Microsoft Deployment Toolkit
Kristina HotzJason Githens
EM-B326
Upgrading to Windows 10 with System Center Configuration Manager
Revisiting the past—the historical challenges of refreshing and upgrading Windows (as if you didn’t know)Moving forward—improvements in refresh, and an all-new, awesome upgrade experienceThe real-world—Overview of Microsoft IT’s upgrade to 8.1Going under the hood on the new upgrade experience, command-line switches and all
Introducing the deployment tools for Windows 10What’s new with the Microsoft Deployment Toolkit and the ADKWindows Image Configuration Designer and Provisioning Packages (when/why ADK, SCCM, MDT, WICD)
Demos, Demos, and Demos
Key Takeaways
The refresh challengeTakes a LONG time end-to-end
Large content size, image and all the apps
Failures can be difficult to recover from—lost
productivity
Complex processes to migrate data, settings, apps
Upgrading Configuration Manager to the latest
version
The improved refresh experience
New, Window 10 ADK now support N-3, from Windows 10 back to
Windows 7Support for Windows 10 deployments on your current Configuration Manager version (back to ConfigMgr 2012 SP1)
New version of MDT (more on MDT later)
Driver management UI improvements
BranchCache with WinPE (to help with the large payload problem)
Improved task sequence resilience for unknown reboots
Improved SMSTS logging logic (file size and how values are
stored/retained)
• 97% success rate in deployments and help desk calls were reduced by 48%.
• Using the available standard deployment images reduced complexity.
• The upgrade preserved user data, settings, and applications.• The deployment method leveraged System Center 2012
Configuration Manager.• Reporting leveraged the data collected in System Center 2012
Configuration Manager to gain insights into upgrade deployment results.
• Bottom line: The Windows 8.1 upgrade had lower cost than traditional operating system deployments.
So, we did
But we learned some things we had to do better . . .
The upgrade challengeReliance (and hope) that the Configuration Manager client recovers after being run over by a truck
Difficult to perform critical pre and post-upgrade actions
Lack of status (radio silence) after upgrade
Complexity managing key content like drivers, language
packs, and other applications
The all-new upgrade experienceDeep integration of Windows setup with Configuration Manager Task Sequence
Pre and post processing actions integrated into upgrade
Drivers and language packs sourced through Configuration Manager in upgrade workflow
Configuration Manager client doesn’t have to recover
Upgrade model works on existing ConfigMgr versions (back to ConfigMgr 2012 SP1)
Anatomy of the new setupSetup.exe /Auto Upgrade /Quiet /compat IgnoreWarning /NoReboot /PostOobe %SystemDrive%\_vNextUpgrade\setupcomplete.cmd /PostRollback %SystemDrive%\_vNextUpgrade\setuprollback.cmd
setupcomplete.cmd# trigger and wait for the CM client to repair on the new OS $process = Start-Process $env:WinDir\ccmsetup\ccmsetup.exe -ArgumentList "/remediate:client" -Wait -NoNewWindow –PassThru #enable health tasks
schtasks /change /tn "\Microsoft\Configuration Manager\Configuration Manager Health Evaluation" /enable | Create-LogEntry
schtasks /change /tn "\Microsoft\Configuration Manager\Configuration Manager Idle Detection" /enable | Create-LogEntry
schtasks /change /tn "\Microsoft\Configuration Manager\Configuration Manager Maintenance" /enable | Create-LogEntry
setupcomplete.cmd# start and wait for the task sequence $service = Get-Service -Name "smstsmgr" Set-Service -Name $service.Name -StartupType Automatic Start-Service -Name $service.Name $service.WaitForStatus("Stopped") # Disable Client Provisioning ModeInvoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $False
The Toolkit(s)Microsoft Deployment Toolkit v.Next (MDT)• Windows 10 Deployment Support• Windows 10 Upgrade Support• Updated Task Sequence binaries to the ConfigMgr v.Next Task
Sequence• Removed deprecated components node from the workbench• Making LTI and ZTI more accessibility compliant• All documentation now on TechNet (removed legacy CHMs and
DOCX)
NEW! Windows Image and Configuration Designer
Windows Image and Configuration Designer
is used to
• Build a customized Mobile or Desktop
image • Create a provisioning package that allows
to customize Windows devices without re-imaging.
Provisioning Package can be • Consumed from removable media
(SD/USB)• Applied through USB tether or NFC tag• Attached to email or downloaded from
network• Embedded in the OS image
WHAT can be customized by provisioning package:
• First run experience customization• Bulk enrollment into MDM• Application - Store (with VPP), Line of
Business, Win32• Enterprise policies - Security restrictions,
encryption, update settings• Enterprise profiles - Wi-Fi, VPN, Email• Root, CA and Client Certificates• Offline content – documents,
audio/video, pictures
If you are a . . .
And want to . . . Use . . .
System Builder or OEM
Configure and apply Windows images on new desktop and mobile devices
WICD to create full image media
Small organization
Customize new desktop and mobile devices WICD to create provisioning package
Configure and apply Windows images on new desktop devices
WICD to create full image media
Mid-sized organization
Create and deploy custom Windows images on new or existing desktop devices
MDT and/or Configuration Manager to create and deploy custom image
Configure and apply Windows images on new desktop devices
WICD to create media
Customize mobile devices WICD to create provisioning package
Large organization
Create and deploy custom Windows images on new or existing desktop devices
MDT and/or Configuration Manager to create and deploy custom image
Customize new desktop and mobile devices WICD to create provisioning packageNote: Combinations of tools are possible, such as putting WICD provisioning package in custom SCCM, MDT, or OEM image
Bringing it all together . . .
Upgrade is a first class citizen—try it!Refresh is still an option, and getting betterWe’re giving you more tools, and making the existing ones better
Breakout SessionsTuesday, October 28th, 3:15 PM-4:30 PM: EM-B216 - Enterprise Client Management with System Center Configuration Manager and Intune
Wednesday, October 29th, 8:30 AM – 9:45 AM: EM-B321 - Infrastructure Deployment for Mobile Device Management with System Center Configuration Manager and Intune
Wednesday, October 29th, 5:00 PM – 6:15 PM - Securing Mobile Device Access to Corporate Resources with Intune
Thursday, October 28th, 3:15 PM-4:30 PM: EM-B312 - Mobile Application Management with Intune
Friday, October 31st, 8:30 AM – 9:45 AM: EM-B317 - Configuring Corporate-Owned Mobile Devices with Intune
Related content
Related contentInstructor-Led Labs
Tuesday, October 28th, 3:15 PM – 4:30 PM: EM-IL200 Introduction to Cloud-Based Mobile Device Management with Intune
Microsoft Solutions Experience Location (MSE)
Find Us Later At. . .
Resources
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
Developer Network
http://developer.microsoft.com
TechNet
Resources for IT Professionals
http://microsoft.com/technet
Sessions on Demand
http://channel9.msdn.com/Events/TechEd
Please Complete An Evaluation FormYour input is important!TechEd Schedule Builder CommNet station or PC
TechEd Mobile appPhone or Tablet
QR code
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.