Microsoft Deployment Toolkit (8443) now available

[Arthur]

Source: Microsoft / Download (Direct Links: x64, x86)

 

The Microsoft Deployment Toolkit (MDT), build 8443, is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607, available on the Microsoft Hardware Dev Center (adksetup.exe file version 10.1.14393.0).

 

You may notice that we are not tagging this release with a year or update version. To better align with the current branches of Windows 10 and Configuration Manager, and to simplify the branding and release process, we are now just referring to it as the “Microsoft Deployment Toolkit”, using the build number to distinguish each release. This is not necessarily a “current branch” of MDT; we are committed to updating MDT as needed with revisions to Windows, the Windows ADK, and Configuration Manager.

 

Here is a summary of the significant changes in this build of MDT:

 

Supported configuration updates

 

• Windows ADK for Windows 10, version 1607
  
• Windows 10, version 1607
  
• Windows Server 2016
  
• Configuration Manager, version 1606
  

Quality updates

 

• Deployment Wizard scaling on high DPI devices
  
• Johan’s “uber bug” for computer replace scenario
  
• Multiple fixes for the Windows 10 in-place upgrade scenario
  
• Several fixes to Configure ADDS step
  
• Removed imagex/ocsetup dependencies, rely solely on DISM
  
• Includes the latest Configuration Manager task sequence binaries (version 1606)
  

[sted]

does that mean it cant deploy windows 7 or 8.1?

[garethEds]

does that mean it cant deploy windows 7 or 8.1?

 

I've just asked the same question to the guys over at Deployment Research on Facebook. My MDT 2013 works great with W10(1607) and W7 so I don't think I shall be changing it anytime soon.

 

Gareth

[garethEds]

So I've had a reply to the question I asked on Facebook. Here it is:

 

'Yes, Gareth it fixes a lot of bugs (adds the Johan Bug Fix) and some new features (i.e., additional task sequence binaries). Remember TEST first and then BLAME someone else!!!'

 

That came from the Deployment Research guys on Facebook.

[edge9001]

I'm VERY new to MDT. I have managed to stumble through creating a W7 deployment with custom OEM information, applications, windows activation and auto joining a domain. I based this deployment off of a dell branded W7Pro install disk.

 

I have tried the same thing with W10, but i get an error location does not contain an identifiable operating system. With W7 I just imported a full set of source file from the disk. I know I am missing something. but what?

 

my steps so far are simple.

open deployment workbench, right click on deployment shares and select new deployment share. new I go to The OS section of said deployment share. and I right click and select import OS. in this wizard I point the to the installation USB(or mounted ISO or even the DELL W10 disk) and I immediately get an error of does not contain an identifiable operating system.

[Arthur]

I immediately get an error of does not contain an identifiable operating system.

That sounds like the disc you are using contains an install.esd image (in the 'sources' subfolder) rather than an install.wim. It's the latter that MDT needs.

 

Do you have a Microsoft volume licensing agreement? If so, you can download a Windows 10 ISO that will work with MDT from the VLSC website.

[edge9001]

No. unfortunatly our company does not have a VLA