Shulou(Shulou.com)06/02 Report--

Summary of major changes in MDT build 8456.

Supported configuration updates

Windows ADK for Windows 10, version 1809

Windows 10, version 1809

Configuration Manager, version 1810

Major changes

The following list is a summary of the major changes in this release:

Support for nested task sequences in LTI scenarios

Modern language pack support

Support for Configuration Manager version 1810

IsVM is evaluated as False on Parallels VM

When VMware VM configures EFI boot firmware, IsVM = False

Gather does not recognize the All-in-One chassis type

MDT will not automatically install BitLocker on Windows Server 2016

Spelling mistakes in BDEDisablePreProvisioning ZTIGather.xml

Supported platform

The MDT version is no longer marked as year or newer. To better align with the current branches of Windows 10 and Configuration Manager, and to simplify the branding and release process, it is now just Microsoft Deployment Toolkit. The build number is used to distinguish each version. For example, the latest version available for download is 8456.

Unlike Configuration Manager with scheduled release plans, MDT is released only as needed to support the new version of Windows 10 Magi Windows ADK or the current branch of Configuration Manager. If necessary, this article will document any known problems with these components.

The following operating system versions are supported with MDT deployment:

Windows 10, version 1809

Windows 10, version 1803

Windows 10, version 1709

Other supported Windows 10 versions

Windows 8.1

Windows 7

Windows Server 2019

Windows Server 2016

Windows Server 2012 R2

Windows Server 2012

Windows Server 2008 R2

precondition

MDT requires the following components, which are included in Windows:

Microsoft .NET Framework 4.0

Windows PowerShell v3.0

MDT requires the latest Windows ADK for Windows 10. MDT also requires Windows ADK's Windows PE plug-in.

Be careful

Windows recommends that you use a Windows ADK that matches the version of Windows you are deploying. For example, when deploying Windows 10 version 1809, use Windows ADK for Windows 10 version 1809.

When integrating MDT with Configuration Manager for ZTI and UDI scenarios, use the latest version of the current branch of Configuration Manager.

Upgrade MDT

The MDT installation process removes all MDT instances installed on the same computer. Existing deployment shares, distribution points, and databases are retained during this process. They must be upgraded after the installation is complete.

The current version of MDT supports upgrading from the following versions of MDT:

MDT build 8450

Note: before attempting to upgrade, create a backup of the existing MDT infrastructure.

LTI

After installing MDT, upgrade the existing deployment share by running the Open Deployment Share wizard from the Deployment Shares node in Deployment Workbench. Specify the path to the existing deployment shared directory, and then select the upgrade check box. This process also upgrades existing network deployment shares and media deployment shares, so they should be accessible. Do not use the active deployment for upgrading, as the files you are using may cause upgrade problems.

ZTI

During the installation of MDT, the existing MDT task sequence that exists in Configuration Manager is not modified. They should continue to work without any problems. There is no mechanism for upgrading these task sequences. If you want to use any new MDT features, create a new sequence of MDT integration tasks in Configuration Manager.

After the upgrade process is complete:

Run Configure ConfigMgr Integration Wizard after the upgrade. It registers the new component and installs the updated ZTI task sequence template.

Create a new Microsoft Deployment Toolkit Files package for any new ZTI task sequence that you create. You can use existing MDT Files packages to upgrade any sequence of ZTI tasks that you created before. Create a new MDT Files package for the new ZTI task sequence.

Known issues Modern language Pack support

Starting with Windows 10 version 1809, the language Interface Pack (LIP) is available as a Local experience Pack (LXP). LXP is an AppX bundle. When specified in the unattend.xml file, they are not automatically selected and deployment fails. Do not set LXP as the default. The user should select the applied LXP from the Windows settings.

Welcome to the official account of Wechat: Xiao Wen study Society.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.