This post is a summary of the “What’s New and Upcoming with OS Deployment in System Center Configuration Manager and the Microsoft Deployment Toolkit” session presented by Jason Githens and Katarina Hotz at TechEd Europe 2014 on October 28, 2014. The full recording (53 minutes) is available here: http://channel9.msdn.com/Events/TechEd/Europe/2014/EM-B326
Disclaimer: This is pre-release information, and may very well change before final release.
Update 2014-10-31: You really want to take a look at the following post by the ConfigMgr team: Sample Task Sequence and all sample scripts for upgrading to Windows 10
Fundamental direction change in setup for Enterprise organizations: Microsoft is really trying to make in-place upgrades to Windows 10 a good experience. I’m glad they are assigning resources for this, and I will believe it’s working when I see it 🙂 Please note that the current scenarios (New Computer, Refresh and Replace) will still be around, but Microsoft really want core upgrades to work.
In addition to the above, Microsoft wants to be able to roll back an upgrade, in the event the upgrade fails for whatever reason.
No need to upgrade to ConfigMgr v.Next to deploy Windows 10, even good old ConfigMgr 2012 SP1 will be able to do it.
Running the Windows 10 upgrade
In the demo Jason where using the following command line in the task sequence to launch the upgrade.
Setup.exe /Auto:Upgrade /Quiet /NoReboot /DynamicUpdate Disable /PostOobe %SystemDrive%\v_NextUpgrade /PostRollback %SystemDrive%\v_NextUpgrade
New core tools
Windows 10 ADK supports Windows 7, Windows 8.1 and Windows 10 deployments.
Windows Image Configuration Designer (WICD), pronounced Wicked ? 🙂 Is supposed to be able to build a customized mobile or desktop image, and also create provisioning packages that allow you to customize a Windows device, without re-imaging.
Personal note: The provisioning idea sounded good to me, but the idea of using WICD for image builds (if that really is the case) almost made me scream out loud… YET another tool to build images! No Thank You! We have enough tools already, stick with MDT and/or ConfigMgr, and let both OEMS, small organizations, and Enterprise use the same deployment solutions to deploy the same windows. If you (Microsoft) think MDT is too complex, then make it easier! Don’t create new solutions. I do meet a lot of OEMs and they would be thrilled to be able to use the real deployment solutions instead of having to re-invent and create everything them selves from scratch. Such as waste of resources (IMNSHO), both internally at Microsoft and at each and every customer. (End personal note).
Microsoft Deployment Toolkit v.Next (MDT) (standalone)
New upcoming version of MDT is in development, not much info presented yet, but a few items were mentioned in the session:
Windows 10 Deployment and Upgrade Support, as well as updated Task Sequence binaries
Removed deprecated components from Deployment Workbench, and making OSD more accessibility compliant.
MDT documentation will be on TechNet (removed legacy help file and DOCX)
OSD in ConfigMgr v.Next
Driver Management UI Improvements (better filtering)
Branch Office scenarios with WinPE (peer caching)
Improved Task Sequence resilience for unknown reboots and improved SMSTS logging (file size and how values are stored)
As you can see in the video, the “old” Operating System Installer node in ConfigMgr 2012 is now renamed to Operating System Upgrade Package.