Exchange Management Tools 2007 – add as an application in SCCM 2012

Adding Exchange Management Tools 2007 as an application in SCCM 2012 is trickier than it should be, mainly because the installation parameters aren’t obvious from the installer itself. Here’s the working configuration.

Choosing x86 or x64

Decide whether you need the 32-bit console, the 64-bit console, or both. The x64 console installation files are found on the standard Exchange 2007 installation media; the x86 console files are a separate download available from Microsoft’s archive/download pages.

Setting up the application

Copy your chosen installation media to your SCCM source location. When creating the application in the console, use the MSI detection wizard and point it at the MSI in the root of the installation media:

exchangeserver.msi

You can use this same MSI as the application’s Product Code for detection purposes.

Install and uninstall commands

Rather than letting SCCM run the MSI directly, use these specific command lines, which install just the Management Tools role: Installation program:

setup.com /mode:install /role:MT

Uninstall program:

setup.com /mode:uninstall /role:MT

Deploying

Once configured with these parameters, distribute the content to your DPs and deploy as you would any other application. As with any application affecting Exchange tooling, test on a small pilot group before deploying broadly — console version mismatches against your Exchange server version can cause subtle management issues.

Worth Knowing Before You Build This Today (2026)

Both products referenced in this guide are long past end of support: Exchange Server 2007 reached end of support in April 2017, and System Center Configuration Manager 2012 (the specific version this post targets, distinct from the current Configuration Manager/MECM releases) reached end of support in July 2022. Neither receives security updates any longer. This guide remains accurate as a historical reference for anyone still maintaining a legacy environment on these exact versions, but a new deployment on current infrastructure should be targeting a supported Exchange and ConfigMgr version instead.

Resources

• Exchange
• guide
• MSI