Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

How to manually determine the license and sale origin channel information for a software product when the Asset Intelligence reports in SMS 2003 with Service Pack 3 do not report the correct channel information


View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

↑ Back to the top


Introduction

This article describes how to manually determine the license and sale origin channel information of an installed Microsoft software product. You may have to determine this information when the Asset Intelligence reports in Microsoft System Management Server (SMS) 2003 with Service Pack 3 (SP3) do not report the correct license channel information for that product.

Note The information that is provided in this article is only for license channel identification and for reporting. This article describes a method to manually extract the channel information for the software products that are installed on the computer.

↑ Back to the top


More information

The Asset Intelligence code in SMS 2003 parses the DigitalProductId registry entry in the Windows registry to extract the sales channel information by using a predefined offset. For example, the sales channel information may indicate whether a software product was sold by using the retail channel or by using an OEM channel. The Asset Intelligence reports use version 3 and version 4 of the DigitalProductId registry entry to extract license channel information from installed software products. However, in some cases, the Asset Intelligence reports may report the license channel information incorrectly for certain installed software products. Whether this issue occurs depends on how the products store product ID information in the registry. For example, an enterprise product that is a select Volume License Key version may be reported as a retail version product in the Asset Intelligence reports. This issue generally occurs when you use software products that use the ProductID registry entry instead of the DigitalProductId registry entry to store product ID information.

The names of the Asset Intelligence reports that provide the license and sales origin channel information are as follows:
  • License 1A - Microsoft License Ledger for Microsoft License Statements
  • License 1B - Microsoft License Ledger Item by Sales Channel
  • License 1C - Computers with a Specific Microsoft License Ledger Item and Sales Channel
  • License 1D - Microsoft License Ledger Products on a Specific Computer
The DigitalProductId registry entry for an installed software product is located in the system registry hive under the Registration subkey for the product. The DigitalProductId registry entry for an operating system is located in the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
The DigitalProductId registry entry contains the encoded REG_BINARY value of the product key that was used to enable the software product. The entry contains the following information:
Name: DigitalProductId
Type: REG_BINARY
Data: data

How to manually extract the product ID of an installed software product

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To manually obtain the channel information for an installed software product that uses an earlier version of the DigitalProductId registry entry, you have to first extract the product ID information from the ProductID registry entry. After you extract the product ID information, note the channel ID value in the product ID information, and then use the table that is provided in this article to find a matching channel description for that channel ID value.

To manually extract the product ID of an installed software product, follow these steps:
  1. Start Registry Editor.
  2. Expand the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
  3. Locate and then expand the subkey for the product for which you want to extract the product ID information.
  4. Locate and then click the Registration subkey.
  5. Double-click ProductID.
  6. Note the value in the Value data box, and then click OK. For example, the product ID information will be displayed as 73931-640-2474146-57484.
  7. Note the second set of numbers in the product ID. This number represents the channel ID value for that product. For example, if the product ID is 73931-640-2474146-57484, the channel ID value is 640.
  8. Use the following table to find a matching channel description.
    Collapse this tableExpand this table
    Values Description
    725Academic
    726 - 736Academic
    471 - 499Home Use Program (HUP)
    721 - 724Home Use Program (HUP)
    197MSDN
    198MSDN
    335 - 338MSDN
    365 - 367MSDN
    640 - 650 OPEN [Volume License Key]
    550 OEM
    630 - 636 OEM
    706 - 712 Office XP or Open License
    652 SELECT [Volume License Key]
    660SELECT [Volume License Key]
    111SELECT (Network installation) [Volume License Key]
    270SELECT [Volume License Key]
    000TRIAL
    436TRIAL
    460TRIAL
    700 - 705 Visual Studio .NET

↑ Back to the top


Keywords: kbexpertiseinter, kbhowto, KB941461

↑ Back to the top

Article Info
Article ID : 941461
Revision : 9
Created on : 12/4/2007
Published on : 12/4/2007
Exists online : False
Views : 375