Deploy Applications Using Microsoft Configuration Manager

Learn how to create, distribute, and deploy a Windows Installer (.msi) application to a target device collection using Microsoft Configuration Manager (MECM).

August 13, 2026 By Michael Limberg

This guide demonstrates how to create, distribute, and deploy a Windows Installer (.msi) application using Microsoft Configuration Manager (MECM). Completing this task ensures your software packages are properly formatted, cached on distribution points, and targeted securely to your managed devices.

This guide is intended for IT administrators and system engineers who manage software lifecycles for organizational endpoints. Use these steps when onboarding a new application into your MECM environment for broad or targeted deployment.

Create the Application

Step #1: In the Microsoft Configuration Manager console, navigate to the Software Library workspace. — In the Microsoft Configuration Manager console, navigate to the **Software Library** workspace.

Step #2: Expand Application Management and click on Applications. — Expand **Application Management** and click on **Applications**.

Step #3: Right-click on Applications and select Create Application to open the wizard. — Right-click on **Applications** and select **Create Application** to open the wizard.

Step #4: Click Browse... to locate your Windows Installer (.msi) file. — Click **Browse...** to locate your Windows Installer (.msi) file.

Step #6: Double-click on the target MSI file (e.g., 7z2601-x64.msi) to load it. — Double-click on the target MSI file (e.g., `7z2601-x64.msi`) to load it.

Step #7: Click Next to confirm the automatically detected application information. — Click **Next** to confirm the automatically detected application information.

If your MSI file originates from an unverified publisher, Configuration Manager will prompt you with a security warning before proceeding.

Step #8: Click Yes to acknowledge the unverified publisher warning and proceed. — Click **Yes** to acknowledge the unverified publisher warning and proceed.

Step #9: Review the import success message and click Next. — Review the import success message and click **Next**.

Step #10: On the General Information page, verify the application metadata and click Next. — On the General Information page, verify the application metadata and click **Next**.

Step #11: Review the deployment Summary and click Next to create the application. — Review the deployment Summary and click **Next** to create the application.

Step #12: Once the process completes successfully, click Close. — Once the process completes successfully, click **Close**.

Configure Deployment Type Properties

Step #13: Right-click the newly created application from the center list and select Properties. — Right-click the newly created application from the center list and select **Properties**.

Step #14: Navigate to the Deployment Types tab. — Navigate to the **Deployment Types** tab.

Step #15: Select the architecture deployment type (e.g., x64 edition) and click Edit. — Select the architecture deployment type (e.g., **x64 edition**) and click **Edit**.

Step #16: In the deployment type properties window, click on the Content tab. Check the box for Allow clients to use distribution points from the default site boundary group. — In the deployment type properties window, click on the **Content** tab. Check the box for **Allow clients to use distribution points from the default site boundary group**.

Step #17: Open the Deployment options dropdown menu and select Download content from distribution point and run locally. — Open the Deployment options dropdown menu and select **Download content from distribution point and run locally**.

Step #18: Click OK to save the deployment type properties. — Click OK to save the deployment type properties.

Step #19: Click OK again to close the main application properties window. — Click OK again to close the main application properties window.

Distribute Content

Step #22: Review the application shown in the Content page and click Next. — Review the application shown in the Content page and click **Next**.

Step #23: On the Content Destination page, click Add and choose Distribution Point. — On the Content Destination page, click **Add** and choose **Distribution Point**.

Step #24: Select the necessary distribution points from the list (such as All DPs or PXE DP). For most applications you will select all of the available distribution points. — Select the necessary distribution points from the list (such as **All DPs** or **PXE DP**). For most applications you will select all of the available distribution points.

Step #25: Click OK to confirm your selection. — Click OK to confirm your selection.

Step #26: Click Next to proceed to the Summary. — Click **Next** to proceed to the Summary.

Step #27: Review the provided details and click Next. — Review the provided details and click **Next**.

Step #28: Once the distribution finishes successfully, click Close. — Once the distribution finishes successfully, click **Close**.

Create a Target Device Collection

Step #29: Navigate to the Assets and Compliance workspace in the left navigation pane. — Navigate to the **Assets and Compliance** workspace in the left navigation pane.

Step #30: Expand Device Collections, right-click your desired organizational folder, and select Create Device Collection. When creating a new application it's best to begin in the Testing and Training folder, so avoid confusion over tested applications. This will be moved later. — Expand **Device Collections**, right-click your desired organizational folder, and select **Create Device Collection**. When creating a new application it's best to begin in the **Testing and Training** folder, so avoid confusion over tested applications. This will be moved later.

Step #32: Click Browse..., select All Systems as your limiting collection, and click OK. — Click **Browse...**, select **All Systems** as your limiting collection, and click OK.

Step #33: Click Next to move to the Membership Rules tab. — Click **Next** to move to the Membership Rules tab.

Step #34: If you plan to populate this collection manually or at a later time, click Next without adding any rules. — If you plan to populate this collection manually or at a later time, click **Next** without adding any rules.

If you choose not to define membership rules during setup, the collection will be completely empty when created.

Step #35: A warning dialog will appear stating the collection has no rules. Click OK to acknowledge. — A warning dialog will appear stating the collection has no rules. Click OK to acknowledge.

Step #36: Review the Summary and click Next. — Review the Summary and click **Next**.

Step #37: Click Close to finalize the creation of the empty device collection. — Click **Close** to finalize the creation of the empty device collection.

Deploy the Application

Step #38: Right-click your newly created device collection, hover over Deploy, and select Application. — Right-click your newly created device collection, hover over **Deploy**, and select **Application**.

Step #39: In the Deploy Software Wizard, click the empty software field to browse for your application. — In the Deploy Software Wizard, click the empty software field to browse for your application.

Step #40: Select the application you created earlier and click OK. — Select the application you created earlier and click OK.

Step #41: Click Next to advance past the General settings page. — Click **Next** to advance past the General settings page.

Step #42: Confirm the Content page settings and click Next. — Confirm the Content page settings and click **Next**.

Recommended Deployment Configuration

Ensure you configure the deployment properly based on user expectations and restart behaviors. Use the following table as a reference for common options:

Configuration Page	Field	Recommended Setting
Deployment Settings	Purpose	Available (Optional) or Required (Mandatory)
User Experience	User notifications	Only show notifications for computer restarts
User Experience	Maintenance windows	Commit changes at deadline or during a maintenance window (requires restarts)

Step #43: Choose your preferred deployment Purpose (e.g., Available) and click Next. — Choose your preferred deployment **Purpose** (e.g., Available) and click **Next**.

Step #44: Configure your scheduling preferences, then click Next. — Configure your scheduling preferences, then click **Next**.

Step #45: On the User Experience tab, check the box for Software Installation. — On the User Experience tab, check the box for **Software Installation**.

Step #46: Adjust the user notifications dropdown to your preference and click Next. — Adjust the user notifications dropdown to your preference and click **Next**.

Step #47: Review any Alerts configurations, then click Next. — Review any Alerts configurations, then click **Next**.

Step #48: Confirm your choices on the Summary screen and click Next. — Confirm your choices on the Summary screen and click **Next**.

Step #49: Click Close to finalize the application deployment. — Click **Close** to finalize the application deployment.

Step #50: Return to the Software Library to view the application and monitor its deployment statistics in the bottom summary pane. In most cases you can begin testing after you see success for 2, which will always include the primary site. — Return to the **Software Library** to view the application and monitor its deployment statistics in the bottom summary pane. In most cases you can begin testing after you see success for 2, which will always include the primary site.

Q: Why do I get a warning prompt when selecting the MSI file during setup?

A: Configuration Manager detects if the installer originates from an unverified publisher. You can safely click "Yes" to bypass this warning if you trust the source file.

Q: Can I proceed without adding membership rules to my Device Collection?

A: Yes. Configuration Manager will display a warning that the collection will contain no members. You can accept this and manually populate the collection later.

Q: What does the "Do not download content" option achieve?

A: This setting stops the client from unnecessarily downloading or caching the application payload before initiating the installation, executing it directly as configured.

Term	Definition
Device Collection	A grouping mechanism in Configuration Manager used to organize users or devices for targeted tasks, such as application deployment.
Distribution Point	A server role within Configuration Manager that hosts package source files for clients to download.
Deployment Type	The specific installation parameters and content (like an MSI package or script) assigned to an application in Configuration Manager.
MSI File	The standard Windows Installer package format used to install, modify, and uninstall software on Windows systems.