Topic last updated—March 2008
Asset Intelligence cannot report the license channel correctly on applications that use ProductID to identify versions
When viewing Asset Intelligence reports License 01A, 01B, 01C, or 01D, the license channel information might not report correctly for some older applications, depending on how the application stores product ID information in the registry. For example, an enterprise that uses select Volume License Key editions might appear to have retail versions. This problem typically affects older products that use the ProductID instead of the DigitalProductID registry value.
Solution
There is no way to incorporate the correct information into the Configuration Manager 2007 Asset Intelligence reports. If you want to verify the versions, however, you can look at the Product ID in the registry of clients you suspect are reporting incorrect sales channel information. The ProductID registry entry for a software product is located in the system registry hive under the Registration subkey for the product. The ProductID registry entry for an operating system is located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion.
When you locate the value ProductID, in the data note the group of numbers after the first dash and match it to the following table of common channel IDs. For example, if the ProductID is 73931-640-2474146-57484, locate 640 in the following table.
ID | Description |
---|---|
OEM |
OEM |
000 |
TRIAL |
111 |
SELECT (Network installation) [Volume License Key] |
197 |
MSDN |
198 |
MSDN |
270 |
SELECT [Volume License Key] |
335 |
MSDN |
336 |
MSDN |
337 |
MSDN |
338 |
MSDN |
365 - 367 |
MSDN |
425 |
MSDN |
436 |
TRIAL |
460 |
TRIAL |
471 - 499 |
Home Use Program (HUP) |
550 |
OEM |
630 - 636 |
OEM |
640 - 650 |
OPEN [Volume License Key] |
652 |
SELECT [Volume License Key] |
660 |
SELECT [Volume License Key] |
700 - 705 |
Visual Studio .NET |
700 - 712 |
Office XP or Open License |
721 - 744 |
Home Use Program |
725 |
Academic |
726 - 736 |
Academic |
Processor count appears to be incorrect on Windows Server 2003
When one of the following conditions is true for a Windows Server 2003-based computer, Windows incorrectly reports the number of physical processors:
- The computer uses one or more
hyperthreading-enabled preocessors.
- The computer uses one or more multicore
processors.
Solution
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain an available hotfix. For more information about this known issue, see Microsoft Knowledge Base article 932370, "The number of physical hyperthreading-enabled processors or the number of physical multicore processors is incorrectly reported in Windows Server 2003," at http://go.microsoft.com/fwlink/?LinkId=111805.
License reports do not contain Exchange Server 2007 information
The licensing model used by Microsoft Exchange Server 2007 is currently not supported by Asset Intelligence reporting. Microsoft Exchange Server 2007 stores license relevant data in Active Directory Domain Services and is not inventoried by Configuration Manager clients. Because of this, Microsoft Exchange Server 2007 licensing data does not appear in license reports.
Solution
None.