MDT 2010/ConfigMgr – UDI – Configuring Application Mappings and Dependencies
This post will cover setting up application dependencies and application mappings with UDI (User Driven Installation). In this example, we are going to configure a automatic package mapping for Adobe Reader 8.2 to Adobe Reader 9.0. We will also configure a prerequisite for Office 2010 of .Net Framework 3.5. An application mapping will automatically install an application based upon another application installed already in the client system. This is most commonly used for upgrading older versions of applications, like our example from Reader 8.2 to 9.0. Application dependencies can be used to ensure that application prerequisites are installed, for example making sure .Net Framework is installed for a .Net dependent application.
The first thing we need to do it open up the UDI Wizard Designer, open up the xml you want to edit (the default xml is udiwizard_config.xml) and then go to our Application/Package Selection screen.
Next, we need to add the packages we want to work with to the selected packages list.
Next, we will need to go to “OSD Applications” and then add the applications to our list.
Adding Adobe Reader 8.2.0 to both 32-bit and 64-bit.
Adding .Net Framework 3.5 SP1 to both 32-bit and 64-bit.
Now we have them added to our list and we can go ahead and create the dependencies and mapping.
First, lets create the mapping for Adobe Reader 8.2 –> 9.0.
We will need the Add/Remove Programs display name along with the application GUID. The easiest place to get the GUID is from the program properties in ConfigMgr if you have imported the MSI code. (Or you can do a quick import to get the code).
Once you have the GUID and display name, then we will want to click “Add” and then enter that information.
Now we can select “OK”.
Next, lets setup our dependency for Office 2010.
Next, we will want to select the dependency and then choose “Require” for our case.
Next, we can click “OK” since we’ve added our dependency.
If you click on Adobe Reader 9.0, you can see the mapping listed:
If you click on Office 2010, you can see the dependency listed:
Next, lets save our configuration and then update the distribution points.
Now it’s time to test! So we will run our UDI Task Sequence on a client machine and launch the wizard.
Because we’ve setup a mapping for Adobe 8.2 to automatically install Adobe 9.0, you will notice that Adobe Reader 9.0 is checked by default when the wizard is run, even though we didn’t configure it to be selected by default.
Also, we had configured Office 2010 to have a prerequisite of .Net Framework 3.5 SP1. So you will notice as soon as we check Office 2010, .Net Framework 3.5 SP1 will become automatically checked.
Now you’ve seen how to create basic application mappings and application dependencies. Hope it helps.