Applications: Autodesk Design Review 2012 & Trueview 2012

Autodesk Design Review 2012 has a few dependencies. It needs 3 Visual C++ Redistributables and the .NET 4  framework.
Visual C++ 2005 SP1 & Visual C++ 2010 are installed as you would expect:

vcredist_86.exe /q

For 2008 I eventually used this command:

vcredist_x86.exe /q:a /c:"vcredist_x86.exe /q"

Don't really see why they had to change this but it doesn't work with the usual switches.
Then we need to install .NET 4. This installation requires a reboot and the only way I was able to make this install without stopping my Task Sequence is by creating a .cmd file with the following content:

dotNetFx40_Full_x86_x64.exe /q /norestart

I don't know why I had to create the batch file but it doesn't work if you use this command in MDT 2010.

As all the prerequisites are installed, you can now install Autodesk Design Review. Get the .msi from their site and use this command to install it with MDT 2010:

MsiExec.exe /i SetupDesignReview2012.msi ADSK_DESKTOPSHORTCUT_1=0 ADR_DONOTSHOWAGAIN=1 ADR_NEXT_INITIAL_CHECK=1 PREFERENCELOCKED=1 /qn

This will disable update checks, will not create the desktop shortcut and disable some other crap.

Applications: CutePDF Writer

CutePDF Writer is a virtual printer. It creates a .PDF document in stead of printing the information. We have noticed that it works way better for bigger files than the other options that are available. I had a small issue with adding it to the Applications in MDT 2010 though. You need to make sure that the converter is installed before the software itself, so create a dependency.
The command for installing CutePDF Writer is "CuteWriter.exe /verysilent /no3d". This will stop the installer from opening a browser window and will prevent installation of AskJeeves. The installation of AskJeeves was problematic because it had to be removed afterwards and it changed the default homepage.

Applications: Java JRE 1.6.0 update 26

Get your .msi file as instructed here.
I used the JRE from the oracle site but that shouldn't make a difference.
The key is to use this EXACT command:

msiexec /i jre1.6.0_26.msi SYSTRAY=0 EULA=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 JU=0 REBOOT=ReallySuppress /qb

This will make sure the updater doesn't run and your users do not get Java update requests.

Installing software per model.

Sometimes you will want to install software or a driver package per model.
A good example for this kind of requirement are the drivers that cannot be installed using the .inf and .sys files such as the HP 3D Drive Guard drivers.
You need to edit your customsettings.ini file.
Change "Priority=Default" to "Priority=Model, Default".
The model variable will automatically be set when the Task Sequence runs.
Then create a subsection for your model. Make sure that this matches the WMI query result for your model!
In my case this would be:

[HP EliteBook 8460p]
MandatoryApplications001={Application GUID}

The task sequence will now do all the default actions but also install this application if you're running it on an HP EliteBook 8460p.

Applications: Office/Visio/Project 2007 Language Packs

The previous entry was very simple. The language packs are a bit harder.
These require custom .xml files that you have to create yourself.

For office, the file for the French language pack looks like this:

<Configuration Product="OMUI.fr-fr">
<Display Level="none" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" />
<AddLanguage Id="fr-fr" ShellTransform="Yes" />
<OptionState Id="OfficeMUI" State="Local" Children="force" />
</Configuration>

For Visio & Project, change where needed.
For Project, change the file to:
<Configuration Product="PMUI.fr-fr">
<Display Level="none" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" />
<AddLanguage Id="fr-fr" ShellTransform="Yes" />
<OptionState Id="ProjectMUI" State="Local" Children="force" />
</Configuration>
Visio:
<Configuration Product="VisMUI.fr-fr">

<Display Level="none" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" />

<AddLanguage Id="fr-fr" ShellTransform="Yes" />

<OptionState Id="VisioMUI" State="Local" Children="force" />
</Configuration>

For other languages, change every fr-fr to the correct language. You can find these easily in your installation folder should you not know them by heart.
Now, put these .xml files in the folder where your Office Language Pack setup.exe is and run the following command for unattended installation of these language packs:
"setup.exe /config config.xml"

Applications: Visio/Project 2007

Deploying Visio/Project 2007 is as easy as deploying Office 2007. Just create your .msp file (by running "setup.exe /admin" to launch the office customization tool) and make sure to at least:
-enter your product key
-accept the license terms
-choose "basic" or "none" display level
-uncheck completion notice
-check suppress modal

Save the .msp file to the same folder of your setup.exe as custom.msp.
The application will now install without user interaction if you use the command "setup.exe /adminfile custom.msp"