Here is a quick guide on how to install Windows 10 using ConfigMgr 2012 R2 SP1 (SP2).
Note #1 : MDT 2013 is not yet updated for ConfigMgr SP1 (SP2) with Windows ADK 10, so you need to use native task sequences.
Note #2 : Windows 10 ADK is currently in technical preview, for lab and test only, not production.
Anyway, first, make sure to upgrade your ConfigMgr 2012 R2 environment to SP1 (SP2) following these instructions:
A Geeks Guide for upgrading to ConfigMgr 2012 R2 SP1 (SP2)
https://deploymentresearch.com/481/A-Geeks-Guide-for-upgrading-to-ConfigMgr-2012-R2-SP1-SP2
But before running the SP1 (SP2) upgrade process, step 3 in the guide, uninstall Windows ADK 8.1, reboot, and then install Windows 10 ADK. I used build Windows 10 ADK RC (Build 10075) in this guide.
Installing the Windows ADK 10.
Once Windows ADK 10 is installed, run through the ConfigMgr 2012 R2 SP1 (SP2) upgrade process.
‘
The ConfigMgr 2012 R2 SP1 (SP2) upgrade updating the default boot images to WinPE 10 (from the Windows ADK 10).
Deploying Windows 10
After the upgrade to SP1 (SP2) is completed, you can start prepare for Windows 10 deployments. The high level overview steps are the following:
- Since the ConfigMgr 2012 R2 SP1 (SP2) setup only updates the default boot images, if you need additional components, you need to either create a new boot image based on WinPE 10, or update the default one with any needed components (HTA, PowerShell, .NET etc.). MDT 2013 does not support the Windows 10 ADK yet, so you have to use the native ConfigMgr wizard if creating a new one.
- Update the DPs for the USMT package (Windows 10 ADK has a new version of USMT).
- Add a Windows 10 operating system image. I added Windows 10 Enterprise x64 build 10074 in this example
- Create a new native task sequence (Don’t use the MDT task sequences for now, they don’t work yet with Windows 10 ADK), do the same configuration as you would do for a Windows 7 or Windows 8.1 image
- Deploy the new task sequence, and for now set the deployment date 1 day back or so. SP1 (SP2) didn’t like when I used the default schedule (now). I got “Skipping Task Sequence because it is not active yet” in the smsts.log file.
The native Windows 10 task sequence, configured to use the default x64 boot image (to which I added HTA components for the fun of it).
The new task sequences available for deployment.
Deploying Windows 10 using ConfigMgr 2012 R2 SP1 (SP2).
Happy Deployment, Johan