Adding Applications
MDT allows you to install applications. This guide will show you how to configure that and how to add them to MDT. I will go ahead and outline the way I like to do things. For this guide will be adding "Primavera 6" to the MDT Applications.
So the first step you need to do is figure out how you will install the application. This can be from a powershell script, or just using the msi with a quiet switch.
Personally I completely and utterly refuse to add any Application to MDT unless I can make it one click. If I cannot install the Application silently, without interaction I do not install it. I will not add applications without a quiet automated way to install them. This means your MDT Deployments will always and forever be no touch deployments. I see very little point in adding applications that do not support silent switches.
There are ways I have discovered to install applications that don't support silent modes (ConEST being one of them). Essentially what I do is make a batch file that copies all files to where they need to go and import all registry keys. This only works on the simpler and older applications and isn't something I recommend unless you have to do it. I will have some outlines at the bottom of this article on how I do this.
Ok back to adding Applications. The one we are doing right now is Primavera 6.
So first things first, put all files related to the application in a single folder. This is also where you will put your batch/powershell file (if needed). Again remember, even if you can install the application using msiexec /qn its better to make a batch file to do the actual install. This allows you to install the software outside of MDT if you need to. Also when you are making your scripts try not to reference UNC paths if you don't have to.
Here you can see all files, as well as the powershell file for the application install.
After you have ensured your script works correctly and all files are in one folder go ahead and copy that entire folder to the MDT Desktop.
After the files have been copied locally to the MDT Server open up the MDT Deployment Workbench and under the deployment share go to Applications. Because this application is new to MDT and because I don't already have the vendor I am goign to create a new folder. Right click on Applications and say new folder, and type in the vendor name. For this I am going to type in Oracle.
After you add the new folder click on it, right click it and say New Application. You will be prompted with some options. In this case I am going to say "Application with source files" because we are adding an entire folder full of files and scripts. This will be the option you choose most of the time. Hit next and you will be shown a screen where you can specify the details of the Application. Now personally I am very OCD when it comes to stuff like this. So for the options I will type in exactly what I see in the Add/Remove Programs in the Control Panel. Click next when done.
It will then ask the source directory, go ahead and hit browse and navigate to the folder you copied to your desktop. Hit ok when done. It will then ask you to specify the name of the directory that will be created. This new directory will be in the Applications folder on the MDT Share, this is a special folder with locked down permissions. I always add a "Install - " to the name so I know if the folder is running an action or an install. I also tend to remove version information from the folder. So "Oracle Primavera P6 Professional 16.2.3.22257" becomes "Install - Oracle Primavera P6 Professional". Hit next.
It will then ask you for the command line. Remember how I told you I make all commands cmd commands even if running a powershell script? This is why. Applications only let you run scripts through the command line. so you will have to tell it you want to run a powershell script. Do this by using
"powershell.exe -file [filehere.ps1]" so in this case it will be "powershell.exe -File Install_P6.ps1"
Hit next a few times then finish. Remember to update your deployment share as well.
After this make sure you test it by imaging a new machine