This is the second article in a series of articles in which I write about my experiences managing Windows 10 with ConfigMgr 2012 R2. In the first article, I reviewed steps for installing Windows 10 ADK and creating new boot images in ConfigMgr. In this article, I’ll review the steps for upgrading MDT 2013 integrated with ConfigMgr to MDT 2013 Update 2.
Note that while MDT 2013 Update 1 is required for managing Windows 10, MDT 2013 update 2 is NOT required. Also Update 2 includes no major features over update 1, but I’m interested in user experience enhancements for Windows 10 in-place upgrade task sequences.
Download and Install MDT 2013 Update 2
You can get this from the Microsoft Download Center. After you download the media, Close the ConfigMgr console, and run the MDT 2013 Update 2 installer. Click Next, accept the terms, accept default settings and install. This automatically uninstalls MDT 2013. Click Finish to Exit.
Integrate MDT with ConfigMgr
After installing MDT, let’s integrate it with ConfigMgr. This is required even if you’ve done this with MDT 2013.
Locate the newly installed Microsoft Deployment Toolkit application in the start menu, and expand it. Select and right click Configure ConfigMgr Integration, and Run as Administrator.
Review the options, and select the radio button for Install the MDT extensions for Configuration Manager. Ensure that the options for Install the underlying checkboxes are also checked.
Click Next and Finish.
Create a Deployment Share
NOTE: If you have an existing share, you can simply upgrade and then update the share for the updates.
In this case, I’m going to create a new share.
Navigate to the start menu, and locate the Deployment Workbench, and right click to Run as Administrator. Click on Deployment Shares, and right-click it and select New Deployment Share.
In the resulting Wizard, enter the deployment share path, and click Next
Give it a name, and click Next.
select the defaults and click Next twice
You should now see the various share options in the Deployment Workbench.
Next, we will enable monitoring for the Share. This will prove useful when we create DaRT boot images for problem diagnostics.
Right-click the share, and select properties.
In the resulting window, click on the Monitoring tab, and check the box to Enable Monitoring for this deployment share, and click OK.
NOTE: Take note of these settings, as we will make use of them in our Customsettings.ini file which we will create after creating a new MDT task sequence.
Create a New MDT Task Sequence
Open the ConfigMgr console, and navigate to Software Library | Operating Systems, right click on Task Sequences and choose Create MDT Task Sequence.
Choose the Client Task Sequence template.
fill in the Task Sequence name and comments
Enter details as necessary. You can join a domain, but I’ll leave this as a Workgroup
Select the default Capture settings, and in the next window, choose to specify an existing boot image package (Only because we have already imported our Windows 10 Boot images). Click Ok and Next
Select the Default settings until you get to MDT Package.
Check the radio button to Create a new Microsoft Deployment Toolkit Files Package, and click Next
fill in the relevant details about the MDT toolkit files.
For OS Image, specify an existing image. In my case I’ve already imported a Windows 10_1511 OS Image
select the default (Zero Touch) deployment method
and specify your Configuration Manager Client Package
In the USMT Package window, opt to Create a new USMT package, and specify the path and package source folder
enter the package properties
select the Create a new settings package radio button, and specify the package source folder
enter the settings package properties details
Click Next on Sysprep Package
Click Next on the summary and Finish.
Make sure to distribute your newly created packages to your DPs
This concludes this article. In the next article, I’ll show you how to configure monitoring and integrate DaRT 10 with ConfigMgr.
Latest posts by Chiyo Odika (see all)
- Azure Monitor Management solution for RDS, Windows VDI and Citrix - February 28, 2019
- Hybrid Cloud Print Known Issues and Workarounds - February 28, 2019
- Hybrid Cloud Print with Passthrough Authentication – Detailed steps - February 28, 2019