Integrate MDT 2012 with SCCM 2012

In case you missed it, the Deployment Guys recently announced the release of the Microsoft Deployment Toolkit (MDT) 2012 Beta 2. The latest release supports a raft of new features, including User-Driven Installation (UDI) and support for integration with System Center Configuration Manager 2012 RC, which is something that MDT 2012 Beta 1 couldn’t do.

So how does the integration process look?

First, download the latest MDT 2012 build from Connect, and copy across the file with the relevant architecture to the SCCM server (given that it’s SCCM 2012, this will probably be MicrosoftDeploymentToolkit2012_x64.msi).

Launch the installer:

Launch the MDT Installer

Next, accept the EULA:

Accept the EULA

Next, choose to install all MDT components and select the installation path:

Install all MDT components

And install.  The installer will prompt for UAC elevation – you can always bypass this step by launching the installer from an elevated command prompt.

Once complete, go to the Start Menu, Microsoft Deployment Toolkit and select “Configure ConfigMgr Integration”:

Choose to integrate MDT

The MDT integration utility should find the locally-installed Configuration Manager Console, and should auto-populate the correct site code and site server details. If not, just enter them manually:

Choose the correct site details

If you’ve already installed the extensions, you can also use this utility to remove the console extensions and MDT task sequences.

Once complete, verify that the process has finished without error, and you’re done:

Verify successful integration

Next, launch the Configuration Manager console and go the Software Library pane, and verify that you now have the extra options for using MDT to create Boot Images and Task Sequences:

Create MDT Boot Images and Task Sequences

And that’s it! Basically the process is identical to integrating MDT 2010 with Configuration Manager 2007, and given that MDT 2012 Beta 2 also integrates with Configuration Manager 2007, that’s not surprising.

MDT 2012 looks like it’s going to give deployment a real kick, especially in combination with SCCM 2012.  Much more on this to come, but for now, MDT is integrated so we deployment fans can get stuck in :-)

No comments yet to Integrate MDT 2012 with SCCM 2012

  • Iliass

    Hello

    I tested MDT 2012 (in standalone mode) and used the “deploy to VHD client” TS templates which works great!

    Now, I integrated MDT 2012 with ConfigMgr 2012 RC1 and noticed the “Deploy to VHD client” and “Deploy to VHD server” templates are not available in the ConfigMgr console.

    It would be great if we could use those templates in SCCM, do you know if this is due to the combination of MDT 2012 beta2 and SCCM 2012 RC1 or will those templates not be available when integrating MDT 2012 with SCCM 2012.

    Thanks a lot for any pointers on this.

    Kind regards,

    Iliass

  • Can someone explain why you want to integrate MDT 2012 into SCCM? Why not use SCCM own task sequence and deployment method? Is there any advantage using MDT2012 instead?

    • James Bannan

      Basically, MDT gives you a much richer framework for creating OSD task sequences than you can get just using the native task sequences. If the functionality of the native task sequences meets your needs, then there’s no need for MDT. However, I always integrate and use MDT in SCCM as it gives you so many more options and flexibility.

      • Michael Moore

        James, could you elaborate a little on some of the extra options and such this gives you. My organization is currently using MDT2010 and we are currently being to roll out SCCM 2012. I was really excited to learn we were beginning SCCM deployment, but I’ve learned they are wanting to just drop MDT altogether and use SCCM. I’ve been a big proponent of SCCM/MDT integration and have been trying to push for this, but I really can’t give a good argument as to the actual WHY we should do this as opposed to just going SCCM for OSD.

        Thanks

        • James Bannan

          Hi – I always use MDT-integrated task sequences for OSD, principally because MDT + SCCM working together produce a far superior outcome than either product working on its own. The task sequence engine in SCCM is effectively a stripped-down version of the one used in MDT, and on the other side of the equation, SCCM provides a management framework which MDT doesn’t have. So using them together gives you all the power of MDT-driven OSD plus SCCM management and backend infrastructure. Also, if you have familiarity with MDT then it makes total sense to keep using it in an SCCM environment – the skills are just as relevant. The real question to be asking is, “Why wouldn’t you use MDT + SCCM?”. :-)

  • Has anyone successfully used the mdt database with SCCM 2012 OS Deployment? I’m unable to get the task sequences to query the database. Worked fine in sccm 2007/mdt 2010.
    Joe

  • [...] Integrate MDT 2010 Update 1 (or newer) with SCCM 2007 SP2 (R2+ preferable). [...]

  • Bjørn Henrik Formo

    You write that you run the installer “on the SCCM server” – but that doesn’t explain what you really need to explain. There are specific “Site systems” in SCCM2012 – which Site system is the MDT installation supposed to run on?

    • James Bannan

      Hi Bjorn – the integration between SCCM and MDT happens via the SCCM console, so really you need to install MDT on each workstation and site system which has the SCCM Console installed. You’re correct – I should have been more specific.

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>