Revamp the SCOM Installer
There are a lot of posts about the SCOM installation here, but this one is a bit different, although a full revamp of the installer is really in order.
First and foremost, I'd like to see the requirement of a user account with a user profile for installation removed. One could still use a SCOM admin account with DB rights to install, I would think, if the installer wrote the install logs to a different location. Right now, it needs a valid user profile, which makes it impossible to install using tools like SCCM.
I'd like to see the wrapper installer removed, and each MSI have command line arguments for installation, or some kind of an xml file that can be written which contains the installation parameters that those individual exes (like OMServer.msi) use to perform the install. Setup.exe is neigh impossible to use, and it means it cannot be packaged as an application in SCCM.
The RC4 requirement needs to be removed (which is currently filed as a bug in the installer, so maybe the rest of this can be "while you are in there...")
I'd like to see the pre-requisite components bundled with the installer where logical. SQL CLR Types, ReportViewer, and even the IIS components needed should be handled by the installer. others, like .NET 3.5 and Reporting Services would likely need to remain separate, but there are several pieces that could be added to the installer and be handled automatically.
Dovetailed from the above, I'd also like to see the installer either a) post-web console installation determine the type of installation you've just performed and tell you what settings need to be modified for constrained delegation to work with a standalone web console server, or b) try to configure those settings itself and notify on failure with explicit details on what you must do to resolve, or both a) and b).
Overall, the installer feels very much as though it has had more stuff bolted in to it over time, but has never had a complete repackaging, save for changing the splash screens.