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

I implemented WDAG via group policy easily.
Switched to ConfigMgr control of it and I cannot get it to work. Trying to manage the exclusions, etc. I cannot roll back (only on my machine) I deleted the deployment. how can I tell what configmgr is doing on a client regards updating wdag settings, etc?
the documentation refers to group policy controlled wdag, but the terms are different.
Anyway, I'm not an idiot, but I don't understand how it's working/not working. I'm sure it's amazing, but I'm missing something.

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

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.

I figured it was time to have a UserVoice item that gathers together all the known misspellings throughout the product. Add your own to the list below making sure to note the version of Configuration Manager. Be sure to indicate where in the console or what log.

[CB 1702][ruleengine.log] Deadlock detected, not retry since there is 1 open transaction(s)

[CB 1702] [Package Manager Status Message] Package Transfer Manager is currently sending software distribution package ### to distribution point server ### (Education|Business) percent of the sending has already completed.

Cancelling or deleting a client operation under Monitoring > Client Operations can only be enabled if the Security Role has security scope set to the All Systems collection. There should be a security permission to enable the ability to cancel or delete client operations instead of adding all systems collection security scope to a role.

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

There should be a built-in PowerShell Cmdlet to disable/enable verbose,debug,sql...etc. logging options instead changing Registry keys.

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.

In https://support.microsoft.com/en-us/help/3213242/software-metering-agent-fails-with-software-metering-failed-to-start-p, MtrMgr.log may indicate that the prepdrv is no longer successfully registered. A potential fix could be adding a CCMEval task which would detect if Metering is enabled on the client, and if so, confirm that prepdrv is successfully registered (read mtrmtr.log, but there may be a better programmatic way to do so), and if not successfully registered, register it.

I would like to be able to right-click a computer in the Deployment Status details and have options like remote control.

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.

I want to beable to replicate all logfiles from ccm client to server into a folder structure build like Site / computer name
This will make it easy to read logfiles from failed installation easier. even when client is offline
This should be done automatic when the logfiles is updated.

When importing drivers and many other tasks, configuration manager displays a notice for the logfile to monitor the task, but there is no hyperlink to open the same. The admin shouldn't have to go searching for these logs, but be presented a hyperlink to the directory.

The easiest way to find a device on a network is with the physical layer information. I can't even understand why this wouldn't be an option. At times while troubleshooting getting the IP address from the end user is the only information that you can gather.