How to view diagnostics and usage data for System Center Configuration Manager

Applies to: System Center Configuration Manager (Current Branch)

You can view diagnostic and usage data from your System Center Configuration Manager hierarchy to confirm that no sensitive or identifiable information is included. Telemetry data is summarized and stored in the TEL_TelemetryResults table of the site database and is formatted to be programmatically usable and efficient. Although the following options give you a view of the exact data sent to Microsoft, they are not intended to be used for other purposes, like data analysis.

Use the following SQL command to view the contents of this table and show the exact data that is sent. (You can also export this data to a text file.):

  • SELECT * FROM TEL_TelemetryResults


Before you install version 1602, the table that stores telemetry data is TelemetryResults.

When the service connection point is in offline mode, you can use the service connection tool to export the current diagnostics and usage data to a comma-separated values (CSV) file. Run the service connection tool on the service connection point by using the -Export parameter.

One-way hashes

Some data consists of strings of random alphanumeric characters. Configuration Manager uses the SHA-256 algorithm, which uses one-way hashes, to ensure that we do not collect potentially sensitive data. The algorithm leaves data in a state where it can still be used for correlation and comparison purposes. For example, instead of collecting the names of tables in the site database, a one-way hash is captured for each table name. This ensures that any custom table names that you created or product add-ons from others are not visible. We can then do the same one-way hash of the SQL table names that ship by default in the product and compare the results of the two queries to determine the deviation of your database schema from the product default. This is then used to improve updates that require changes to the SQL schema.

When viewing the raw data, a common hashed value will appear in each row of data. This is the hierarchy ID. This hashed value is used to ensure that data is correlated with the same hierarchy without identifying the customer or source.

To see how the one-way hash works

  1. Get your hierarchy ID by running the following SQL statement in SQL Management Studio against the Configuration Manager database: select [dbo].[fnGetHierarchyID]()

  2. Use the following Windows PowerShell script to do the one-way hash of the GUID that's obtained from the database. You can then compare this against the hierarchy ID in the raw data to see how we obscure this data.

    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 (   
    $hashAlgorithm = [System.Security.Cryptography.SHA256Cng]::Create()    
    # Hash the input   
    $hashedBytes = $hashAlgorithm.ComputeHash($bytesToHash)              
    # Base64 encode the result for transport   
    $result = [Convert]::ToBase64String($hashedBytes)    
    return $result