A Geeks Guide for upgrading MDT 2013 to MDT 2013 Update 1

In this post you learn to upgrade an existing MDT 2013 environment, with or without ConfigMgr integration, to MDT 2013 Update 1. The guide is divided in two parts:

• Upgrading MDT 2013 Lite Touch (standalone) to MDT 2013 Update 1
• Upgrading MDT 2013 Zero Touch (integrated with ConfigMgr 2012 R2) to MDT 2013 Update 1

Update September 16, 2015: MDT 2013 Update 1 has been re-released, new build (8298). Read the announcement from the product team:

MDT 2013 Update 1 re-released (build 8298)
http://blogs.technet.com/b/msdeployment/archive/2015/09/15/mdt-2013-update-1-re-released-build-8298.aspx

Download links

MDT 2013 Update 1 (build 8298) download link: http://www.microsoft.com/en-us/download/details.aspx?id=48595

Now, back to the upgrade guides!

Upgrading MDT 2013 Lite Touch (standalone) to MDT 2013 Update 1

Note #1: Don’t forget to create new task sequences after the upgrade, the MDT 2013 Update 1 task sequence templates have updated logic on disk partitioning (and a few other updates).

Note #2: Not applicable for this guide, but please note that new deployment shares will be locked down by default (security)

Note #3: There is a known issue in Windows ADK 10 (which MDT uses) that you should know about. It’s not the end of the world, there is a workaround:

Updating the deployment share breaks on Windows Server 2012 R2 if you have a fast disk

So, the injection of the MDAC component into the MDT 2013 Update 1 boot image breaks when running on Windows Server 2012 R2, in combination of having a fast disk (SSD). This is a known bug in the Windows ADK 10.

Keith Garner has posted a more detailed explanation on the issue:  http://keithga.wordpress.com/2015/08/17/mdt-2013-uberbug01-mdac-and-the-fast-machine/

Workaround #1: Update the deployment from a Windows 10 machine with MDT 2013 Update 1 and Windows 10 ADK installed (open deployment share remotely).

Workaround #2: Disable the MDAC from the MDT boot images, no harm if you are not using the MDT database.

Continue with the real upgrade work

Other than above, upgrading MDT 2013 Lite Touch to MDT 2013 Update 1 is quite straight forward, simple follow these steps:

1. Make a backup copy of your deployment share (yes, complete backup).
2. Check if there is a pending reboot, use the http://gallery.technet.microsoft.com/scriptcenter/Get-PendingReboot-Query-bdb79542 from TechNet Gallery, written by Brian Wilhite. To run the cmdlet, first load the script as a function by "dot sourcing" the Get-PendingReboot.ps1 script. Run . .\Get-PendingReboot.ps1, and then run the Get-PendingReboot command.

   Note: The script also supports the -ComputerName parameter if you want to run it on remote machines.

   
   

   
   Running the Get-PendingReboot command after “dot sourcing” the Get-PendingReboot.ps1 script.

3. Uninstall Windows ADK 8.1, and then install Windows ADK 10. Select the following components:

   Deployment Tools
   Windows Preinstallation Environment (Windows PE)
   Imaging And Configuration Designer (WICD)
   User State Migration Tool (USMT)

4. Reboot the machine (just for good measure).
5. Install MDT 2013 Update 1 (automatically uninstalls MDT 2013)
6. Using Deployment Workbench, right-click the deployment share and select Upgrade Deployment Share.
7. Repeat step 6 if you have more deployment shares.
8. After upgrading the deployment share, using Deployment Workbench, right-click the deployment share and select Update Deployment Share. This will create new boot images.

   Note: If the update fails, review the workarounds in the beginning of this post:  

9. Repeat step 8 if you have more deployment shares.
10. Now the fun begins! You really need to create new MDT task sequences. The MDT 2013 Update 1 task sequence templates have updated logic on disk partitioning (and a few other updates).
11. If using WDS for PXE booting MDT boot images, replace the boot images with the new ones.

Upgrading a deployment share.

Updating the deployment share (after upgrade), to create new boot images.

Replacing the old MDT 2013 boot images with MDT 2013 Update 1 boot images.

Upgrading MDT 2013 Zero Touch (integrated with ConfigMgr 2012 R2) to MDT 2013 Update 1

Note #1: Don’t forget to create new task sequences after the upgrade, the MDT 2013 Update 1 task sequence templates have updated logic on disk partitioning (and a few other updates).

Note #2: There is a known issue in Windows ADK 10 (which MDT and ConfigMgr 2012 R2 SP1 uses) that you should know about. It’s not the end of the world, there is a workaround:

Creating boot images with additional components (like PowerShell) breaks if you have a fast disk

Injection of the additional component into the ConfigMgr boot image may break when running on Windows Server 2012 R2, in combination of having a fast disk (SSD). This is a known bug in the Windows ADK 10.

Workaround: Install the ConfigMgr Console on a Windows 10 machine with MDT 2013 Update 1 and Windows 10 ADK installed. Create the boot images from that console.

First, MDT 2013 Update 1 Zero Touch is supported on both ConfigMgr 2012 R2 and ConfigMgr 2012 R2 SP1 (SP2), but I do recommend to upgrade to Windows ADK 10, ConfigMgr 2012 R2 SP1 CU1 + the KB3084586 hotfix. Windows ADK 10 allows for managing WinPE 10 boot images from the console, adding drivers etc. CU1 fixes Windows 10 driver import, and the KB3084586 hotfix fixes an issue where driver packages are bloated. I also recommend installing KB3089193 to fix an issue with offline servicing of Windows 10 updates.

Anyway, that means there are two main parts to the upgrade:

• Upgrade ConfigMgr 2012 R2 to ConfigMgr 2012 R2 SP1 CU1 + KB3084586 + KB3089193
• Upgrade the MDT 2013 integration in ConfigMgr to MDT 2013 Update 1

Upgrade ConfigMgr 2012 R2 to Windows ADK 10 and ConfigMgr 2012 R2 SP1 CU1 + KB3084586 + KB3089193

Before you start, since upgrading to Windows ADK 10 and ConfigMgr 2012 R2 SP1 will upgrade the default USMT from Windows ADK 8.1 to to USMT from Windows ADK 10, I recommend copy the USMT for Windows 8.1 folder somewhere else in the event you still need it.

Here are the steps for the upgrade:

1. Backup your ConfigMgr 2012 R2 server (SQL Backup, of course)
2. Copy the SQL Database to another SQL Server, and run the TESTDBUPGRADE process
3. Make a copy of the existing USMT for Windows 8.1 package, and configure the package to use the new location.
4. Uninstall Windows ADK 8.1
5. Install Windows ADK 10
6. Install ConfigMgr 2012 R2 SP1, select the upgrade option, wait until status for all components are ok.
7. Install ConfigMgr 2012 R2 SP1 CU1
8. Install KB3084586 and KB3089193 hotfixes for ConfigMgr 2012 R2 SP1 CU1

Upgrade the MDT 2013 integration in ConfigMgr to MDT 2013 Update 1

Once the ConfigMgr 2012 R2 SP1 CU1 setup is completed, you can start upgrading the MDT integration.

1. Install MDT 2013 Update 1 (automatically uninstalls MDT 2013)
2. Run the Configure ConfigMgr Integration wizard, and install the extensions
3. Create a new dummy task sequence using the Create MDT Task Sequence wizard, and select to create a new MDT package and new USMT package during that wizard.
4. Create new boot images using the Create MDT Boot image wizard.

   Note: You can also upgrade existing boot images, but I recommend leaving them as they are for now, to not break any production deployments  

5. Now the fun begins! You need to create new MDT task sequences, and of course configure them to use the new MDT package, new USMT package, and new boot images. The MDT 2013 Update 1 task sequences for example have updated logic on disk partitioning (and a few other updates).