none
Any reason to upgrade from MDT 2010 to MDT 2012 or 2013 For Windows 7 deployments? RRS feed

  • Question

  • We are only deploying Windows 7 via MDT and don't expect to deploy Windows 8 or Server 2012 any time soon.

    Since we don't need compatibility with OSes newer than Windows 7, is there any benefit to updating to newer versions of MDT now instead of waiting until we refresh to the next desktop OS years from now?

    Friday, February 21, 2014 4:12 AM

Answers

  • If you find something useful there http://download.microsoft.com/download/B/F/5/BF5DF779-ED74-4BEC-A07E-9EB25694C6BB/Whats%20New%20in%20MDT%202013%20Guide.docx then yes. Otherwise not really.

    Anyway, unless you made lots of customizations in your deployment share(s) the upgrade process is quite simple. And as this release is also correcting few bugs why not upgrading.

    You can always try the upgrade by setting a new temporary MDT 2013 server, copying your deployment share, updating it and see if everything is fine.


    My technet galleries contributions : <a href="http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d"> ConfigMgr driver injector</a> // <a href="http://gallery.technet.microsoft.com/SCCM-Collection-Splitter-e1c82b06"> SCCM Collection splitter</a>

    Friday, February 21, 2014 8:55 AM
  • Hopefully you made your customizations to separate files, or the upgrade will replace them with upgraded stock versions.

    I think applying the images is faster, since 2012/13 uses DISM as opposed to setup. The interface is a little better, and in 2013 you can add multiple apps to bundles with checkboxes, instead of browsing and selecting them one at a time, that's nice.

    You'll need to find win 8 drivers to add to WinPE 5 boot images, but adding DaRT tools is supported now, you dont need to go through a manual process.

    • Marked as answer by MyGposts Monday, February 24, 2014 4:11 PM
    Friday, February 21, 2014 4:53 PM

All replies

  • If you find something useful there http://download.microsoft.com/download/B/F/5/BF5DF779-ED74-4BEC-A07E-9EB25694C6BB/Whats%20New%20in%20MDT%202013%20Guide.docx then yes. Otherwise not really.

    Anyway, unless you made lots of customizations in your deployment share(s) the upgrade process is quite simple. And as this release is also correcting few bugs why not upgrading.

    You can always try the upgrade by setting a new temporary MDT 2013 server, copying your deployment share, updating it and see if everything is fine.


    My technet galleries contributions : <a href="http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d"> ConfigMgr driver injector</a> // <a href="http://gallery.technet.microsoft.com/SCCM-Collection-Splitter-e1c82b06"> SCCM Collection splitter</a>

    Friday, February 21, 2014 8:55 AM
  • Hi,

    check this article. It´s a overview about New Features and issues.


    Kind regards,

    Tim
    MCITP, MCTS, MCSA
    http://directoryadmin.blogspot.com

    This posting is provided 'AS IS' with no warranties or guarantees and confers no rights.

    "If this thread answered your question, please click on "Mark as Answer"

    Friday, February 21, 2014 9:41 AM
  • If you find something useful there http://download.microsoft.com/download/B/F/5/BF5DF779-ED74-4BEC-A07E-9EB25694C6BB/Whats%20New%20in%20MDT%202013%20Guide.docx then yes. Otherwise not really.

    Anyway, unless you made lots of customizations in your deployment share(s) the upgrade process is quite simple. And as this release is also correcting few bugs why not upgrading.

    You can always try the upgrade by setting a new temporary MDT 2013 server, copying your deployment share, updating it and see if everything is fine.


    My technet galleries contributions : <a href="http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d"> ConfigMgr driver injector</a> // <a href="http://gallery.technet.microsoft.com/SCCM-Collection-Splitter-e1c82b06"> SCCM Collection splitter</a>

    What types of customizations from MDT 2010 cause problems in MDT 2013?

    Also, is it true that to get from MDT 2010 to 2013, we would need to first migrate to MDT 2012 and then migrate MDT 2012 to MDT 2013?

    Friday, February 21, 2014 3:21 PM
  • Hopefully you made your customizations to separate files, or the upgrade will replace them with upgraded stock versions.

    I think applying the images is faster, since 2012/13 uses DISM as opposed to setup. The interface is a little better, and in 2013 you can add multiple apps to bundles with checkboxes, instead of browsing and selecting them one at a time, that's nice.

    You'll need to find win 8 drivers to add to WinPE 5 boot images, but adding DaRT tools is supported now, you dont need to go through a manual process.

    • Marked as answer by MyGposts Monday, February 24, 2014 4:11 PM
    Friday, February 21, 2014 4:53 PM
  • Hopefully you made your customizations to separate files, or the upgrade will replace them with upgraded stock versions.

    I think applying the images is faster, since 2012/13 uses DISM as opposed to setup. The interface is a little better, and in 2013 you can add multiple apps to bundles with checkboxes, instead of browsing and selecting them one at a time, that's nice.

    You'll need to find win 8 drivers to add to WinPE 5 boot images, but adding DaRT tools is supported now, you dont need to go through a manual process.

    What specifically is considered a "customization" that will cause a problem in a new version of MDT?

    Will the same image files and task sequences work in 2013 that were captured and created in 2010?

    Friday, February 21, 2014 9:25 PM
  • I was especilly thinking of changing the scripts or the wizard definition files that comes in the script folder of MDT.

    Mickael,
    My technet galleries contributions :
    ConfigMgr driver injector
    SCCM Collection splitter

    Friday, February 21, 2014 9:36 PM