Home > Deployment, MDT > Using Application “bundles” in MDT 2010

Using Application “bundles” in MDT 2010

One of the more interesting things in MDT is the “Application bundle” application install option.  What an application bundle allows is the ability to install multiple applications, in order, as dependencies.  Think of it more as a logical container for applications that need to be installed, perhaps in a specific order, or as prerequisites for another application (like, for instance, installing Visual Studio 2008 prerequisites, Visual Studio itself, and then the latest service pack).

Adding the application(s)

To create an application bundle that will show up in the list of applications to install (or be available to configure via a task sequence), you first need to add all of the applications to MDT that will make up the bundle.  This is done similar to adding Office 2007 as I documented in my post on creating an MDT deployment point – you must create a New Application and add it’s source files to the deployment share.  I’ll document quickly how to add the Windows Live Essentials components to your deployment share and “bundle” them (instructions on getting the .msi packages you’ll need from the Windows Live Essentials downloadable package can be found here, if you do actually want to try this).

First, right-click on the Applications folder in the deployment share (in this example I’ve created a folder underneath applications to hold all of the Windows Live installation apps – this is purely for cosmetic reasons) and select “New Application” from the drop-down list:

New Application

Select “Application with source files” from the first wizard page, click “Next”, and then fill out the information about the application and click “Next” again – in this example, I’m adding the x86 package for the Application Error Reporting component of Windows Live:

New Application Wizard

Point the wizard to the local path that contains the setup package, and click “Next”:

Source directory

You will need to provide the actual installation command used to run the setup – in this case, the command is “msiexec /i dw20shared.msi /qn”, so I’ve entered that into the “Command line” field:

Command line

Once that’s done, click “Next” a few times and the application will be added to your Applications in your deployment share.  Next, right-click the new Application and select “Properties” from the drop-down list:

Properties

Make sure to *check* the box labeled “Hide this application in the Deployment Wizard” – this will keep the individual installers from showing up in the list of applications to be installed during deployment, ensuring only the bundle will be used to install the apps, in the correct order – click “OK” to save the changes:

Hide application

Creating the bundle

Once you’ve added all the other components necessary (repeating the above steps for each application that will make up your bundle), the bundle itself needs to be created.  To do this, right-click on the Applications folder (or any subfolder, as in my example) in the deployment share, and select “New Application”:

New Application Bundle

This time, select the “Application bundle” option from the list of application types, and click “Next”:

Application bundle

Fill out the details of the application as you would any other application, and click “Next” a few times until the new bundle is added to your Applications list:

Application bundle details

Next, right-click on the new Application bundle in the Applications list, and select “Properties” from the drop-down list:

Properties

Go to the “Dependencies” tab, and click the “Add” button:

Add dependencies

In the “Select an item” window that pops up, select the application installers from the list, one at a time (clicking “OK” after selecting each to add to the list), until you’ve got all of the applications that will make up this “bundle” in your list, in the order you want or need.  Note that you can use the “Up” and “Down” buttons to move applications up and down the list in this window if you didn’t add them from the Applications list in the order required:

Application dependencies list

Lastly, right-click your deployment share and choose “Update Deployment Share” to update it, and also right click on your Media and select “Update Media Content” (again, as per previous posts on this subject).  Once these complete, you can copy the updated media to your USB key, or burn the .ISO.  The new “bundle” will show up in the applications list during deployment, and will install each application, in the order it is listed in the “Dependencies” tab during deployment if it’s selected to be installed.

If you’ve got lots of applications that you deploy to each and every build you do, this is a great way to cut down on the clicking in the deployment wizard – or makes for fewer entries in your task sequences for applications.

Categories: Deployment, MDT Tags:
  1. Simon
    February 9th, 2010 at 18:32 | #1

    I am having an issue with MDT2010. We use multiple makes/models of machine with deployment and I need to add in specific applications (namely Biometic(fingerprint) software for each model – ie: only the 32-bit Lenovo Fingerprint reader for Lenovo machines and NOT the Panasonics in use … and also the Panasonic Fan Application for the Panasonic’s and NOT the Lenovo’s etc … I would ideally like to keep the main Application screen clear – as all of the applications listed here during the deployment are make/model independant (ie: Office, Reader etc). Can you please advise on how this might be possible ?

    Thanks in advance!

  2. Wooaple
    August 13th, 2010 at 19:11 | #2

    Really good work. :D

  3. Bob
    February 19th, 2011 at 15:02 | #3

    @Simon
    Did you find out how to deploy applicationd per model? I am trying to do the same.

  4. jprice
    April 18th, 2011 at 10:11 | #4

    @Simon and Bob, you will probably need to create an SQL database, create a database entry for the specific computer that requires the fingerprint reader software/driver, then update the deployment share.
    of course, that’s a very rough description of what to do, not to mention you’ll need to install and configure SQL Server 2008.
    my suggestion would be to manually install the fingerprint reader software/driver once the image has been deployed to the Levono machines.

  5. Ben
    July 7th, 2011 at 01:49 | #5

    http://www.myitforum.com/forums/m229103.aspx

    Follow this link, it has info on how to achieve what you’re after without a database

  6. January 27th, 2012 at 12:25 | #6

    Hello Simon. I also have the need to automatically deploy an application based on hardware make\model without an MDT database available. Not only that, I needed to have the application deploy silently without user intervention, and hidden from the application screen in the MDT wizard. I was able to figure out how to do this by using a custom batch file. More information about how to do this is on my blog here: http://www.joedissmeyer.com/2011/08/install-mdt-application-based-on-model.html

    To achieve what you are trying to do, here is an example:
    1) Create a new application in MDT.
    2) Create the install.cmd script for this application as defined in my blog post above.
    3) Add the application to an Application Bundle – since this script will exit automatically if the correct hardware model is not detected this is safe to add to a mandatory app bundle without any side effects. If you are not using app bundles, then add the GUID of the application as a mandatory application in customsettings.ini, or directly as an additional task in your task sequence. If you are not skipping the Application selection in the MDT wizard I suggest checking the “Hide this application in the Deployment Wizard” in the app properties so it isn’t listed.

    This will help you achieve your deployment goal by hiding the app and deploy based on make and model WITHOUT any user intervention. Good luck!

    @Simon

  7. January 27th, 2012 at 12:27 | #7

    @Bob
    Hi Bob. Here is a way to deploy an application based on make\model in MDT:
    http://www.joedissmeyer.com/2011/08/install-mdt-application-based-on-model.html

  1. No trackbacks yet.

Bad Behavior has blocked 92 access attempts in the last 7 days.