I think this is what we are all looking for:
Repair applications - You can now specify a repair command line for Windows Installer and Script Installer deployment types. This was released with 1810
I often have seen that only for the purpose of troubleshooting colleges prefer a package than an application. A program can be enforced. At the same time a program is made available to provide the uninstall so users can do a repair by themselves. It is not the most sophisticated approach but often simple and helpful. Giving people the power to help themselves would mean a reduction of help desk calls and more user satisfaction. The uninstall command and the install command exist normally in an application. So it would mean nearby no effort to provide a reinstall button for enforced applications. Giving admins control which applications should show this button would be appreciated.
152 votesstarted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
This is now available in the 1612 Technical Preview.
Is this a similar suggestion? Maybe the voices can be give to this: https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8558383-improved-automation-and-extensibility-by-exposing
I feel even that duplicates exist is unacceptable. After 7 years it should be built-in what is described here: https://techcommunity.microsoft.com/t5/Configuration-Manager-Archive/Known-Issue-and-Workaround-Duplicate-Records-When-You-Use/ba-p/272965
1,403 votesplanned · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
Saw a working demo of this recently so updating to planned.
I also would love to have the complete history of equivalent PowerShell commands. Exporting results from the console is not as satisfying as having pure text in objects that can be sorted, filtered and the properties needed could be selected. As well as working around errors I encounter when using the WMI PowerShell cmdlets but is successfully handled by the console. This is especially valuable as the documentation of all WMI classes seems never to be up-to-date or at least I do not find it. Additionally I find the performance of the console could be better some times. So having the PowerShell commands that retrieve only what is needed at the moment speeds up the work with SCCM tremendously
Check out the new uninstall behavior in 1804 tp.