I'm in the process of preparing to distribute Education Master Suite 2014 with SCCM 2012. Various machines will need to end up with differing subsets of the suite. Distributing the entire suite in one piece won't work due to the large size and installation time limits. With SCCM 2012, the installation package is normally downloaded to the local machine before the installation process starts.
Since there is a significant overlap between the 3rdParty Prerequisites, I was hoping to be able to configure the suite once and then package each application separately. Or would it be a better idea to download the separate installers for each application and then package each that way even though many of the "3rd Party" stuff ends up being part of the installation set for each and every application which redundantly uses up distribution point disk space and network bandwidth as the same files get transferred repeatedly.
Looking at the text files created in "SMS_SCCM Scripts" folder, it appears that many of the installers expect to be part of the same folder structure as indicated by the ADSK_SOURCE_ROOT attribute.