@Curtis CruzHave a look at my articles on distributing customisations, we used this method to disrtibute the files. However it does not replicate registry entries that the installers might make.https://blogs.msdn.microsoft.com/developingfordynamicsgp/2008/08/20/automating-distribution-of-customizations-part-1/https://blogs.msdn.microsoft.com/developingfordynamicsgp/2008/08/26/automating-distribution-of-customizations-part-2/FYI: All Winthrop Development Consultants products support a scripted silent install. You should check with the other ISVs if they can do the same.https://winthropdc.wordpress.com/2015/08/24/gppt-installing-gp-power-tools-upgrading-from-sdt-silent-installs-and-more/Happy New Year
msiexec /i "E:\GP2013 Software Installs\MDGP2013_R2_DVD_ENUS\Bin\GreatPlains.msi" /qb+ SQL_SERVER_NAME="SQLservername" INSTALLDIR="C:\Program Files\Microsoft Dynamics\GP2013" SELECTED_COUNTRY="United States" TRANSFORMS=:Inst01 INSTANCE_NAME="CORP" MSINEWINSTANCE=1 ADDLOCAL=EREC,FAM,MFG,PSTL,SP
Curtis, I'd capture everything, filter for 'setup.exe' or whatever the name of the installer is, then save the filtered results to a file for review.
Senior Systems Specialist C A L Business Solutions Inc. Phone: 860.485.0910 x110
If you've found this thread useful, dive deeper into User Group community content by role