Make the log files directly accessible via the console rather than digging around in the file system trying to remember which file holds which logs and ideally make them accessible from a context menu in the relevant areas.

Add an Alert that shows the state of the CMG Connection Point.

Currently, I have no automated way to tell if the CMG is healthy unless I go into the console and run the Connection analyzer.

I'd like to see a built-in alert I can configure to notify me if the CMG service is in a non-Ready state, the Connection Point is "disconnected" or the number of "Clients online from CMG" is below a specific threshold.

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.

Many times when you are testing something with ConfigMgr, you'd like to send client state messages immediately to MP. Now you need to wait for state message reporting cycle to occur. You can start the other client cycles manually with Configuration Manager Control Panel utility (or remotely from ConfigMgr console) except state messages.

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.

we need a better way to check, and resolve client health from within the console with out having to go the web and collect a wide range of third party scripts/apps to help resolve the issues.

for example: duplicates GUID. inactive clients, etc..

things like this should be available from the start.

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!

Log files - It would be helpful to have links to log files that pertain to the different tasks we do in SCCM. For instance when deploying apps we could have access to log files right in the Deployment(AppName) area

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.

I would love to see a infrastructure health dashboard. A go to location for making sure all MPs, SUPs, DBs etc. are healthy, rather than having to go through system statuses in the console. Perhaps have some tiles that show how many endpoints are hitting each MP, SUP as well.

Have the ability to select the Updates show in the content of a workstation and the ability to click install and to see the error if it reports back an error.

This can currently be done for Application content but cannot be done for Updates.

To try to get this capability just for Updates for troubleshooting/support for workstations. You have to leverage ReCast- Right Click Tools and leverage the Remote Software Center to kick off updates for install for workstations that you are troubleshooting.

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.

The third party application SCCM client center provides essential troubleshooting support for the client. Why not integrate the features into the Admin console?

For large environments the ability to log to a central database. this would collective provide a central location for all server logs (DPs, MPs, ect..) deployments with a high server count (500 DPs), if\when there is a issue, the logs role over very quickly and the chance at catching the issue is not likely

Record log file entries in local client time NOT UTC. cant accurately trouble shoot time sensitive event.

We are finding we have reached a point where the IIS logs on our management points are frequently close to filling the disks. It would be nice for ConfigMgr to have a native ability to configure a cleanup of IIS logs for components that use it rather than having to create a separate "scheduled task" or similar action.
This could even be an action triggered when the component monitor reports a low disk space on MP status.

When viewing a Status Message that says "see log for details" the message shoudl provide some from of link to the correct log file(s).