MDT 2013 Update 1 Preview: What’s Changed


In case you missed it at http://blogs.technet.com/b/msdeployment/archive/2015/03/02/microsoft-deployment-toolkit-2013-update-1-preview-now-available.aspx, the new preview of MDT 2013 Update 1 is now available for download from the Connect website.  This new release works with the new ADK preview for Windows 10, which is available on the download center at http://www.microsoft.com/en-us/download/details.aspx?id=45522.

While this new release adds support for Windows 10 deployment, it also supports deploying Windows 7, Windows 8, and Windows 8.1 (and their server equivalents).  But at this point, there’s no support for ConfigMgr – that comes later.

So what’s changed in this new release?  Let’s go through it exhaustively by looking at the individual files:

 

  • Credentials_ENU.xml.  Fixed an accessibility issue in the pane.
  • DeployWiz_Definition_ENU.xml.  Fixed the condition on the BitLocker pane so that it displays for all supported OSes, including Windows 10.
  • DeployWiz_Initialization.vbs.  Fixed OS version logic to handle Windows 10.
  • DeployWiz_Roles.vbs.  Fixed OS version logic to handle Windows 10.
  • LiteTouch.wsf.  Updated to handle the new task sequence engine from ConfigMgr 2012 R2.
  • LTIApply.wsf.  Fixed OS version logic to handle Windows 10.  Added logic to handle split WIM files (SWMs).
  • LTICleanup.wsf.  Fixed OS version logic to handle Windows 10.
  • ServerManager.xml.  Added Windows 10 (client) features to the list.
  • Summary_Definition_ENU.xml.  Fixed accessibility issues in the pane.
  • WelcomeWiz_Choice.xml.  Fixed an accessibility issue in the pane.
  • WelcomeWiz_Initialize.xml.  Fixed an accessibility issue in the pane.
  • Wizard.hta.  Fixed an accessibility issue in the pane.
  • ZTIApplyGPOPack.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTIAppXmlGen.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTIBde.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTIDisableBDEProtectors.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTIDiskpart.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTIDiskUtility.vbs.  Fixed OS version logic to handle Windows 10.
  • ZTIGather.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTIOSRole.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTISupportedPlatforms.xml.  Added entries for Windows 10.
  • ZTIUserState.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTIUtility.vbs.  Added new function and properties to handle modified OS version logic.
  • ZTIValidate.wsf.  Fixed OS version logic to handle Windows 10.
  • ZTIWindowsUpdate.wsf.  Modified logic to only set detailed Windows Update Agent logging registry entries when debugging.
  • ZTIWinRE.wsf.  Fixed OS version logic to handle Windows 10.

So to summarize that, here are the changes:

  • Fixed the OS version logic to handle Windows 10 in all scripts.
  • Fixed accessibility issues in all wizards.
  • Added support for applying a split WIM.
  • Updated the task sequence engine from an older ConfigMgr 2007-based version to the latest ConfigMgr 2012 R2-based version.
  • Removed undesired Windows Update Agent (WUA) logging entries that could cause WUA to write excessive logging information.
  • Added new Windows 10 features to the “role and feature” list.

Other changes in Workbench:

  • Removed the “Getting Started” node, as documentation like this can be found on the web.
  • Removed the obsolete “Components” node.
  • Modified the Windows PE template in LiteTouchPE.xml to add new task sequence engine DLLs.

And in the task sequence templates:

  • Sysprep and Capture.  Removed the condition from the “Apply Windows PE (BCD)” step so that it always runs (since all supported OS versions need this).
  • Standard Server Task Sequence.  Removed the condition from the “Apply Windows PE (BCD)” step so that it always runs (since all supported OS versions need this).

Given the extent of the changes, it should be a fairly safe and minor upgrade from MDT 2013, but of course do your own testing first, make a backup, and don’t do this in production until the MDT 2013 Update 1 release later this year.  If you’ve made any changes to any of the MDT scripts, be sure to back those changes up so that you can compare your changes to the new scripts and reintegrate those changes if needed.

Comments (11)
  1. JJ says:

    Thanks Michael! Any idea if a fix to ztisetbackground.wsf in MDT that handles showing the deployment progress background is include or in the works? As I'm sure you know it stops working after the "Windows Setup" phase due to hoe Windows 8.1 and Windows
    10 handle the post-image OOBE. I imagine it has to be possible if the task sequence progress dialog can still be seen throughout the entire process.

  2. JoeZeppy412 says:

    Hi,

    Any chance of this bug getting fixed? More people are considering going to UEFI with Wiondows 10, this might becmoe a bigger deal...

    https://social.technet.microsoft.com/Forums/en-US/22cb4d44-4215-483e-8bdc-b13d9d27725b/what-partition-does-mdt-2012-place-winre-on?forum=mdt

    • It appears that MDT has a bug in ZTIWinRE.wsf
    MDT will create the proper partition configuration on uEFI machines.

    *however* MDT fails to copy the WinRE image to the Recovery partition, instead copying it to the System partition for uEFI scenarios only (BIOS is fine).
    I could fix, but it's lower priority for me. So another day.
    ________________________________________
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  3. Anonymous says:

    Please reference the MDT 2013 Release Notes as a starting point.
    Important! MDT 2013 Update 1 Preview

  4. JJ says:

    Regarding my comment above, we figured out a way to extend ztisetbackground.wsf to work with Windows 8.1 and Windows 10 builds from beginning to end. Happy to share if anyone is interested. I can be reached at jim@onjankowski.com.

  5. RobC says:

    I am just checking in to see if you are going to put support for the Server 2008/Vista OS'es back into the MDT 2013 Update 1. The OS Life Cycle is still supported and we still use if for Legacy 32-Bit Applications that do not support running on a 64-Bit
    OS. I can definitely see removing the Server 2003/XP OS'es when going from MDT 2012 to MDT 2013, but I think you pulled the plug on the Server 2008/Vista OS to soon.
    Thanks,
    Rob

  6. Mykel says:

    Will the new version have a new name? What is release date of mdt for win10? In the past it was the same day as he new os it supported.

  7. Merging MTN''s WIMBoot blog w/ MDT 2013 U1 Preview says:

    Thanks Michael, great work that we have come to expect from you over the years. I am trying to merge the guidance you provided in your April 2014 post re: WIMBoot and this updated build of MDT 2013 U1 Preview using a custom W10 image. Wish me luck!

  8. Mike, do you know if the MDT team will be updating ZTIDiskPart to accommodate the modified partition layout recommended in?:

    http://video.ch9.ms/sessions/winhec/2015/files/WDI201%20-%20Windows%2010%20for%20PCs%20and%202%20in%201s%20Manufacturing%20End-to-End%20Overview.pptx

  9. That is something they are presently looking at, assuming they can work out the technical challenges with doing so.

  10. Shaun Miller says:

    With a lot of help from Jim Jankowski who comment earlier. I have put together a full solution for deployment progress branding on Technet Gallery. This works with Windows 7, 8 and 10 form start to finish.

    https://gallery.technet.microsoft.com/SCCMMDT-OSD-Status-175c90fe

    Hope this helps,
    Shaun

  11. aw says:

    hai, I just want to tell you that I am just very new to blogs and seriously loved this website. More than likely I’m planning to bookmark your blog post .
    You amazingly come with really good posts. Thanks a lot for sharing your blog Microsoft.

    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Aceh
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Bali
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Balikpapan
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Bandung
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Banjarmasin
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Banten
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Batam
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Bekasi
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Bengkulu
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Bogor
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Bontang
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Cianjur
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Cikarang
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Cilegon
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Cirebon
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Denpasar
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Jakarta
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Jambi
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Jember
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Karawang
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Kendal
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Kudus
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Kupang
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Lampung
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Madiun
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Makasar
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Malang
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Maluku
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Manado
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Medan
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20NTT
    http://www.lokerjobindo.com/search/label/Loker%20Daerah%20Padang

Comments are closed.

Skip to main content