Per AppDynamics support in attempting to identify the java 1.7 Sun+JRocket agent from the java 1.8 agent: "Unfortunately there is no way (other than the appdynamics download page and checking the checksums) that can show the difference between 1.7 and 1.8 versions." If I were to follow supports recommendation, this would mean that there would need to be 3 data stores that contained the checksums of every agent release since 20.7.0.0 (1 for java1.8, 1 for java1.7-ibm, and  for java1.7-sun+jrocket) so that you could check which list the agent you're working with falls under. The only way to build those data stores is to manually download and extract each checksum from every agent. Since that process would be far to costly from a data transfer and time expediture stand point... I have opted to alter the agent packages and add a unqiue coded entry and value to the MAINIFEST.MF under the base directory javaagent.jar file. The same place the entry that identifies the IBM agent from the Sun+JRocket agent. This allows me to gather the needed information at the same time and location as the 1.7 agent sub-distribution. This is a massive oversight on AppDynamics part in the configuration and release management disciplines. One that could have been easy corrected... in the exact same way that I have been forced to correct it for them. ... View more

https://docs.appdynamics.com/display/PRO44/Unattended+Installation+for+.NET Optional Parameters: AD_SetupFile: Pass the absolute file path to the setup configuration file. INSTALLDIR: Specify the the directory to install the .NET Agent executables and supporting files. DOTNETAGENTFOLDER: New in 4.1.3, specify the parent directory for local data including agent configuration files and log files. For example: msiexec /i dotNetAgentSetup64.msi /q /norestart /lv %TEMP%\AgentInstaller.log AD_SetupFile=C:\temp\SetupConfig.xml INSTALLDIR=D:\AppDynamics DOTNETAGENTFOLDER=D:\AppDynamicsData ... View more