Add .exe installers to the list of application templates
Instead of using script install for a .exe file make a separate one that can read the exe file just like it does the MSI file. Also when you click on the script installer have it look for Powershell or VBS or HTA scripts and not .exe files.
Have to say, I agree with this one, but I think the exe component may be out of reach for the config Mgr team alone especially in the short term. The script installer should look for scripts (.bat,.vbs,.ps1 at a minimum) though, that has always annoyed me.
I think the biggest issue with the exe option is that there is no standard for exe files.
I always thought that MSI stood for Microsoft Installer, but it is rare to find anything supplied by Microsoft these days in the MSI format, so if Microsoft rarely use MSI's, why would anyone else.
As Microsoft have moved to exe installers for the majority of their software, maybe something needs to be organised between the CM dev team and the rest of Microsoft to find a way to standardize and make Microsoft exe installers easily deployable from CM or standardize on a format that is more easily deployed from CM.
Maybe you can lead the charge to standardizing exe installers for Microsoft products in a way that you can work with in CM. (if MS standardize, maybe others will follow...). If you then add support for exe's in the wizard, would there be a way for it to only see the supported type exe's
I realize there are many different formats for exe's and a lot of them are wrappers with various installers inside, including MSI's, but maybe a meeting internally to decide on some standards might be the first step. We can only hope.
Note that on this page, there is a list of the issues with exe's, maybe you can use that in your meeting agenda with other department heads for standardization of exe installers :) - https://serverfault.com/questions/11670/the-corporate-benefits-of-using-msi-files/274609#274609