There is a lot of very detailed information in the individual component client logs files, But with all that detail in so many logs, it can be difficult to tell what the client is doing at any given time. I would like to see a master log of all the high level client activity and timestamps.
12:00 hardware inventory started
12:02 hardware inventory complete
12:05 policy download
12:08 software inventory started
etc...
It would help narrow down the number of logs to examine and the timeframes to look at.

Make Software Center available (as an App?) so that you can see exactly what is in Software Center for a remote machine. You launch the app on your technician PC, supply the machine name and user name and the Software Center shows up on the technician PC with exactly what the user sees. This would be very valuable for level 2 and service desk people to help users.

One of the most issues found is database performance based on fragmented indexes. A notification or automatic defragmentation on for the relevant indexes would be nice.

IT would be a nice option to have the option to clear CCMCache folder directly from SCCM Admin console by right-clicking on the client.

@JasonSandys: "When it works, it works fine. When it breaks, God help you cause no one else can."

Add your comments on how we can make this better.

Configuration Manager Service Manager (the start/stop services window) should be in built-in as part of Monitoring, and sped up!

It would be great if in the new Suppert Center Advanced Log File Viewer, there would be an option for Advanced Filters, when opening a log file, the filters load automatically and we dont need to load them manually everytime we open a log.
Same as with the other buttons, that can be activated and deactivated.

Upgrade needs to have better logging - for example during an upgrade, the spimportinventory stored procedure was failing on a merge with SQL error 8672:
The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row.

Tracking this down was difficult because of the MERGE statement - if each row were being processed separately, the specific problem data could be called out when an error occurs.

When installing a cumulative update on console , the version seen in windows "program and features" or in sccm resource explorer - installed application is not updated. making the CU deployment difficult to follow up. Could you be sure this is updated with the CU installation. screenshots for CU3 in attached doc

integrate sccm logs inside the console with nice view and charts

It would appear at a high level that adjustments were not made to coordinate support timelines across the architecture of components for SCCM, Example, while extending Windows 10 1709 Ent. support to 30 months, I would expect the ADK to be supported with the Configuration Manager release 1810, (1903, 1909, etc.) to maintain parity with bug fixes.