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.

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.

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.

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

When checking Client Status it would improve the experience if I could run ccmeval on a client that has failed any test immediately to see if the issue still exists.

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 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.

In our environment SCCM Server installs client on discovered resource but they failed to install due to machine specific issue, could you prepare a tool which we can give it to floor support technician to run on machine which have SCCM Client issue or Installation failure, the tool should check for all prerequisites for client install also firewall issues like (WMI and File and Print sharing not allowed ) it should the issue with which it becomes easy to fix the underlying problem and get the sccm client successfully deployed

The new option in the console for Client diagnostics - Collect Log files, need to be able to trigger option from the client running a task sequence. The reason for this is when a task sequence logic encounters a error and you want to auto capture the logs, this client action will be key to automating the log captures. Also for Windows 10 Servicing where the machine runs on the Internet and capturing the logs works great over the CMG, but again just want to automate the log capture than rather manually capturing the logs.