Partilhar via

MDT 2013 Update 1 Preview: What’s Changed

  • Artigo

In case you missed it at https://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 https://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

  • Anonymous
    March 05, 2015
    The comment has been removed
  • Anonymous
    March 23, 2015
    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
  • Anonymous
    March 27, 2015
    Please reference the MDT 2013 Release Notes as a starting point.
    Important! MDT 2013 Update 1 Preview
  • Anonymous
    April 02, 2015
    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.
  • Anonymous
    June 08, 2015
    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
  • Anonymous
    June 09, 2015
    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.
  • Anonymous
    June 29, 2015
    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!
  • Anonymous
    August 06, 2015
    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
  • Anonymous
    August 06, 2015
    That is something they are presently looking at, assuming they can work out the technical challenges with doing so.
  • Anonymous
    August 13, 2015
    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