locked
MDT Vs. SCCM RRS feed

  • Question

  • Hello Guys,

    We have a SCCM Environment and our team is looking to deploy MDT for a different region.

    Can we know the Pros / Cons with MDT over sccm and usage / config info.


    Regards, Prasad

    Wednesday, September 25, 2019 3:50 AM

Answers

  • Hi Prasad,

    Generally speaking, MDT is suitable for small-scale environments, while SCCM is more suitable for large-scale environments.

    1.MDT is free, which is a huge advantage for many smaller business. MDT as a standalone tool is great for tiny environments without a lot of computers to migrate. MDT is also a fine fit for environments that are not connected. MDT is best used for creating "thin" images that just contain OS updates and runtimes. It is Lite Touch Installation (LTI), not fully automated. MDT is primarily used for image computers and storing images, customizing them, etc. 

    2. SCCM's license costs are also much more than those of MDT, as MDT is free.  SCCM on the other hand, is a much more complex tool which allows you to do a lot more than MDT does. Whereas SCCM is best used for creating "thick" images containing line-of-business applications. It can also incorporate WSUS within it, and provide update reporting. It can also provide auditing against what a standard machine should be.

    3. If you are in a very big organization, it's recommended to integrate MDT with SCCM. More specifically, if you have thousands of computers and many different applications to manage it’s a good direction to consider. You should integrate MDT operating system images with Configuration Manager for large-scale operating system deployments to take advantage of enterprise-level management features such as: replication, multicast DPs, bandwidth management, reporting, poor network connections to remote sites, and stronger security through encryption and password protection. The SCCM plus MDT combination is preferred for "zero touch installations" and "user driven installation deployments".

    For more information, please refer to:
    Microsoft Publishes Best Practices for Windows Deployments
    WINDOWS 10 DEPLOYMENT METHODS

    Thanks for your time.

    Best regards,
    Simon Ren

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by SAAD Youssef Wednesday, September 25, 2019 7:23 AM
    • Marked as answer by RealStruggler Wednesday, September 25, 2019 7:34 AM
    Wednesday, September 25, 2019 6:35 AM

All replies

  • Hi Prasad,

    Generally speaking, MDT is suitable for small-scale environments, while SCCM is more suitable for large-scale environments.

    1.MDT is free, which is a huge advantage for many smaller business. MDT as a standalone tool is great for tiny environments without a lot of computers to migrate. MDT is also a fine fit for environments that are not connected. MDT is best used for creating "thin" images that just contain OS updates and runtimes. It is Lite Touch Installation (LTI), not fully automated. MDT is primarily used for image computers and storing images, customizing them, etc. 

    2. SCCM's license costs are also much more than those of MDT, as MDT is free.  SCCM on the other hand, is a much more complex tool which allows you to do a lot more than MDT does. Whereas SCCM is best used for creating "thick" images containing line-of-business applications. It can also incorporate WSUS within it, and provide update reporting. It can also provide auditing against what a standard machine should be.

    3. If you are in a very big organization, it's recommended to integrate MDT with SCCM. More specifically, if you have thousands of computers and many different applications to manage it’s a good direction to consider. You should integrate MDT operating system images with Configuration Manager for large-scale operating system deployments to take advantage of enterprise-level management features such as: replication, multicast DPs, bandwidth management, reporting, poor network connections to remote sites, and stronger security through encryption and password protection. The SCCM plus MDT combination is preferred for "zero touch installations" and "user driven installation deployments".

    For more information, please refer to:
    Microsoft Publishes Best Practices for Windows Deployments
    WINDOWS 10 DEPLOYMENT METHODS

    Thanks for your time.

    Best regards,
    Simon Ren

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by SAAD Youssef Wednesday, September 25, 2019 7:23 AM
    • Marked as answer by RealStruggler Wednesday, September 25, 2019 7:34 AM
    Wednesday, September 25, 2019 6:35 AM
  • Note that many folks, including myself, generally disagree with #3. There is no technical reason this must be done. It can work very well but it does add a lot of overhead, complexity, and an extra learning curve if you are not already familiar with MDT. ConfigMgr OSD stands on its own and is perfectly capable without MDT. Also, the UDI component of MDT is extremely old, borderline unsupported, has known bugs and issues that won't be addressed, and there are better alternatives available.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, September 25, 2019 1:42 PM