MDT VS SCCM

Question

We are running in SCCM Environment, and our team is looking to deploy MDT for a different region. Could we know the difference between MDT and SCCM? What are the advantages and disadvantages of them?

Answer 1

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

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, you can 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".

Please refer to: Microsoft Publishes Best Practices for Windows Deployments

Best regards,
Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I think others have laid out most of it. However If you own Configuration Manager, you should leverage that and avoid MDT. Why duplicate your efforts? You probably have most of your Applications in ConfigMgr, why duplicate those for MDT?

MDT runs as ADMIN, ConfigMgr as SYSTEM. You might find odd behavior if you're used to CM and then move to MDT

ConfigMgr will provide better support, MDT is essentially a dead product. They update the bare minimum to support new windows versions, but no feature enhancements.

Community Hub! ConfigMgr will continue to have more community content that you can borrow and integrate saving you time.

I just see no need to onboard MDT into an environment that already has ConfigMgr, its adding additional complexity where it's not needed.

Answer 3

Basically if you want to manage your devices after you deploy them you need SCCM. MDT is for deployment only.

Answer 4

Hi,

Hope everything goes well. May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

Thanks and regards,
Simon