Much more robust content distribution
Most of my time in CM is cleaning up content distribution. Packages in WMI but not in Content Library, in Content Library but not in WMI, content failed validation, etc. We need a much more robust content distribution process. If the package list is not correct, auto repair. If content is in the content library but not vaild, remove it. If content distribution fails, retry it AFTER the previous has been cleaned up. Having to run PS commands to remove orphaned packages from WMI, and then run SQL queries to find packages ID's for Applications (which should be a column in the console btw) and then search for orphaned/corrupt .ini files in PkgLib, and having to do this on a daily basis if you want to keep your DP's clean and functioning, is ridiculous. The CM team has come up with a lot of great ideas and has worked very hard to make CM a great product. But this is a glaring issue that needs attention.
I have spent 2 days figuring out how to clean up orphaned software updates from DPs, and I am yet to figure out how to get rid of them from Content Library on the site server...
It seems to me that there is a lot of room for improvement here.
Hope this gets some attention in future releases.