In your CustomSettings.ini file, you would add something like the following to a section of your choice: In your CustomSettings.ini file located in the MDT Settings package (created by default when you create a new MDT Task Sequence in ConfigMgr) or with a Dynamic Variables step in the Task Sequence, you define a variable list with values of the applications that you want to be installed. Instead of adding a step to install a single or up-to 10 Applications in a regular “Install Application” step, you could leverage the Install Application step to install Applications based upon something called a Base Variable. How it worksīefore we start talking about the script that I’ve written, let’s just walk through how the whole process works when you want to install Applications based upon a variable list. In this post I’ll walk you through how the script works and how to implement it in different scenarios. This works great, however as you may have noticed I’m not a fan of VB, so I’ve re-written the VB script in PowerShell.

The section in an MDT integrated Task Sequence called Install Applications includes a VB-script from MDT that converts a variable list that is later on used in the next step called Install Applications.

When you integrate MDT with ConfigMgr, you get tons of extra features and great additions. The scenario of dynamically installing Applications based upon a variable list (CustomSettings.ini or Dynamic Variables) during OS Deployment is not something new and has been around for ages.

Mdt time now