Support Center for Configuration Manager
Applies to: System Center Configuration Manager (Current Branch)
Starting in version 1810, use Support Center for client troubleshooting, real-time log viewing, or capturing the state of a Configuration Manager client computer for later analysis. Support Center is a single tool to consolidate many administrator troubleshooting tools.
Support Center aims to reduce the challenges and frustration when troubleshooting Configuration Manager client computers. Previously, when working with support to address an issue with Configuration Manager clients, you would need to manually collect log files and other information to help troubleshoot the issue. It was easy to accidentally forget a crucial log file, causing additional headaches for you and the support personnel who you're working with.
Use Support Center to streamline the support experience. It lets you:
Create a troubleshooting bundle (.zip file) that contains the Configuration Manager client log files. You then have a single file to send to support personnel.
View Configuration Manager client log files, certificates, registry settings, debug dumps, client policies.
Real-time diagnostic of inventory (replaces ContentSpy), policy (replaces PolicySpy), and client cache.
Support Center viewer
Support Center includes Support Center Viewer, a tool that support personnel use to open the bundle of files that you create using Support Center. Support Center's data collector collects and packages diagnostic logs from a local or remote Configuration Manager client. To view data collector bundles, use the viewer application.
Support Center log file viewer
Support Center includes a modern log viewer. This tool replaces CMTrace. OneTrace provides a customizable interface with support for tabs and dockable windows. It has a fast presentation layer, and can load large log files in seconds.
Support Center also includes Windows PowerShell cmdlets. Use these cmdlets to create a remote connection to another Configuration Manager client, to configure the data collection options, and to start data collection.
Install the following components on the server or client computer on which you install Support Center:
An OS version supported by Configuration Manager. For more information, see Supported OS versions for clients. Support Center doesn't support mobile devices.
.NET Framework 4.5.2 is required on the computer where you run Support Center and its components.
Find the Support Center installer on the site server at the following path:
After you install it, find the following items on the Start menu in the Microsoft System Center group:
- Support Center (ConfigMgrSupportCenter.exe)
- Support Center Log File Viewer (CMLogViewer.exe)
- Support Center Viewer (ConfigMgrSupportCenterViewer.exe)
You can't install the latest version if an older version is already installed
If you already have an older version of Support Center installed, the version 1810 installer fails. This issue is due to how the files are versioned between the original version and the latest version. To work around this issue, uninstall the older version of Support Center first. Then install the latest version from Configuration Manager version 1810.
Remote connections must include computer name or domain as part of the user name
If you connect to a remote client from Support Center, you must provide the machine name or domain name for the user account when establishing the connection. If you use a shorthand computer name or domain name (such as
.\administrator), the connection succeeds, but Support Center doesn't collect data from the client.
To avoid this issue, use the following user name formats to connect to a remote client:
Scripted server message block connections to remote clients might require removal
When connecting to remote clients using the New-CMMachineConnection PowerShell cmdlet, Support Center creates a server message block (SMB) connection to each remote client. It retains those connections after you complete data collection. To avoid exceeding the maximum number of remote connections for Windows, use the
net use command to see the currently active set of remote connections. Then disable any unneeded connections by using the following command:
net use <connection_name> /d
<connection_name> is the name of the remote connection.
Application deployment evaluation cycle request isn't sent correctly to remote machines
In Support Center, if you select Application deployment evaluation from the Invoke trigger action on the Content tab, this action starts a task that evaluates deployed applications. If you're connected to a local client, it evaluates both machine and user application deployments. However, if you're connected to a remote client, it only evaluates machine application deployments.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.