Merge pull request #5168 from aczechowski/cz-2107cb-9760004-tooldiag

create new article for tools data

Author: v-shils

memdocs/configmgr/core/TOC.yml

@@ -233,6 +233,8 @@ items:
           href: plan-design/diagnostics/levels-of-diagnostic-usage-data-collection-2006.md
         - name: Data for version 2002
           href: plan-design/diagnostics/levels-of-diagnostic-usage-data-collection-2002.md
+    - name: Configuration Manager tools
+      href: plan-design/diagnostics/tools.md
     - name: Frequently asked questions (FAQ)
       href: plan-design/diagnostics/frequently-asked-questions.yml
   - name: Security and privacy for Configuration Manager

memdocs/configmgr/core/plan-design/diagnostics/diagnostics-and-usage-data.md

@@ -2,7 +2,7 @@
 title: Diagnostics and usage data
 titleSuffix: Configuration Manager
 description: Learn about the diagnostics and usage data that Configuration Manager collects about itself.
-ms.date: 12/23/2019
+ms.date: 08/10/2021
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
@@ -16,14 +16,21 @@ ms.localizationpriority: medium
 
 *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.  
+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](../../servers/deploy/configure/about-the-service-connection-point.md) 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](../../servers/manage/use-the-service-connection-tool.md).
 
-> [!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.  
+> [!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](https://privacy.microsoft.com/privacystatement).  
+For more information, see the [Microsoft privacy statement](https://privacy.microsoft.com/privacystatement).
+
+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](how-diagnostics-and-usage-data-is-used.md)
+
+> [!TIP]
+> The **ConfigurationManager** PowerShell module also collects usage data. For more information, see [Configuration Manager cmdlet library privacy statement](/powershell/sccm/privacy-statement).
+>
+> Some of the tools that are included with Configuration Manager collect usage data. For more information, see [Diagnostic usage data for tools](tools.md).

memdocs/configmgr/core/plan-design/diagnostics/frequently-asked-questions.yml

@@ -3,21 +3,20 @@ metadata:
   title: Diagnostic and usage data FAQ
   titleSuffix: Configuration Manager
   description: Frequently asked questions about diagnostic and usage data for Configuration Manager
-  ms.date: 10/01/2021
+  ms.date: 11/15/2021
   ms.prod: configuration-manager
   ms.technology: configmgr-core
   ms.topic: conceptual
   author: aczechowski
   ms.author: aaroncz
   manager: dougeby
-  ms.collection: M365-identity-device-management
-    
+
 title: Frequently asked questions about diagnostics and usage data
 summary: |
   *Applies to: Configuration Manager (current branch)*
-  
+
   This article provides answers to frequently asked questions about diagnostic and usage data in Configuration Manager.
-  
+
 
 sections:
   - name: Ignored
@@ -58,7 +57,7 @@ sections:
       - question: |
           Can the data be used to form a network map?
         answer: |
-          No. This data doesn't include any network details, such as IP addresses or detailed geographic information. For more information, see [Levels of diagnostic usage data](levels-overview.md#bkmk_versions), and find more detail for the version you're using.
+          No. This data doesn't include any network details, such as IP addresses or detailed geographic information. For more information, see [Levels of diagnostic usage data](levels-overview.md#version-specific-details), and find more detail for the version you're using.
           
           The data does include time zone information from each site. This information can provide insight into the broad geolocation and global dispersion of sites in a hierarchy.
           
@@ -80,6 +79,8 @@ sections:
           For example, the following cloud services are a part of Microsoft Endpoint Manager:
           
           - [Desktop Analytics data privacy](../../../desktop-analytics/privacy.md)
+          - [Tenant attach data collection](../../../tenant-attach/data-collection.md)
+          - [Endpoint analytics data collection](../../../../analytics/data-collection.md)
           - [Privacy and personal data in Intune](/intune/protect/privacy-personal-data)
           - [Windows Autopilot requirements](/windows/deployment/windows-autopilot/windows-autopilot-requirements)
           
@@ -88,4 +89,4 @@ sections:
         answer: |
           No. Configuration doesn't collect or transmit any personal data or customer data. It's an on-premises product that you directly deploy, manage, and operate. The diagnostics and usage data that Microsoft collects improves the installation experience, quality, and security of future releases.
           
-          For more information about Configuration Manager data, see [Levels of diagnostic usage data](levels-overview.md).
+          For more information about Configuration Manager data, see [Levels of diagnostic usage data](levels-overview.md).

memdocs/configmgr/core/plan-design/diagnostics/how-diagnostics-and-usage-data-is-collected.md

@@ -2,7 +2,7 @@
 title: Diagnostics data collection
 titleSuffix: Configuration Manager
 description: Learn about how Configuration Manager collects diagnostics and usage data about itself.
-ms.date: 12/23/2019
+ms.date: 08/10/2021
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
@@ -16,7 +16,7 @@ ms.localizationpriority: medium
 
 *Applies to: Configuration Manager (current branch)*
 
-To collect diagnostics and usage data for Configuration Manager, each primary site runs SQL Server queries on a weekly basis. In a multi-site hierarchy, the data is replicated to the central administration site.  
+To collect diagnostics and usage data for Configuration Manager, each primary site runs SQL Server queries on a weekly basis. In a multi-site hierarchy, the data is replicated to the central administration site.
 
 At the top-level site of a hierarchy, the service connection point submits this information when it checks for updates. The mode of the service connection point determines how the data is transferred:
 
@@ -26,5 +26,12 @@ At the top-level site of a hierarchy, the service connection point submits this
 
 For more information, see [About the service connection point](../../servers/deploy/configure/about-the-service-connection-point.md).
 
+Next, you can view diagnostic and usage data to confirm that your Configuration Manager hierarchy contains no sensitive information:
+
 > [!div class="nextstepaction"]
 > [How to view diagnostics and usage data](view-diagnostics-and-usage-data.md)
+
+> [!TIP]
+> The **ConfigurationManager** PowerShell module also collects usage data. For more information, see [Configuration Manager cmdlet library privacy statement](/powershell/sccm/privacy-statement).
+>
+> Some of the tools that are included with Configuration Manager collect usage data. For more information, see [Diagnostic usage data for tools](tools.md).

memdocs/configmgr/core/plan-design/diagnostics/how-diagnostics-and-usage-data-is-used.md

@@ -2,7 +2,7 @@
 title: Use of diagnostics data
 titleSuffix: Configuration Manager
 description: Learn about how Microsoft uses the diagnostics and usage data that Configuration Manager collects.
-ms.date: 12/23/2019
+ms.date: 08/10/2021
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
@@ -38,7 +38,9 @@ Microsoft uses available data to improve the product. For example:
 
 - The initial support offered by the current branch of Configuration Manager limited the support timeline for Windows Server 2008 R2. Microsoft examined the usage data from customers who had upgraded to the Configuration Manager current branch. They then identified the need to revise and extend this timeline to support customers who still use this OS.
 
-- Microsoft improved the prerequisite checks for installing an update. They removed obsolete rules, accounted for additional cases, and automatically remediated some issues.  
+- Microsoft improved the prerequisite checks for installing an update. They removed obsolete rules, accounted for additional cases, and automatically remediated some issues.
+
+Next, learn about how Configuration Manager collects diagnostics and usage data about itself:
 
 > [!div class="nextstepaction"]
 > [How Configuration Manager collects data](how-diagnostics-and-usage-data-is-collected.md)

memdocs/configmgr/core/plan-design/diagnostics/levels-overview.md

@@ -1,12 +1,11 @@
 ---
 title: Levels of diagnostic usage data
 titleSuffix: Configuration Manager
-description: Learn about the levels of diagnostics and usage data that Configuration Manager collects
-ms.date: 04/05/2021
+description: Learn about the levels of diagnostics and usage data that Configuration Manager collects.
+ms.date: 08/10/2021
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
-ms.collection: M365-identity-device-management
 author: aczechowski
 ms.author: aaroncz
 manager: dougeby
@@ -46,25 +45,29 @@ Some examples of data that this level doesn't collect include:
 
 The Full level includes all data in the Basic and Enhanced levels. It also includes additional information about Endpoint Protection, update compliance percentages, and software update information. This level can also include advanced diagnostic information like system files and memory snapshots. This advanced data might include personal information exists in memory or log files at the time of capture.
 
-## <a name="bkmk_change"></a> How to change the level
+## How to change the level
 
 To change the data collection level, you need **Modify** permissions on the **Site** object class.
 
 1. In the Configuration Manager console, go to the **Administration** workspace, expand **Site Configuration**, and select the **Sites** node.
+
 1. Select **Hierarchy Settings** in the ribbon.
+
 1. Switch to the **Diagnostic and Usage Data** tab, then choose the data level.
 
-## <a name="bkmk_versions"></a> Version-specific details
+## Version-specific details
 
 The following articles detail the specific data that Configuration Manager collects at each level with each supported version:
 
+- [Diagnostic and usage data for 2107](levels-of-diagnostic-usage-data-collection-2107.md)
 - [Diagnostic and usage data for 2103](levels-of-diagnostic-usage-data-collection-2103.md)
 - [Diagnostic and usage data for 2010](levels-of-diagnostic-usage-data-collection-2010.md)
 - [Diagnostic and usage data for 2006](levels-of-diagnostic-usage-data-collection-2006.md)
 - [Diagnostic and usage data for 2002](levels-of-diagnostic-usage-data-collection-2002.md)
-- [Diagnostic and usage data for 1910](levels-of-diagnostic-usage-data-collection-1910.md)
 
 ## Next steps
 
+Next, learn about the diagnostics and usage data that Configuration Manager collects for its tools:
+
 > [!div class="nextstepaction"]
-> [Frequently asked questions](frequently-asked-questions.yml)
+> [Diagnostic usage data for tools](tools.md)

memdocs/configmgr/core/plan-design/diagnostics/tools.md

@@ -0,0 +1,45 @@
+---
+title: Diagnostic usage data for tools
+titleSuffix: Configuration Manager
+description: Learn about the diagnostics and usage data that Configuration Manager collects for its tools.
+ms.date: 08/10/2021
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: conceptual
+author: aczechowski
+ms.author: aaroncz
+manager: dougeby
+---
+
+# Diagnostic usage data for tools
+
+*Applies to: Configuration Manager (current branch)*
+
+<!-- 9760004 -->
+
+Some of the tools that are included with Configuration Manager collect usage data. Microsoft uses this data to improve the quality of these tools, and better understand customer usage. Microsoft collects data for the following Configuration Manager tools:
+
+- Client tools
+- Server tools
+- Support Center
+- CMTrace
+
+For more general information about these tools, see [Configuration Manager Tools](../../support/tools.md).
+
+> [!NOTE]
+> The **ConfigurationManager** PowerShell module also collects usage data. For more information, see [Configuration Manager cmdlet library privacy statement](/powershell/sccm/privacy-statement).
+
+The following data is collected for these tools:
+
+- Version
+- Start and stop times to calculate duration of use
+
+Because these tools can run on any Windows device, they all use the Windows diagnostic data channel. They don't rely on Configuration Manager diagnostic data collection. The device on which the tool runs needs to be configured for at least **Optional** diagnostic data. If you configure the device for any other setting, Windows won't collect data for these Configuration Manager tools. For more information on these Windows diagnostic data levels, see the following articles:
+
+- [Windows 10, version 1709 and newer optional diagnostic data](/windows/privacy/windows-diagnostic-data)
+- [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization)
+
+Next, see the frequently asked questions about diagnostic and usage data for Configuration Manager:
+
+> [!div class="nextstepaction"]
+> [Frequently asked questions](frequently-asked-questions.yml)

memdocs/configmgr/core/plan-design/diagnostics/view-diagnostics-and-usage-data.md

@@ -2,7 +2,7 @@
 title: View diagnostics data
 titleSuffix: Configuration Manager
 description: View diagnostic and usage data to confirm that your Configuration Manager hierarchy contains no sensitive information.
-ms.date: 08/13/2021
+ms.date: 11/15/2021
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: how-to
@@ -18,11 +18,11 @@ ms.localizationpriority: medium
 
 You can view diagnostic and usage data from your Configuration Manager hierarchy to confirm that it includes no sensitive or identifiable information. The site summarizes and stores its diagnostic data in the **TEL_TelemetryResults** table of the site database. It formats the data to be programmatically usable and efficient.
 
-The information in this article gives you a view of the exact data sent to Microsoft. It's not intended to be used for other purposes, like data analysis.  
+The information in this article gives you a view of the exact data sent to Microsoft. It's not intended to be used for other purposes, like data analysis.
 
 ## View data in database
 
-Use the following SQL command to view the contents of this table and show the exact data that's sent:  
+Use the following SQL command to view the contents of this table and show the exact data that's sent:
 
 ``` SQL
 SELECT * FROM TEL_TelemetryResults
@@ -34,7 +34,7 @@ When the service connection point is in offline mode, use the service connection
 
 For more information, see [Use the service connection tool](../../servers/manage/use-the-service-connection-tool.md).
 
-## <a name="bkmk_hashes"></a> One-way hashes
+## One-way hashes
 
 Some data consists of strings of random alphanumeric characters. Configuration Manager uses the SHA-256 algorithm to create one-way hashes. This process makes sure that Microsoft doesn't collect potentially sensitive data. The hashed data can still be used for correlation and comparison purposes.
 
@@ -49,14 +49,14 @@ When you view the raw data, a common hashed value appears in each row of data. T
 2. Use the following Windows PowerShell script to do the one-way hash of your support ID.
 
     ``` PowerShell
-    Param( [Parameter(Mandatory=$True)] [string]$value )  
-      $guid = [System.Guid]::NewGuid()  
-      if( [System.Guid]::TryParse($value,[ref] $guid) -eq $true ) {  
-      #many of the values we hash are Guids  
-      $bytesToHash = $guid.ToByteArray()  
-    } else {  
-      #otherwise hash as string (unicode)  
-      $ue = New-Object System.Text.UnicodeEncoding  
+    Param( [Parameter(Mandatory=$True)] [string]$value )
+      $guid = [System.Guid]::NewGuid()
+      if( [System.Guid]::TryParse($value,[ref] $guid) -eq $true ) {
+      #many of the values we hash are Guids
+      $bytesToHash = $guid.ToByteArray()
+    } else {
+      #otherwise hash as string (unicode)
+      $ue = New-Object System.Text.UnicodeEncoding
       $bytesToHash = $ue.GetBytes($value)
     }  
       # Load Hash Provider (https://en.wikipedia.org/wiki/SHA-2)
@@ -68,9 +68,11 @@ When you view the raw data, a common hashed value appears in each row of data. T
     return $result
     ```
 
-3. Compare the script output against the GUID in the raw data. This process shows how the data is obscured.
+1. Compare the script output against the GUID in the raw data. This process shows how the data is obscured.
 
 ## Next steps
 
+Next, learn about the levels of diagnostics and usage data that Configuration Manager collects:
+
 > [!div class="nextstepaction"]
 > [Levels of diagnostic usage data](levels-overview.md)