In this post you learn to upgrade an existing MDT 8450 environment, with or without ConfigMgr integration, to MDT 8456. The guide is divided in two parts:
- Upgrading to MDT 8456 Lite Touch (standalone)
- Upgrading to MDT 8456 Zero Touch (integrated with ConfigMgr Current Branch 1810)
Official MDT 8456 Release Notes
My own (Johan) Release Notes for MDT 8456
- The bug in Litetouch.wsf (line 1593) regarding DaRT Integration failing for networks beginning with 169.x is still not fixed. Just change "169." to "169.254" and you're good.
- WinPE Addon for Windows ADK 10 v1809 are missing files for WPF. Simply copy BCP47Langs.dll and BCP47mrm.dll from a Windows 10 v1809 installation to Windows\System32 of the boot image. You can either use the Extra Files feature, or simply mount the boot image and add them.
MDT 8456 download link: http://www.microsoft.com/en-us/download/details.aspx?id=57775
New Features at a glance in MDT 8456
Please read the release notes for a full list of new features, but the most important features are:
- Support for Windows 10 v1809
- Support for Windows Server 2019
- Nested task sequence support for LTI scenario
- Modern language pack support
- Support for Configuration Manager version 1810
- IsVM evaluates to False on Parallels VMs
- IsVM = False when VMware VM is configured with EFI boot firmware
- Gather doesn't recognize All-in-One chassis type
- MDT doesn't automatically install BitLocker on Windows Server 2016
- BDEDisablePreProvisioning typo in ZTIGather.xml
Now, back to the upgrade guides!
Upgrading to MDT 8456 Lite Touch (standalone)
Worth mentioning is that there are no changes in the MDT 8456task sequence templates compared to the 8443 release, so if you upgrade from that one, you don't need to create new task sequence. Very nice.
Upgrading to MDT 8456 is quite straight forward, simple follow these steps:
1. Make a complete backup copy of your deployment share(s)
2. Yes, really, make a complete backup copy of your deployment share(s) 🙂
3. Check if there is a pending reboot, use the http://github.com/DeploymentResearch/DRFiles/blob/master/Scripts/Test-PendingReboot.ps1 script.
4. If you're not using Windows ADK 10 v1809 already, uninstall the version you have, and then install Windows ADK 10 v1809. Select the following components:
Imaging and Configuration Designer (ICD)
User State Migration Tool (USMT)
5. Install the WinPE Addon for Windows ADK 10 v1809. Select the following components:
Windows Preinstallation Environment (Windows PE)
6. Reboot the machine (to make sure the wimgapi driver is registered)
7. Install MDT 8456 (automatically uninstalls earlier versions)
8. Using Deployment Workbench, right-click the deployment share you want to upgrade, and select Upgrade Deployment Share.
9. Repeat the previous step if you have more deployment shares.
10. After upgrading the deployment share, using Deployment Workbench, right-click the deployment share and select Update Deployment Share. This will create new boot images.
11. Repeat the previous step if you have more deployment shares.
12. If using WDS for PXE booting MDT boot images, replace the boot images with the new ones.
13. In MDT 8456 the Standard Client Task Sequence and Standard Server Task Sequence templates, as well as their VHD versions, are modified with an extra Apply Patches action in the Postinstall phase to support the updated language packs. This means if you want that support, you need to either create new task sequences, or modify existing sequence with this extra step.
Upgrading to MDT 8456 Zero Touch (integrated with ConfigMgr Current Branch 1810)
For ConfigMgr integration updates, make sure you have upgraded to Windows ADK 10 v1809 on your site server, and also installed the WinPE addon for Windows ADK 10 v1809. You should also update existing boot images to v1809, including the two default boot images (netboot files are typically extracted from these, and you want to have the latest version). Also worth mentioning, there are only minor changes in the MDT task sequence templates for ConfigMgr, but to take advantage of those changes, you either need to do the same modifications to existing task sequences, or create new ones.
1. Install MDT 8456 (automatically uninstalls earlier versions).
2. The ConfigMgr Integration extensions have not been updated from MDT 8450 (other then updated binary signatures), so there is no need to re-run the Configure ConfigMgr Integration wizard.
3. Create a new dummy task sequence using the Create MDT Task Sequence wizard, and select to create a new MDT package during that wizard.
4. There are no changes (other than version number updates in the boot image script), so you don't need to create new MDT boot images.
However, since the MDT package has changed for ConfigMgr, you need to either:
Option #1: Create new task sequences, and select the new MDT 8456 package.
Option #2: Modify the existing task sequence to use the new MDT 8456 package (typically 5 – 7 changes in every task sequence).
Written by Johan Arwidmark.
I used this procedure for updating to the latest mdt…I uninstalled the adk and the adkpe as well and reinstalled both. (after a reboot of course). I added the old deployment share and did an update when I added it…it seemed successful. I recreated my boot media(we use usb booting not wds) and now when I attempt to image a device I get spammed with script errors…I am at a loss on what to do…as it has broken my complete mdt environment.
Make sure to download Windows ADK for Windows 11 21H2 (version 10.1.22000.1). The latest version, Windows ADK for Windows 11 22H2 is not compatible with MDT 8456.
I'm trying to support the imaging for the company as the previous guy finished sometime ago. MDT version installed is 8450 and is integrated into sccm (2010 – adk2004). Capturing into 8450 with the standard TS (from one of your blogs) has always been seamless. Unfortunately with ADK2004 the capture gets an error "can not find script file c:\ltibootstrap.vbs". The ts fails between the sysprep/create wim tasks. Looking at the posts I'm a little wary of upgrading…Have you tested with 8450 with adk2004? Is it compatible to use this version of mdt with adk2004? Have you tested the HF with… Read more »
I haven't done any tests on MDT 8450 for years, but it only supports up to Windows 10 1709, and Windows ADK 10 1709. You should upgrade to MDT 8456 + Hotfix for ADK 2004 and Windows 10 20H1 and higher. Just make sure to make a backup of your deployment share prior to upgrade, and you can always revert if you run into any issues.
Having a nightmare upgrading the deployment share. Where can I find an old version (6.3.8443.1000) of MDT to download and downgrade?
I've upgraded quite a number of environments to MDT 8456 by now. What issues are you seeing? And in regards to an older MDT version, send me a message on LinkedIn, and I can probably help out 🙂 ( http://linkedin.com/in/jarwidmark ) / Johan
Thanks! I'll have to resurrect my LinkedIn account. During the first attempt at upgrading the deployment share in the workbench, I encountered a file name character length error, now I'm getting access to the path is denied.
Yes, please do get that account going, the issue you're having is very likely quite easy to fix.
"Performing the operation "New drive" on target "Name: DS001 Provider: MicrosoftDeploymentToolkit\MDTProvider Root: D:\MDT\DeploymentShare".
Performing the operation "upgrade" on target "deployment share".
Upgrading an existing deployment share
Beginning the upgrade.
Backing up existing configuration.
The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Check this post: https://deploymentresearch.com/windows-8-deployment-the-specified-path-file-name-or-both-are-too-long/
Sorry try this link:
I had a working MDT 8450, but after upgrading to 8456 I get an error when trying to upgrade the deployment share. I have already updated SCCM to 1810 hotfix and ADK to 1809. Here is a picture of the error:
Please reply soon, I can't seem to find much on this.
Sure looks like a plain access denied issue. You can run procmon from sysinternals with a filter on that file/folder to see what's going on. Often issues like this can be caused by antivirus software as well.