| title | titleSuffix | description | ms.date | ms.subservice | ms.service | ms.topic | author | ms.author | manager | ms.localizationpriority | ms.collection | ms.reviewer |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diagnostics and usage data |
Configuration Manager |
Learn about the diagnostics and usage data that Configuration Manager collects about itself. |
08/10/2021 |
core-infra |
configuration-manager |
conceptual |
Banreet |
banreetkaur |
apoorvseth |
medium |
tier3 |
mstewart,aaroncz |
Applies to: Configuration Manager (current branch)
Configuration Manager collects diagnostics and usage data about itself, which is used by Microsoft to improve the installation experience, quality, and security of future releases.
Each Configuration Manager hierarchy enables diagnostics and usage data. It consists of SQL Server queries that run on a weekly basis on each primary site and at the central administration site (CAS). When the hierarchy uses a CAS, child primary sites replicate their data to that CAS. At the top-level site of your hierarchy, the service connection point submits this information when it checks for updates. If the service connection point is in offline mode, you transfer the information by using the service connection tool.
Note
Configuration Manager collects data only from the site's SQL Server database, and it doesn't collect data directly from clients or site servers.
For more information, see the Microsoft privacy statement.
Next, learn about how Microsoft uses the diagnostics and usage data that Configuration Manager collects:
[!div class="nextstepaction"] How Microsoft uses diagnostics and usage data
Tip
The ConfigurationManager PowerShell module also collects usage data. For more information, see Configuration Manager cmdlet library privacy statement.
Some of the tools that are included with Configuration Manager collect usage data. For more information, see Diagnostic usage data for tools.