Forum Discussion

Greta Pauwels's avatar
Greta Pauwels
Copper Contributor
Apr 18, 2017

MDT for windows 10 version 1703

Can I use the "old" MDT (for version 1607) to deploy Windows 10 version 1703?

 

If not, where can I find the new version of MDT for windows 10 version 1703?

13 Replies

  • David M Heck's avatar
    David M Heck
    Copper Contributor

    ADK Download page: https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit

  • Steffen Nielsen's avatar
    Steffen Nielsen
    Copper Contributor

    Hi Greta,

     

    I assume you mean MDT 8443, which was released in November?
    I have used that MDT, with the ADK 10.1.14393 to create the Windows 10 1703 images we use in our organisation, so the answer would be yes.

     

    The new MDT is not yet released, but I recommend ou follow this blog:
    https://blogs.technet.microsoft.com/msdeployment/

     

    The ADK, however, is released for 1703, and can be found here:

    https://blogs.technet.microsoft.com/ausoemteam/2017/04/06/download-windows-adk-for-windows-10-version-1703/

    • Tony Fleming's avatar
      Tony Fleming
      Copper Contributor

      Agreed, I have also completed capturing and deploying a Win10 x64 1703 reference image using the same configuration but I found that when I deploy it to a physical device (vs. virtual machine) at the beginning of the STATERESTORE Property phase/ZTINextPhase (Component) I hear "All right, you're connected.  Now we'll check for any updates".  I'm assuming this is the network adapter configuration as it is not uniquely identified in the deployment logs.

       

      I would like to disable it but I can't find any documentation indicating its presence.  I didn't know if controlling it might be a feature in ADK 1703.  Has anyone else seen this behavior?

      • Peter McDaniel's avatar
        Peter McDaniel
        Copper Contributor

        It is Cortana. Made me jump the first time it happened (A SurfacePro on which the volume defaults to 100%) It can be disabled by adding this to the Unattend.xml, in Pass 4, Deployment Neutral, under Run SynchronousCommand:

        Reg Add HKLM\Software\Microsoft\Windows\CurrentVersion\OOBE /v DisableVoice /d 1 /t REG_DWORD /f

Resources