Monday, May 07, 2012 4:05 PM
I'm still using MDT 2010 Update 1, but am planning to install MDT 2012 soon. I'm curious about the changes, if any, there are with respect to the command line when adding Apps with Source Files to a Deployment Share. I'm not real comfortable using the command line, but I found a nice tool called MDTMSIApp.exe that does a great job of creating the comand line parameters and switches, and capturing the App's GUID. I know it's just for evaluation, but I have used it in Production for almost all our Apps.
Does MDT 2012 improve on MDT 2010's ability to import/add Apps with source files so I don't have to "experiment" with parameters and switches on my own?
Monday, May 07, 2012 5:14 PM
The problem is that there is no one-size fits all for installing any application. Just like the applications, installations of application can be and are unique. There's no magic to discover how an application should be installed. There is some baseline standardization based on the installer technology used, but that in way eliminate the uniqueness of every application and its installer. See my recent post on this same subject: http://social.technet.microsoft.com/Forums/en/mdt/thread/b9cc136b-d497-4fd8-93ab-65e81e954284.
There will always be a level of testing and trial and error involved because there are a large number of variables when installing software; however, consulting the vendor's documentation (as mentioned in that thread) is the best place to start.
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
- Marked As Answer by RV2011 Monday, May 07, 2012 5:53 PM