[mdt] MDT 2013 Update 1 Now Available

[Arthur]

At last!

 

Source: Microsoft / Download (x64, x86)

 

The Microsoft Deployment Toolkit (MDT) 2013 Update 1 is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, available on the Microsoft Hardware Dev Center. (Scroll to the bottom of the page to the section, "Customize, assess, and deploy Windows on your hardware." The page also includes other Windows kits; remember for deployment you only need the Windows ADK for Windows 10).

 

Significant changes in MDT 2013 Update 1:

 

• Support for the Windows Assessment and Deployment Kit (ADK) for Windows 10
  
• Support for deployment and upgrade of Windows 10
  
• Support for integration with System Center 2012 R2 Configuration Manager SP1 with the Windows 10 ADK (see this post on the Configuration Manager Team blog for more information on using the Windows 10 ADK with Configuration Manager)
  

Here is a more detailed list of some specific changes in this release:

 

• Support for new Enterprise LTSB and Education editions of Windows 10
  
• Support for modern app (.appx) dependencies and bundles
  
• Improved support for split image files (.swm)
  
• Switched to using DISM for imaging processes (instead of deprecated ImageX)
  
• Deployment Workbench revisions for deprecated content
  
• Enhanced accessibility within the Deployment Workbench
  
• Revised lists of time zones, regions and languages in the Deployment Wizard
  
• Removed Start menu shortcut for “Remove PXE Filter”
  
• Several MVP recommended fixes for Windows Updates, password handling, and PowerShell cmdlets
  
• Added missing OOBE settings to Unattend.xml
  
• Unattend.xml default screen resolution changed to allow for automatic scaling
  
• Updated task sequence binaries from System Center 2012 R2 Configuration Manager SP1
  
• New GetMajorMinorVersion function for integer comparison of Windows version numbers
  

We are still working to update the MDT documentation on TechNet, so in the short-term will use this blog to share any additional necessary information regarding this release.

Edited August 18, 2015 by Arthur

[garethEds]

Just posted in the Windows 10 forum as well - there are apparently some issues if installing in certain scenarios. Have a read here for information and workarounds:

 

 

Deployment Research > Research

 

 

Gareth

[Arthur]

there are apparently some issues

Quite a lot of issues. There are another five that aren't currently mentioned on Johan's blog.

 

• UberBug 01 – MDAC and the Fast Machine
  
• UberBug 02 – English keyboards only please!
  
• UberBug 03 – Less Logging is not better
  
• UberBug 04 – Litetouch Success may mean Failure
  
• UberBug 05 – Batch scripting is dead
  
• UberBug 06 – Having two recovery partitions is more secure
  
• Gotcha – Upgrading a Deployment Share
  
• Gotcha – No progress is good progress
  

Edited August 19, 2015 by Arthur

[Arthur]

MDT 2013 Update 1 Release Notes and Known Issues « Microsoft Deployment Toolkit Team Blog

 

This post is to serve as the release notes and known issues list for the current release of MDT 2013 Update 1 (v6.3.8290).

 

The list of known issues below provides a number of workarounds that are currently available to help unblock affected customers. We will revise the list as needed. Given the number of issues with this build we will release a newer build of MDT 2013 Update 1 in the next several weeks to address as many of these issues as we can. Watch this blog for more information.

[Gatt]

Just encountered this issue with Win10..

 

Deployment fails as soon as its starts applying the Win10 Image with

 

[color=#2A2A2A][font=Segoe UI]Failure (5624): 87: Run DISM: /Apply-Image /Image-File:"\\ts-wds\reminst\images\windows10\install.wim" /index:1 /ApplyDir:W: /SWMFile "\\ts-wds\reminst\images\windows10\res.rwm"[/font][/color]
[color=#2A2A2A][font=Segoe UI]Litetouch deployment failed, Return Code = -2147467259 0x80004005[/font][/color]

 

 

 

Fix / Workaround is to edit your LTIApply.wsf file: https://connect.microsoft.com/ConfigurationManagervnext/Feedback/Details/1692057

 

Image appears to be applying now, so hopefully the TS will now complete...

[Arthur]

MDT 2013 Update 1 re-released (build 8298)

 

Download (x64, x86)

 

The following issues are fixed in build 8298.

 

• Multiple drive partitioning issues are addressed by significant revisions to the Format and Partition Disk step (see release note below), including:
  
  • Upgrading to MDT 2013 Update 1 does not work for UEFI systems
    
  • An extra unneeded partition is created on both UEFI and BIOS systems
    
  • You cannot specify a custom partition layout containing a "Recovery"-type partition needed for UEFI systems
    
  • LTIApply error, "There is not enough space on the disk"
    
  • WINRE_DRIVE_SIZE from ZTIDiskpart.wsf is Too Small
    

   

  [*]Multiple issues related to XML processing:

  • Application bundles returning error 87
    
  • Selecting a keyboard locale in the Deployment Wizard
    
  • Deployments failing due to Unattend.xml errors
    
  • ZTIPatches returning error "Object required (424)"
    
  • Cleanup after image capture doesn't remove LTIBootstrap entry
    

   

  [*]Several issues with the Windows 10 in-place upgrade task sequence including:

  • The upgrade process ends with warnings "Unable to create WebService class"
    
  • The upgrade task sequence is available from Windows PE
    
  • After upgrade a System_License_Violation blue screen appears
    

   

  [*]Applications that use a command file start using System32 as the working directory

  [*]Spanned images cannot be applied

Edited September 15, 2015 by Arthur

[garethEds]

Still nervous about installing it. We're not even considering 10 until at least next year. Windows 7 does everything we need on the hardware we have so I see it becoming our 'new XP' :-)

 

Gareth