We need a "manual" or force clean - a complete removal of all traces of the ConfigMgr client to be supported again.
Too much wasted time is spent trying to track down all the left overs that cause unhealthy clients.
Thankfully some of those in the community have published scripts that help, but unfortunately they are "not supported" and many times incomplete.26 votes
I have no metrics to back this up, yet I feel Support Center is under utilized as it has to be installed separately and manually from the MECM client.
Could you give us one or more of the following options?
1) Add an checkbox in the client install settings area to have Support Center install after the MECM client is installed.
2) Have Support Center install by default like the MECM client
3) Make installing Support Center an option in the Add dropdown under a Tools folder, in the TS editor.15 votesNoted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We don’t package Support Center with the client at this time because it would add 15MB or so to the MSI package, and we’re trying to avoid bloating it as much as possible.
That being said, there’s certainly no reason we can’t have other solutions in place to make it easier to get Support Center onto client machines or to otherwise opt-in to having it distribute with clients.
We will look into ways to improve this in the future.
Allow to select view font in CMTrace, eg monospace. Per session (some files look better in default font, some would look better to view in monospace).15 votes
The old version of HASHDIR.exe tool doesn't work with new version of SCCM. This could be because of SHA256 hashing of SCCM CB.
Is there any possibility to release a new version HASHDIR.exe tool for SHA256 hashed content. This would be really useful whenever SCCM admins want to perform has miss match troubleshooting ...
This concern was raised by Stefan - https://twitter.com/stefan_farnik/status/10300752183652270085 votesNoted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We’d like to better understand the scenario here. How often do you need to troubleshoot hash errors and how did this tool help? Could better status messages or in-console monitoring help here?
The Support Center utility is a great addition but doesn't seem to support specifying a remote computer to connect to from the command line. This would allow it to be called automatically from scripts and other tools.
This is option is implemented for the remote control viewer by running: CmRcViewer.exe <remote-computer>
Likewise it would be great to be able to call the Support Center thus:
ConfigMgrSupportCenter.exe <remote-computer>4 votes
The CMTrace tool is able to parse non-SCCM log files (e.g. 1E's Nomad logs) to properly pick up timestamps, process ID's etc. It would be very helpful if this could be added to the Support Center/Support Center Log File Viewer. It seems3 votesNoted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We will look into this. If you could provide some samples of log files that are not properly rendered by Support Center, please attach them or e-mail them to me so we can validate them.
Current Config Manager client install includes an option to deploy CMTrace along side the client. Please include an option to deploy OneTrace as well\instead.3 votes
I often use a tool to search all log files for a particular entry, and the search results tell me what line the entry is located on within each log file. If CMTrace had line numbers, it would help locate the search results within the log files.2 votes
Interesting idea! One potential problem here is that a “line” in CMTrace may not map to a single line in a log file — it could actually be a concatenation of several lines.
We’ll think about this problem and take this idea under consideration for the future. Thanks!
- Don't see your idea?