How do I sequence applications in MDT?
Applies to: Microsoft Deployment Toolkit (MDT) 8456 and later
Last updated: May 2025
Problem
You need to control the order in which applications are installed during deployment—for example, installing dependencies (like .NET or Visual C++ runtimes) before dependent software (like Office or custom apps).
Solution
MDT allows you to control application installation order using one of two methods:
- Application Bundles – group apps in a specific order
- Multiple “Install Application” steps in a Task Sequence
Option 1: Use an Application Bundle
An Application Bundle is a single item that includes multiple apps in a defined order.
Step 1: Create the Bundle
- In Deployment Workbench > Applications
- Right-click > New Application
- Select Application Bundle > Click Next
- Name the bundle (e.g.,
Base Software Stack) - On the “Included Applications” screen, add apps in the exact order you want them to install
Step 2: Use the Bundle in Your Task Sequence
- In your Task Sequence:
- Find the Install Applications step
- Select Install a single application
- Choose the bundle you created
Option 2: Add Multiple Install Steps
You can manually add multiple “Install Application” steps in the Task Sequence for full control.
Step 1: Open the Task Sequence
- In Deployment Workbench > Task Sequences
- Right-click your sequence > Properties > Task Sequence tab
Step 2: Add Install Application Steps
- Under the State Restore phase:
- Click Add > General > Install Application
- Set each to install a single specific application
- Repeat for each app, in the desired order
Example Order:
- Install Visual C++ Redistributable
- Install Microsoft Office
- Install Chrome
- Install Custom App
Best Practices
- Always install dependencies first (e.g., runtimes, .NET, frameworks).
- Avoid duplicate applications in both the bundle and separate steps.
- Use clear naming for application versions to avoid confusion.
Notes
- Logs for application installs are found at:
C:\MININT\SMSOSD\OSDLOGS
- You can apply conditions to specific install steps (e.g., WMI queries, roles).
- Application steps run in sequence; one failure may halt the deployment unless error handling is configured.




