Aracılığıyla paylaş

What’s Changed in MDT 8450

  • Makale

Back in December, a new build of MDT was released.  Continuing the pattern established with the release before it (8443), it’s identified only by its build number, hence it’s called MDT 8450.  As Aaron detailed in the announcement blog at https://blogs.technet.microsoft.com/msdeployment/2017/12/21/mdt-8450-now-available/, this release is primarily for compatibility with the latest ADK, Windows 10, and ConfigMgr releases, and includes fixes for a variety of bugs (with the full list included).

Here’s a quick rundown of every change made to the MDT scripts and templates for those that are curious:

  • Templates:
    • SCCM_Client.xml.  Changed the UEFI recovery partition size from 300MB to 499MB to make sure it’s big enough (same as what MDT was already using for Lite Touch).
    • SCCM_Server.xml.  Changed the UEFI recovery partition size from 300MB to 499MB to make sure it’s big enough (same as what MDT was already using for Lite Touch).
  • Scripts:
    • DeployWiz_ProductKeyVista.vbs.  Fixed logic that caused an “invalid deployment type” error.
    • LiteTouch.wsf.  Fixed a variety of logic related to LTI Windows 10 upgrade task sequences (which also fixed an issue related to autologon after a reboot prior to the upgrade).
    • LTIApply.wsf.  Changed the BCDBOOT logic to always run it the same way for UEFI devices, regardless of the OS version, to address some boot-loop issues on bare metal UEFI deployments on some devices.
    • LTICleanup.wsf.  Inconsequential changes (line alignment).
    • ServerManager.xml.  Fixed component names that prevented the installation of Windows Media and IIS Management Console features on Windows Server 2016.
    • SetupComplete.cmd.  Fixed logic related to the changes in LiteTouch.wsf for Windows 10 upgrade task sequences.
    • SetupRollback.cmd.  Ditto.
    • ZTIBde.wsf.  Changed the BitLocker pre-provisioning logic to not try to do anything with the TPM while in Windows PE, to avoid putting the TPM into a reduced functionality state.
    • ZTIGather.wsf.  Added some new chassis types (30, 31, 32 for laptops; 35 and 36 for desktops; 28 for servers).
    • ZTIMoveStateStore.wsf.  Fixed the logic that moved the state store so that it didn’t use a hard-coded \StateStore folder location.
    • ZTIOSRole.wsf.  Fixed the logic so that it works for multiple calls to get the source location.
    • ZTIUtility.vbs.  Fixed logic to ignore disabled “Install Operating System” steps (caused problems with some types of task sequences).

Additionally, all the standalone task sequencer binaries (used to run LTI task sequences) were updated to the latest code from ConfigMgr.

So, it’s a very minor update overall.  If you have existing task sequences created with MDT 8443, you shouldn’t need to recreate them, although if you have ConfigMgr task sequences you might want to edit the “Format and Partition” UEFI steps to specify 499MB instead of 300MB for the recovery partition size.

And as always, back up your deployment share before upgrading (especially if you’ve made any script edits), reintegrate your changes if needed, and make sure you update your boot images (including on WDS, USB boot media, boot ISOs, etc.) as mismatched versions will cause all sorts of problems.

Comments

  • Anonymous
    March 29, 2018
    Each time a new version is released there is a spike in comments on the TechNet forums from people asking how to upgrade or why their upgrade didn't work (maybe they are entirely new to MDT and inherited an existing system or it is their first MDT upgrade). So it might be an idea to publish an upgrade document and then link to it in each new blog post relating to a new release? Also, a functionality suggestion. The Roles and Features task sequence is brilliant, but now Microsoft is fully focused on Windows 10. When the next big update is released could it include the same layout as the Roles and Features task sequence but address the Apps that come with Windows 10? Enterprises don't want apps Candy Crush but it is there when users log in. Using DISM to mount and then PowerShell to clean the DVD source is already tiresome after just the fifth iteration of the operating system. An MDT task sequence that can do the same would make everybody happy.