A WMI query for the memory type and for the form factor on a Windows Server 2003-based computer returns 0x0 for each entry (922813)
The information in this article applies to:
- Microsoft Windows Server 2003, Datacenter Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003 R2 Standard x64 Edition
- Microsoft Windows Server 2003 R2 Enterprise x64 Edition
- Microsoft Windows Server 2003 R2 Datacenter x64 Edition
SYMPTOMS
You use Windows Management Instrumentation (WMI) to query the Win32_PhysicalMemory class for the memory type and for the form factor on a Microsoft Windows Server 2003-based computer. Additionally, the computer uses DDR-2 memory. In this scenario, the query returns 0x0 (unknown) for each entry.
CAUSE
WMI uses the System Management BIOS (SMBIOS) reference specifications for this hardware lookup operation. The memory type and the form factor are part of the memory device specification (a Type 17 structure).
Additionally, note the following specifics: - The memory type that is returned by the BIOS for DDR-2 memory is 0x13 (19). This specification was introduced in the SMBIOS v2.4 specification. 0x13 is defined as the DDR-2 memory type.
- The form factor that is returned by the BIOS for DDR-2 memory is 0xF (15). This specification was introduced in the v2.5 preliminary SMBIOS spec document. 0xF is defined as the FB-DIMM form factor.
These specifications are not included
on operating systems that were released before SMBIOS versions 2.4 and 2.5. Therefore, a value of 0x0 is returned when you perform the WMI queries that are described in the "Symptoms" section on a Windows Server 2003-based computer. Windows Server 2003 was released before the SMBIOS specifications for versions 2.4 and 2.5 were defined. Note The 0x0 value resolves as unknown.
Any tools that use this data, such as third-party systems management software, will be affected. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 7/19/2006 |
---|
Keywords: | kbprb kbExpertiseInter KB922813 kbAudOEM |
---|
|