We recently added a new MP to a trusted domain, and modified the boundaries, so client on that domain would only connect to that MP. We have no way of checking if this is working. A simple list of clients connected to which MP would be super helpful. We would be able to tell from a list which domains these clients are on and if they are connected to the correct MP. Also health info of the MPs, trolling through logs ain't fun. A quick easy look at MP health status to tell if something needs investigating.

Add in a client notification option to be able to restart the SMS Agent service on a machine.

Restart Components of Secondary Sites in the console through the component status and configuration manager service manager.
This can be done on the Primary site but the secondary sites are not listed via the system status\component status.

It would be great to see a tooltip or option in the cmtrace toolbar to get more details about a log file. For example when opening EPCtrlMgr.log I see a tooltip with the description of the log file "Records information about the syncing of malware threat information from the Endpoint Protection site system role server with the Configuration Manager database."

The ability to toggle split pane cmtrace in Software Centre. I like to see what’s going on when I’m patching, the ability to toggle a CMTrace pane showing tabs for the relevant client logs during patching e.g wuhandler.log, updateshandler.log, statemessage.log

It would be great if the Servicing Extension Tool released in 2014 would be integrated to the Current Branch Version. Separate installation still works for CB and show all Release KBs, new blogs, Site Versions and Client Targeting. See attached figure. So adding this stuff to current "Updates and Servicing" section as sub point would be fantastic. This helps also the community to see directly new KBs and information about issues etc. and they can faster react to fix it.

Is it possible to add a way to view Config Manager Client scheduled actions as interpreting scheduler.log needs a manual when you factor in randomisation and deferals?

Would be particularly helpful when troubleshooting policy evaluation and configuration items

Newer Components like

​- BusinessAppProcessWorker​
- SMSCloudConnectionSTSWorker​
- SMSDataEngine​
- SMSPhasedDeployment​
- WsfbSyncWorker

should also be affected by the Archive RegKeys:

HKLM\SOFTWARE\Microsoft\SMS\Tracing\ArchiveEnabled
HKLM\SOFTWARE\Microsoft\SMS\Tracing\ArchivePath

Currently the old Logfile Versions are saved at <InstallDIR>\Microsoft Configuration Manager\Logs\

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.