MDT and Windows 10…coming soon!


I'm dusting off this blog for a quick announcement: we are working on an update to MDT to support Windows 10 and the new Windows 10 ADK (and perhaps a few other revisions as well…). A preview will be available soon, expected in the next two months. Watch this space for more information.

— Aaron Czechowski, Senior Program Manager

This posting is provided "AS IS" with no warranties and confers no rights.


Comments (41)
  1. Anonymous says:

    Awesome Can’t wait !

  2. Anonymous says:

    Hey Aaron, Can you confirm if this would be a new version (like "MDT 2015") or an update to MDT 2013? Would help to plan if a new server will be required for Windows 10 build deployment for our customers.

    Thanks.

  3. Anonymous says:

    @Haecki – we are tracking a design change request for that work but currently don’t have it planned as an immediate change.
    @dgt845 – often times that will work, but it is very dependent upon the hardware vendor and their drivers.

  4. Anonymous says:

    Hi Amil – this will be an update to MDT 2013, in-place upgrade will be fully supported.

  5. Anonymous says:

    Good news !

  6. Anonymous says:

    Can’t Wait!

  7. Anonymous says:

    @Tobias & Tristan: please make your feedback actionable and file it on Connect:

    https://connect.microsoft.com/ConfigurationManagervnext/MicrosoftDeploymentToolkit

  8. Anonymous says:

    Can’t wait!

  9. Anonymous says:

    Super! !

  10. Anonymous says:

    @Alphaeus – great comments, thanks for the feedback. Happy to discuss things here, but to make it actionable please file it on Connect:

    https://connect.microsoft.com/ConfigurationManagervnext/MicrosoftDeploymentToolkit
    p.s. this is also where you’ll find the preview posted in the coming months….

    @Brett/David – we’ve definitely heard that feedback and would love to convert MDT to pure Windows PowerShell, it’s likely the right thing to do at this time. However, it would require the boot image to be expanded to include the .NET and PowerShell optional
    components by default (which we’re considering anyway, but does have an impact). It’s also a massive engineering effort as we’d basically have to rewrite every script! So we’d rather prioritize bug fixes and new features over something of this sort at this
    time.

  11. Anonymous says:

    Bring it on!

  12. Anonymous says:

    great news!!!

  13. Anonymous says:

    Sounds good! Looking forward to the get my hands on the version.

  14. Anonymous says:

    I have a question about Winpe drivers. We typically use IBM Servers and it is very difficult to find Winpe 5.0 drivers. Can I use WinPE 4.0 or Server 2012 drivers instead in MDT2013? I am only interested in Storage and NIC drivers.

    Thanks,
    Deepak

  15. Anonymous says:

    The link to Connect (https://connect.microsoft.com/ConfigurationManagervnext/MicrosoftDeploymentToolkit) returns ‘Page not found’. Has the site changed?

  16. Trey says:

    Awesome!

  17. Brett Bartrum says:

    Will it be rewritten in PowerShell? 😛

  18. shakeel says:

    Superb. Long wait ;(

  19. M.Praveen says:

    I am waiting

  20. OSD.Tips says:

    Awesome – let’s go!

  21. David Bloom says:

    +1 to the PowerShell rewrite comment.

  22. Alphaeus Mote says:

    Could the application bundling be a little more intuitive? For instance, creating a single bundle with multiple steps with the use of a + sign and then setting all the normal information?

    Also maybe adding step numbers on the side of the task sequence so when looking at the reporting console, you can jump to the appropriate step?

  23. Tobias Wink says:

    Great, I hope it will be possible to make a full Copy from existing TS Mike SCCM?

  24. Tristan Ferron says:

    Hi,

    Some "tips" than lots of peoples add again and again at each upgrade could be included ?

    Great job, thanks.

    DeployWiz_Initialization.vbs __________________________________________________________
    read one more time cs.ini if "Priority=TaskSequenceID" is used in cs.ini
    99 Dim sCmd
    Set Oshell = createObject("Wscript.shell")
    202 sCmd = "wscript.exe """ & oUtility.ScriptDir & "ZTIGather.wsf""" ‘
    oItem = oSHell.Run(sCmd, , true)

    ZTIWindowsUpdate.wsf_____________________________________________________________
    WSUS issue
    https://keithga.wordpress.com/2013/09/12/ztiwindowsupdate-wsf-errors/
    403 " result(" & UpdateResult.GetProgress.GetUpdateResult(item).ResultCode & ") : " & UpdatesToDownload.Item(item).Title, MSIT_LogType

  25. Haecki says:

    Can’t wait 🙂

    Hopefully it will include improvements like "use dism instead of imageX" for capture the image.(http://deploymentbunny.com/2014/05/19/nice-to-know-switch-from-imagex-to-dism-in-mdt)

    and lots of other stuff from the Deployment-Gurus "Mikael Nyström and Johan Arwidmark !!!

    Would like to have the version info of a driver inside a "boot.wim" (SCCM) – not only the name.

  26. Brian Cerveny says:

    Excellent.. I’ll check back every day until it’s released.. lol

  27. Tim Nielsen says:

    So glad to see an in place update! Keep up the good work guys! I mean it!

  28. Anonymous says:

    Recent Releases and Announcements

    · An on-demand hotfix update package is available for

  29. DA says:

    Any chance you can build in a way around the domain legal disclaimer after the deployment joins the domain?

  30. Amnon Feiner says:

    The Super / Duper / Uber deployment tool! Can’t wait for the next boot from Via Monstra

  31. Buy Tough says:

    Check out our website for new and refurbished toughbooks and toughpads!
    http://www.mooringtech.com/

  32. New name? says:

    Whats the name of the new MDT? MDT 2015? and when is the release date?

  33. Paul Dredge says:

    Do we have any updates on when this might be released. Looking at deploying Windows 10 this summer and was hoping it would be available in time?

  34. Steve says:

    Aaron with Windows 10 coming out in Two days it seems that ZTI still isn’t supported for Windows 10. When can we expect to see the full release of MDT to support ZTI with SCCM 2012 R2 SP1?

  35. Terry Mc says:

    Not knowing the release date is starting to worry me.

  36. Jon says:

    Installed MDT 2013 on a recently upgraded Win10 PC and installed the Win10 ADK. The Workbench still wants the 8.1 ADK. Let’s go, MSFT!

  37. Brian says:

    Any update on this site besides Feb. 2015?

  38. mickey1529 says:

    When windows 10 boots it says we have encountered a error, we will gather data and reboot for you, then it reboots, it does not say the error but reboots the second time on its own, and takes a while. I have a HPg6 6gb of ram and had windows 7 home premium,
    before the w 10 install. My other laptop does not show the error message

  39. Terry Mc says:

    Seems like they could at least post an update of progress or expected release.

  40. Gert Goos says:

    When will the new version of mdt (2015) be released ?

Comments are closed.

Skip to main content